What are A2A payments?

Account-to-account (A2A) payments are electronic transfers that move funds directly between bank accounts, without routing through card networks such as Visa or Mastercard. The payer's bank sends funds to the payee's bank over a domestic or cross-border payment rail, with no card scheme sitting in between. A2A is not a single system or network; it is a category that includes direct debits, direct credits, wire transfers, instant payment rails, and open-banking-initiated payments.

A2A payments are gaining share globally, with digital wallets now accounting for approximately 30% of global point-of-sale volume in markets led by India, Brazil, and Nigeria, many of which are funded by A2A infrastructure rather than cards. The category is growing fastest in markets where governments have invested in real-time payment infrastructure and, in some regions, mandated bank API access through open banking regulation.

Push payments and pull payments

All A2A transactions fall into one of two structures, defined by which party initiates the transfer.

A push payment is initiated by the payer, who instructs their bank to send funds to a recipient's account. The payer controls the timing and amount. Examples include a one-off bank transfer, a payroll run sent from an employer's account, or a refund sent by a business back to a customer. Push payments are generally irrevocable once sent.

A pull payment is initiated by the recipient, who requests funds from a payer's account with the payer's prior consent. The classic form is a direct debit mandate, where a utility company or subscription service draws recurring payments on a fixed schedule. Open-banking-powered pull payments, delivered through payment initiation services (PIS), are a newer variant that allows third-party platforms to trigger a pull from a user's bank account in real time, with the user authenticating through their bank's own interface rather than a static mandate.

The push/pull distinction matters for fintechs because the two structures have different settlement timing characteristics, return and dispute rights, and authorization models. Push payments typically carry no chargeback right. Pull payments on legacy rails may take several business days to confirm, while open-banking-initiated pull payments can confirm in seconds.

How A2A rails work in practice

The underlying infrastructure for A2A payments varies by market and use case. The major rail types are:

Batch settlement rails

Traditional A2A rails process payments in bulk files that settle at defined points during the business day. ACH in the US, SEPA Credit Transfer in Europe, and BACS in the UK are the primary examples. These systems are low-cost and highly reliable but operate on business days only and carry limited structured data per transaction. They remain the dominant infrastructure for payroll, pension disbursements, and supplier payment files.

Real-time payment rails

Instant A2A rails settle individual transactions in seconds, around the clock. Examples include RTP and FedNow in the US, Faster Payments in the UK, SEPA Instant in Europe, PIX in Brazil, and UPI in India. These systems support both push and, increasingly, pull payment flows. Global A2A e-commerce spend is projected to reach $936 billion (USD) by 2030, driven significantly by markets such as Brazil, where the launch of PIX accelerated A2A e-commerce spend from $3.6 billion in 2020 to $35.3 billion in 2024. 

Open-banking-initiated payments

In markets with open banking regulation, licensed third-party providers can initiate A2A payments through bank APIs on behalf of a payer, with the payer authenticating directly through their bank. In the EU and UK, this is governed by PSD2, which established the Payment Initiation Service Provider (PISP) regulatory category. The payer does not share card details with the merchant; the payment is authorized through the bank's own authentication flow. This model supports both one-off and recurring payments, and typically settles over the domestic instant rail.

A2A vs. card payments

For fintechs and operators choosing between payment methods, the practical differences between A2A and card-based payments come down to four dimensions:

• Cost: Card transactions carry interchange fees, scheme fees, and acquirer margins that typically range from 1.5% to 3.5% of transaction value. A2A payments settle over bank rails directly, with no interchange layer, making them significantly cheaper per transaction, particularly for high-value B2B flows
• Settlement speed: Cards settle to the merchant on a T+1 or T+2 basis after netting through the card schemes. Real-time A2A rails settle immediately; batch A2A rails settle same-day or next-day depending on the submission window
• Chargeback exposure: Card networks give payers statutory chargeback rights. Push-based A2A payments are generally irrevocable, which eliminates chargeback risk for merchants but removes a consumer protection that some users expect
• Reach: Card networks have global merchant acceptance infrastructure. A2A rails are domestic by default, requiring cross-border payment routing or correspondent banking arrangements to move funds across currency boundaries

Why A2A matters for fintechs

For platforms processing high-volume or high-value flows, A2A rails are often the more economical infrastructure choice. Key operational considerations include:

• Payroll and disbursements: Large credit files, government transfers, and employer payroll are almost universally processed over batch A2A rails; card networks are not used for these flows
• Subscription billing: Direct debit mandates and open-banking pull payments are the primary mechanism for recurring billing in most markets, avoiding card expiry and replacement friction
• Marketplace payouts: Platforms paying contractors, gig workers, or marketplace sellers typically use domestic A2A rails for local payouts, routing through SWIFT or local rail equivalents for cross-border disbursements
• Reconciliation: A2A transactions, particularly on real-time rails with ISO 20022 messaging, carry richer reference data than card transactions, enabling more automated payment reconciliation workflows
• FX considerations: A2A payments are denominated in the domestic currency of each rail. Cross-border A2A flows require a currency conversion and settlement step, either via SWIFT correspondent banking or through a multi-currency infrastructure layer

For platforms managing USD, GBP, or EUR flows across multiple markets, access to local A2A rails in each corridor avoids the cost and latency of routing everything through SWIFT. For a broader view of how A2A infrastructure integrates with virtual accounts and electronic funds transfer frameworks, see our related glossary entries.

‍