
Sooner or later a merchant asks their PSP for pay by bank. Sometimes it is a utility that wants lower acceptance costs on recurring bills, sometimes a merchant expanding into a market where customers rarely pay by card online.
The question for the PSP is not whether account-to-account (A2A) payments are growing. They are. The question is what happens inside your payment infrastructure when bank payments sit next to cards in the same checkout, and which parts of your current gateway logic stop working the way you expect.
This article covers both: where A2A stands at the end of 2026, how it differs from card processing at the gateway level, and the operational checklist a PSP should run before adding it.
Where A2A stands in 2026
An A2A payment is a transfer from the payer's bank account straight to the payee's account, with no card scheme involved. Customers reach these payments through national instant payment schemes, Open Banking payment initiation, QR codes and bank-led wallets.
A few data points show the direction:
- Volume. Juniper Research expects global A2A transaction value to grow 113% over five years from USD 91.5 trillion, reaching USD 195 trillion in 2030.
- Open Banking payments in the UK. The UK Payments Initiative, backed by UK banks and fintechs, announced the market rollout of its Open Banking payment scheme on 2 June 2026. The initial use cases are payments to government bodies, utilities, charities and financial services providers.
- Europe. Since 9 October 2025, payment service providers in the eurozone have had to offer instant euro transfers together with a check that the payee's name matches the account. The European Payments Initiative's wallet, Wero, has been live for retail payments in Germany since the end of 2025, and Luxembourg became its fourth market in September 2026.
- Regulation in progress. The EU's PSD3 and Payment Services Regulation reached provisional political agreement and passed the European Parliament's ECON committee in May 2026. As of late October 2026, they still need formal adoption by Parliament and Council.
None of this means cards are going away. Cards still behave consistently from one country to another, come with a familiar chargeback process and offer credit. A2A is becoming a second rail that merchants expect their PSP to support, market by market.
Why A2A is not "just another payment method" for the gateway
Most gateway logic was built around card transactions. A2A changes several assumptions at once.
There is no BIN. Card routing often starts from the card number: BIN range, issuer, card country, card type. A bank payment carries none of this. Routing has to rely on other parameters: the customer's country, currency, amount, the scheme or provider chosen at checkout.
The customer authorises the payment elsewhere. In an Open Banking flow, the customer leaves the checkout, approves the payment in their banking app or online banking, and comes back. Each redirect is a point where customers drop off, and the final status may arrive asynchronously rather than in the authorisation response.
On instant schemes, settlement is instant and the payment is final. Funds reach the payee within seconds. There is no authorisation-then-capture window, and a refund is a new transfer back to the customer, not a reversal of the original transaction.
Disputes follow the scheme, not a card network. Most A2A schemes do not have a chargeback process comparable to Visa or Mastercard. Buyer protection, dispute procedures and liability depend on the scheme and on national rules, such as the UK's mandatory reimbursement regime for victims of authorised push payment (APP) fraud.
The fraud pattern changes. With cards, the main concern is card-not-present fraud and stolen card data. With A2A, the main threat is APP fraud: the customer is persuaded to send money themselves. UK Finance reports that 66% of APP fraud cases start online and 17% through telecommunications networks.
Most schemes are domestic. Each country, and sometimes each scheme, has its own API standard, authentication flow and rules. A merchant selling in five countries may need five separate A2A connections.
The PSP checklist: what your gateway has to handle
1. Adding schemes and providers without rebuilding the gateway
The fragmentation above lands on the PSP's engineering team. If every new scheme or Open Banking provider is a separate integration project, A2A turns into a backlog of one-off work. Before committing to a market, check how a new provider gets connected: is the integration already available, or does it start from zero?
2. Routing rules that work without card data
Review which of your routing rules depend on card attributes. For bank payments you need rules based on transaction and customer parameters: country, currency, amount, the payment method chosen at checkout, time of day. If you work with more than one A2A provider in a market, you also need a way to split or balance traffic between them.
3. A plan for failed bank payments
When a card is declined, the gateway can often retry through another acquirer. A failed bank payment is different: the customer may have abandoned the redirect, the bank's API may be unavailable, or the payee check may have failed. Decide in advance what happens next: retry through another provider for the same scheme, or return the customer to the checkout to choose another method, including a card. For bank payments, cascading works before the customer is redirected to the bank.
4. Asynchronous statuses and reconciliation
Bank payments can confirm after the customer has left the page. The gateway needs to handle late status updates and notify the merchant reliably. On the finance side, instant settlement means reconciliation has to match payments that arrive in seconds, across providers that report in different formats. A unified view across cards and bank payments saves the operations team from reconciling each provider separately.
5. Refunds and disputes
Since a refund is a new outbound transfer, the gateway needs a payout path to the customer's account and a link between the refund and the original payment. For disputes, document the procedure for each scheme you support, and tell merchants clearly what protection their customers have.
6. Conversion by bank and by provider
The business case for A2A depends on payments going through at the major banks in the market. A single underperforming bank API can pull down the conversion for a whole segment of customers. Track success rates and decline reasons per provider, and where possible per bank, so the payments team sees the problem before merchants report it.
How Payneteasy approaches this
Payneteasy provides white-label payment gateway and payment orchestration software to PSPs, banks and large merchants. Several parts of the checklist above map to documented platform functions:
- Connecting providers. PSPs from the Payneteasy integrations catalog are already connected to the platform. With Payment Channels, a PSP from the catalog can usually be put to work within 1–2 weeks; the timeline depends mainly on the provider's onboarding.
- Routing on transaction parameters. Routing rules can use transaction parameters such as currency, amount and bank, as well as customer data such as IP country and billing country, and time and day of week. Traffic can be balanced between providers by coefficients or equally.
- Cascading between providers. A Cascading Chain passes a transaction to the next acquirer or PSP in the chain, with settings that define which decline codes continue or stop the chain. For bank payments, cascading works before the customer is redirected to the bank.
- Reconciliation and reporting. Reports and statements combine traffic from all connected PSPs, with decline reasons per processor and reconciliation updates available via API.
- Payouts. Payouts can be sent through SEPA, SWIFT and local rails, depending on the provider and market.
The gateway supports A2A payments next to cards: Open Banking, SEPA (including SEPA Instant where available) and local methods such as Pix, UPI, BLIK and iDEAL, depending on the connected PSP.
Which A2A schemes and providers a project needs depends on the PSP's markets and merchants, so the setup is defined during discovery.
Before you add A2A: a short list
- Which markets and schemes do your merchants actually need?
- Can your gateway connect a new A2A provider without a custom project?
- Which routing rules depend on card data, and what replaces them for bank payments?
- What happens when a bank payment fails, and who decides whether to offer a card?
- Can your reconciliation handle instant, final payments from several providers?
- Do you track conversion per provider and per bank?
Sources
- Juniper Research, "A2A Transaction Value to Reach $195 Trillion in 2030 Globally", 22 September 2025
- The Paypers, "UK banks and fintechs launch open banking payment scheme", 2 June 2026
- European Commission, "New EU rules make instant euro payments faster and safer", 10 October 2025
- European Payments Initiative, "EPI initiates Wero in Luxembourg", September 2026
- European Parliament, Legislative Train: Revision of EU rules on payment services (updated 25 October 2026)
- UK Finance, Annual Fraud Report 2026 press release, 15 June 2026