Banking Glossary

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. For the full definition, read What Is Banking Orchestration?

Orchestration

AI agent orchestration

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.

Journey orchestration

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.

Workflow orchestration

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.

Payment orchestration

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

Banking-as-a-Service orchestration

Banking-as-a-Service (BaaS) orchestration connects a non-bank platform, such as a marketplace, a software provider, or a spend management tool, to several licensed banking providers through one integration. The platform can then issue cards, open accounts, or pay out under its own brand, and route each product to the provider that fits best in each country. It is usually owned by the platform's product and payments teams.

BaaS orchestration chooses which provider does the work. Banking orchestration runs inside the financial institution that provides it, keeping every partner program's accounts, payments, approvals, and audit record on one live picture, so a bank that offers Banking-as-a-Service governs its partners' activity as closely as its own.

Middleware

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.

Payments, treasury and digital assets

Payment workflow

A payment workflow is the sequence of steps a payment passes through between initiation and settlement: capture, validation, approval, sanctions screening, routing to a rail, settlement, and reconciliation. Each step can involve a different system or person, and the workflow defines the order, the rules, and what happens when a step fails. Payments and operations teams design and run payment workflows, often separately for each rail.

In banking orchestration, the payment workflow runs on the same live context as the ledger and the controls around it. Every step is an event the institution can trace, and adding a rail means adding a route to the same workflow rather than building a separate one.

Transaction banking

Transaction banking is the set of services a bank provides to businesses to move and manage money day to day: payments and collections, cash and liquidity management, account services, and trade finance. It sits at the center of a business's operations, which is why it anchors commercial banking relationships and the deposits that come with them. Corporate treasurers and finance teams use it; commercial banking and treasury services teams run it.

Banking orchestration gives transaction banking one live view across the rails, accounts, and approvals it spans, so a financial institution can offer its commercial customers real-time visibility and control under its own brand.

Cash position

A cash position is the total cash a business holds across its bank accounts at a point in time, net of payments due in and out. Treasurers check it daily, often several times a day, to decide what to pay, what to hold, and what to invest or borrow. Building it usually means pulling balances from several banks and portals and reconciling them by hand.

The term assumes every holding is fiat cash. As businesses begin to hold stablecoins and tokenized deposits alongside cash, XYB uses asset position instead: every asset a treasurer holds, fiat and stablecoin, across every bank and every rail, in real time.

Tokenized deposits

Tokenized deposits are bank deposits represented as digital tokens on a programmable ledger. They remain deposits: a liability of the issuing bank, held under its banking license, not a separate asset issued by a third party. The token form lets them move and settle instantly, around the clock, and carry rules with them, such as conditions on when funds release. Banks are piloting them for business payments, treasury, and settlement between institutions.

Tokenized deposits are one instance of decentralized finance reaching the balance sheet. For a financial institution, the practical question is whether its ledger can treat a token as a first-class currency type alongside fiat, on the same live context, or has to run it in a separate system.

Banking systems

System of record

A system of record is the authoritative source for a given piece of data: the one system whose version wins when copies disagree. In banking, the core ledger is usually the system of record for balances and transactions, while other systems are the system of record for customers, cards, or loans. Every integration decision starts with knowing which system is authoritative for what.

Banking orchestration does not have to change which system is the system of record. Above an existing core, the core stays authoritative and orchestration keeps every other system in step with it on one live context. Where a new proposition starts without a core, the AFI Platform's multi-currency ledger can be the system of record itself.

Related: Canonical model · The AFI Platform

White-label banking

White-label banking is when a financial institution offers a product built on another company's technology under its own brand. The customer sees only the institution's name and design; the technology provider stays invisible. It lets an institution launch digital accounts, payments, or treasury services without building the underlying platform, while keeping the customer relationship. It is the reverse of banking-as-a-service, where a non-bank brand offers products on a bank's license. White-label treasury is a common case: a commercial treasury portal offered under the bank's own brand.

On the AFI Platform, white-label is the shape of every Solution rather than an option: the Experience Layer renders under the institution's brand, and the institution owns the offering and the relationship.