Skip to content

Reference stack

Add open banking payments

An account-to-account payment stack covering payment initiation, consent, bank connectivity, account verification and reconciliation.

MerchantsPlatformsBillers

Intended audience and markets

Audience

MerchantsPlatformsBillers

Markets

United KingdomEuropean Economic AreaSelected open-banking markets

Infrastructure layers

01

Payment initiation

Required

Initiate customer-authorised account-to-account payments.

Selection criteria

  • PISP coverage and legal entity
  • Bank reach
  • Payment status and refund model
02

Account verification and data

Optional

Verify account ownership and obtain data needed for risk or reconciliation.

Selection criteria

  • Verification method
  • Consent and refresh
  • Data normalisation
03

Consent and user experience

Required

Present bank selection, consent and redirect or embedded flows.

Selection criteria

  • Conversion and accessibility
  • Consent evidence
  • Fallback behaviour
04

Reconciliation and risk

Required

Match payment outcomes to orders and detect abuse.

Selection criteria

  • End-to-end reference
  • Pending and failed states
  • Fraud and refund controls

Implementation sequence

  • Payment initiation
  • Account verification and data
  • Consent and user experience
  • Reconciliation and risk

Regulatory considerations

  • Payment-initiation permissions and consumer protections vary by market.
  • Variable recurring payments and similar products are not uniformly available.

Technical considerations

  • Design for asynchronous status, bank downtime and user abandonment.
  • Do not treat an initiation response as final settlement.

Questions to ask providers

  • Which legal entity contracts for each service and in which jurisdictions?
  • Which responsibilities remain with the product operator rather than the provider?
  • What are the implementation, approval, testing and migration timelines?
  • How are incidents, exits, data portability and business continuity handled?
  • How are refunds, returns and mistaken payments handled?

What this stack does not cover

  • Card acceptance and direct-debit mandates are separate rails.

Related stacks

Reviewed on 2026-07-07.

Provider options are examples of infrastructure roles, not endorsements or a guarantee of suitability, availability or regulatory compliance. Confirm requirements for your product with each provider and qualified advisers.