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.
Overview
Meaning and scope
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.
Mechanism and operation
An open banking payment typically lets an authorized third party initiate a bank-account transfer after the payer grants consent through a supported bank interface. The payer is usually sent to the bank or a secure bank-controlled authorization flow to confirm the instruction. The initiation service receives status information according to the relevant interface and payment scheme; it does not automatically become the custodian of the payer’s deposits. A bank accepting an instruction is different from the beneficiary receiving final funds. Availability, verification and cancellation rules depend on the jurisdiction, participating institutions and local account-to-account payment rail. Merchants must keep order state separate from redirection, authentication and payment-finality state, especially when callbacks arrive late or the customer closes the browser.
Practical payment example
A customer authorizes a bank transfer through a regulated open-banking flow; the merchant verifies the actual payment status separately from the consent screen.
Operational checks
Verify consent scope, payer authentication, amount, currency, beneficiary details, bank instruction reference, idempotency handling and final credited receipt. Reconcile failed or pending bank outcomes before marking orders paid. 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. 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.
Distinctions and limits
Open banking describes standardized access or initiation interfaces; it is not synonymous with instant payment, guaranteed delivery, or a particular bank settlement system.
Related reading
Related definitions: Payment Reconciliation.
Example
A customer authorizes a bank transfer through a regulated open-banking flow; the merchant verifies the actual payment status separately from the consent screen.
Comparison
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.
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)