Plain definitions of the banking infrastructure terms in use today. Each entry explains the term on its own, then how it relates to banking orchestration. Where XYB’s own vocabulary is the answer, the entry links to AFI Concepts.
AI agent orchestration is the coordination of multiple AI agents: deciding which AI agent or tool acts on a task, in what order, and with what data and permissions. It sits in the AI stack, above the systems a financial institution runs, and is usually owned by data and AI teams. Its decisions are probabilistic by design, because the AI agent is choosing what to do next.
AI agent orchestration decides what an AI agent does. Banking orchestration supplies the ground it acts on: current state rather than a stale copy, the entitlements that bound each action, and an audit trail of everything that happened. The two work as a pair. The AI agent chooses; the substrate records what happened.
Related: Banking orchestration · The AFI Platform
Journey orchestration, also called digital banking orchestration, coordinates the steps of a customer journey across channels. An account opening that starts on a phone, pauses for a document, and finishes with a branch adviser is one journey; journey orchestration keeps the customer and the staff on the same step. It sits at the engagement surface and is usually owned by digital and customer-experience teams.
Journey orchestration sequences what the customer sees. Banking orchestration works beneath it, keeping the systems, people, and processes behind each step on one live context, so every channel shows the institution's actual state rather than a copy that has to be reconciled later.
Related: Banking orchestration · Experience Layer
Workflow orchestration, also called business process orchestration, automates multi-step business processes: routing tasks between systems and people, applying rules, and tracking each case to completion. Workflow tools are general-purpose and work across industries; operations and IT teams use them to automate processes such as onboarding, servicing, and exception handling.
Workflow orchestration runs a process. Banking orchestration runs the process together with the systems it touches and the people involved, with banking context built in: the ledger, the payment rails, and the regulatory controls each step depends on. A workflow tool has to be taught all of that; banking orchestration starts from it.
Related: Banking orchestration · Orchestration Layer
Payment orchestration routes each payment to a rail or provider, choosing between options such as ACH, wire, real-time payment rails, or card processors on cost, speed, and availability, and handling retries when a route fails. Merchants and payment service providers adopted it first; financial institutions now use it as they connect more rails.
Payment orchestration is one function within banking orchestration. Banking orchestration handles payments alongside the ledger, the data, and the workflows around them, so a payment's status, its approvals, and its accounting stay on one live context instead of being reconciled across separate systems afterwards.
Related: Banking orchestration · Open adapters
Middleware is software that connects applications so they can exchange data, translating formats and passing messages between systems. An enterprise service bus (ESB) is a centralized form of middleware that routes messages between many applications through one shared channel. Financial institutions have long used both to connect core systems to channels and third-party services.
Middleware moves messages between systems; it does not hold the state of the business or govern the process those messages belong to. Banking orchestration does both. Every action is an event carrying full context, governed and auditable, so the institution operates on one live picture of its business rather than a chain of hand-offs between systems.
Related: Banking orchestration · Canonical model