Open Banking Payment
Pronunciation: OH-pun BANKING PAY-munt
Also known as: Open Banking Transfer
Definition
An open banking payment is an account-to-account payment initiated through regulated access to a customer’s bank account using open banking interfaces and customer authentication. Open banking payment is the general payment type. Pay by Bank is a common customer-facing name, while open banking payment processing describes the technical and operational workflow that supports it. For payment teams, the important point is to define the responsible system, the evidence that proves the outcome, and the exception path when normal processing does not complete.
Overview
An open banking payment is an account-to-account payment initiated through regulated access to a customer’s bank account using open banking interfaces and customer authentication. Open banking payment is the general payment type. At checkout, a payment initiation provider connects the merchant or platform to the selected bank, passes the payment details, and redirects or hands off the customer for bank authentication and approval.
In operational terms, this flow should remain connected to Payment Status Mapping , because its upstream decision and downstream outcome must be interpreted together. The implementation should record consent, payer bank, beneficiary, amount, currency, payment reference, authentication outcome, provider identifiers, and subsequent bank status. These records support Payment Authorization and let an operator reproduce the result from authoritative evidence rather than relying on a dashboard snapshot or a provider’s latest status alone. For merchants, developers, finance teams, and payment operators, a well-designed implementation means that customer authorization, provider processing, payment status, and final financial evidence remain distinct but traceable throughout the payment journey.
Open Banking Payment should remain distinct from Payment Reconciliation, because the two records can carry different authority, timing, and financial effects.
Risks include payment redirection fraud, account takeover, unavailable bank APIs, consent failure, duplicate initiation, and mistaken fulfillment based only on an early status. Important failure modes include duplicate or delayed events, wrong destinations or currencies, stale instructions, unavailable providers, unsupported retries, and customer-facing status that differs from authoritative records.
The final control should feed Payment Reconciliation , preserve the original evidence, and document any correction, override, or manual action. Controls should validate inputs server-side, authenticate external events, make irreversible actions idempotent, and reconcile provider, network, settlement, and ledger evidence. For Open Banking Payment, this point supports the definition’s focus on open banking payment is an account-to-account payment initiated through regulated access to a customer’s bank account using open.
Key Takeaway
Open Banking Payment is useful only when its scope, evidence, state transitions, financial effect, and exception handling are defined precisely; otherwise similar events can be mistaken for the same payment outcome.
Sources
- Pay by Bank — Open Banking Limited (2026-08-03)
- Interlinking payment systems and the role of application programming interfaces — Bank for International Settlements, CPMI (2026-08-03)
- Authentication Cheat Sheet — OWASP (2026-08-03)