Klarna, Afterpay, Affirm, and Zip differ most on merchant fees, market reach, and repayment terms. All four let a customer split a purchase into instalments while the merchant is paid upfront, and all four charge the merchant more than a card transaction does. The choice between them comes down to where a business sells, what it sells, and what the customer’s basket looks like.

Buy now, pay later has moved well past novelty. Industry estimates put global BNPL gross merchandise volume above USD 560 billion in 2025, growing at roughly 20% annually. At that scale the provider decision is a real commercial one, so here is how the four compare on the things that determine cost and coverage.

How the four BNPL providers compare

Fee figures are published ranges and vary by contract, category, and volume. Treat them as a starting point for negotiation rather than fixed rates.

Klarna

Klarna is the broadest of the four by geography. Founded in Sweden in 2005 and listed on the NYSE in September 2025, it reported USD 33.7 billion in gross merchandise volume in the first quarter of 2026 across roughly 119 million consumers. Its take rate, at around 2.7%, is the lowest of the group, which reflects a business built on high-frequency, lower-value transactions: Klarna’s average order value sits near USD 101.

For merchants, Klarna’s appeal is reach and recognition. It operates across more markets than the other three, which matters for a business selling into several countries and wanting one BNPL relationship rather than a different provider per market. Published merchant rates start around 3.29% plus a fixed fee and rise from there depending on the product and contract.

The tradeoffs are cost at the lower end of the basket range and onboarding time. Klarna’s rate is competitive at its base but climbs for some products, and merchants have reported multi-week approval processes.

Afterpay

Afterpay, trading as Clearpay in the UK, is the most focused of the four on a specific shopper profile: younger customers buying mid-range fashion and beauty. Its model is the classic pay-in-four structure, four interest-free instalments over six weeks, with consumer transaction limits generally capped around USD 2,000.

That cap defines where Afterpay fits. It works well for repeat, lower-ticket retail purchases and poorly for anything expensive. Afterpay charges consumers late fees on missed payments, which is a difference from Affirm and worth knowing if a merchant’s customer base is price-sensitive.

Geographically it is strongest in Australia, where it originated, and has substantial presence in the US and UK. For a fashion or beauty brand targeting a younger demographic in those markets, it is often the first BNPL provider to consider.

Affirm

Affirm is the outlier on basket size and pricing. It holds roughly one-third of US BNPL payment value, focuses on larger purchases, and prices accordingly: its take rate is around 8.9%, more than three times Klarna’s, and merchant rates commonly run near 6% plus a fixed fee. Its average order value, near USD 255, is roughly two and a half times Klarna’s.

That pricing buys a different product. Affirm offers longer repayment terms suited to high-ticket items such as electronics, furniture, and travel, charges consumers no late fees, and reports payment activity to credit bureaus. Merchants in high-ticket categories often find the higher fee is offset by the size of the basket it unlocks.

One honest caveat that vendor comparisons tend to skip: Affirm’s zero-late-fee promise does not mean zero consumer cost. A substantial share of Affirm loans carry interest, so the “interest-free” framing applies to some plans and not others. Merchants should understand which plans they are enabling.

Affirm’s footprint is narrow by comparison, concentrated in the US and Canada. For a merchant selling only into those markets with high-value products, that concentration is not a problem. For a global business it is a limitation.

Zip

Zip requires a caveat that older comparisons miss entirely. Zip has withdrawn from the UK and is winding down its New Zealand operation, leaving its footprint concentrated in Australia and the United States. Any comparison recommending Zip for a market it has left is out of date, and merchants should verify current availability before building an integration.

Where it does operate, Zip offers pay-in-four alongside longer-term options and charges consumers late fees. In Australia, its home market, it remains a meaningful player alongside Afterpay. Outside Australia and the US, it is no longer a practical option.

What BNPL costs merchants, and what you get for it

BNPL is materially more expensive than card acceptance. Published merchant rates across providers run roughly 3.29% to 8% plus a fixed fee, against typical card processing of 2% to 3%. That gap is the central fact of the BNPL decision.

The case for paying it rests on basket economics. Merchants commonly report average order value increases in the range of 10% to 30% after adding BNPL, along with reduced cart abandonment, because the payment option removes the affordability objection at the point of decision. Whether that trade is worth it depends entirely on category and margin: a high-margin, high-ticket retailer can absorb 6% to unlock a larger basket, while a low-margin grocery or commodity seller usually cannot.

The honest way to evaluate this is to model it against your own numbers rather than trusting a general uplift figure. Gr4vy’s guide to how instalment payments work covers the mechanics behind the model.

A regulatory note worth factoring in: the UK Financial Conduct Authority brought BNPL under formal regulation from July 2026, which adds compliance obligations for providers operating there. Merchants selling into the UK should confirm how their provider has adapted.

How to choose a BNPL provider for your market

The decision resolves along three axes.

Geography first. Klarna has the broadest international footprint. Afterpay is strongest in Australia, the US, and the UK. Affirm is US and Canada. Zip is now Australia and the US only. A business selling into a market its preferred provider does not serve needs a different provider for that market, which is how merchants end up running more than one.

Then ticket size. Affirm is built for high-value baskets and prices for them. Afterpay caps out around USD 2,000 and suits lower-ticket retail. Klarna sits in the middle with the broadest range of plan types.

Then customer profile. Afterpay skews young and retail-focused. Affirm suits considered, higher-value purchases. Klarna spans everyday shopping. The provider whose consumer base already overlaps with your customers will convert better than the one with the marginally lower fee.

Gr4vy’s merchant’s guide to BNPL covers the wider question of whether to offer BNPL at all.

Running more than one BNPL provider

Most merchants selling across several markets end up with more than one BNPL provider, because no single provider covers every market well. A business selling in Australia, the UK, and the US could reasonably want Afterpay for Australian retail, Klarna for the UK, and Affirm for high-ticket US purchases. That is three integrations, three contracts, three reporting formats, and three sets of rules about which provider appears at which checkout.

The operational question then becomes how to add, switch, and control providers without an engineering project each time. This is the coordination problem payment orchestration addresses: connecting providers through one integration and deciding through configuration which methods appear in which market.

The practical difference is speed. Ding, the international mobile top-up service operating across more than 140 countries, used no-code rules to show different payment methods by market, prioritising local options where they performed best, and cut the time to integrate a new gateway or local payment method from three to six weeks down to three days. The same principle applies to BNPL: if adding a provider for a new market takes a quarter, it usually does not happen. Gr4vy’s guide to BNPL and payment orchestration covers the setup in more detail.

Frequently asked questions

Which BNPL provider is cheapest for merchants?

Klarna generally has the lowest published starting rate, from around 3.29% plus a fixed fee, and the lowest take rate of the four at roughly 2.7%. Affirm is the most expensive, commonly near 6% plus a fixed fee with a take rate around 8.9%. Rates vary by contract, category, and volume, so published figures are a starting point for negotiation instead of fixed prices.

What is the difference between Klarna and Affirm?

They serve structurally different markets. Klarna focuses on high-frequency, lower-value purchases with the broadest international footprint and an average order value near USD 101. Affirm focuses on higher-ticket US and Canadian purchases with longer repayment terms, no consumer late fees, and an average order value near USD 255. Affirm’s take rate is roughly three times Klarna’s, reflecting the different segments.

Is Zip still available in the UK?

No. Zip has withdrawn from the UK and is winding down its New Zealand operation, leaving its footprint concentrated in Australia and the United States. Merchants should verify current market availability directly with any provider before building an integration, as coverage changes.

How much do BNPL providers charge merchants?

Published merchant rates run roughly 3.29% to 8% of the transaction plus a fixed fee, against typical card processing of 2% to 3%. Klarna starts at the lower end, Affirm and several others sit closer to 6%. The higher cost is generally justified by average order value uplift and reduced abandonment, though whether that trade works depends on category and margin.

Does BNPL increase average order value?

Merchants commonly report average order value increases in the range of 10% to 30% after adding BNPL, along with lower cart abandonment, because the option removes the affordability objection at the point of purchase. These are reported ranges rather than guaranteed outcomes, and the effect varies significantly by category, so it is worth modelling against your own basket data.

Which BNPL provider is best for high-ticket items?

Affirm, in the US and Canada. It is built for larger purchases, offers longer repayment terms suited to electronics, furniture, and travel, and has an average order value roughly two and a half times Klarna’s. Afterpay is a poor fit for high-ticket purchases, with consumer limits generally capped around USD 2,000.

Do merchants need more than one BNPL provider?

Many do, once they sell across several markets, because no single provider has strong coverage everywhere. Klarna is broadest internationally, Afterpay is strongest in Australia and retail markets, Affirm is US and Canada, and Zip is now Australia and the US. Businesses selling into multiple regions commonly run two or three providers and route customers to the right one by market.

Is BNPL regulated?

Increasingly. The UK Financial Conduct Authority brought BNPL under formal regulation from July 2026, adding compliance obligations for providers operating there. Other jurisdictions are at varying stages, and merchants selling internationally should confirm how each provider has adapted in the markets they serve.

Choosing between them

There is no single best BNPL provider, and any comparison that names one is usually selling something. The four occupy genuinely different positions: Klarna is the internationally broad, lower-cost, high-frequency option; Afterpay owns younger retail shoppers in a handful of markets; Affirm is the high-ticket US specialist that prices accordingly; and Zip is now an Australia and US proposition after retreating from other markets.

The right choice follows the market a business sells into and the basket it sells, in that order. Fee differences matter, but a provider two points cheaper in a market where its consumer base is thin will convert worse than a slightly costlier provider customers already use and trust. For businesses selling across several markets, the realistic answer is more than one provider, and the practical question becomes how quickly a new one can be added when a market demands it.

Gr4vy connects merchants to more than 400 payment providers and methods, including BNPL providers, through a single integration, so adding or switching one is a configuration change. To talk through the right BNPL mix for your markets, get in touch with our team.

Pix, UPI, FedNow, and SEPA Instant are national instant payment schemes with very different adoption. All four move money between bank accounts in seconds, at a fraction of card costs, and all four are backed by central banks or central infrastructure. What separates them is whether ordinary people actually use them to buy things. In Brazil and India, the answer is emphatically yes. In the United States and much of Europe, the schemes are running but consumers have barely met them.

That gap matters for merchants, because it determines whether supporting a scheme is a requirement or an option. Below is how the four compare on scale, cost, and merchant relevance, with figures attributed to the operators and central banks that publish them.

How the four schemes compare at a glance

Pix (Brazil)

Pix is the most successful instant payment launch anywhere. Operated by Banco Central do Brasil since November 2020, it handled 63.4 billion transactions worth roughly R$26.4 trillion in 2024, a volume that exceeded combined credit and debit card transactions in Brazil by around 80%. Adoption reached most of the adult population within five years of launch, a pace no comparable scheme has matched.

For merchants, Pix is no longer optional in Brazil. Worldpay’s Global Payments Report puts Pix at roughly 42% of Brazilian e-commerce value and 34% at the point of sale in 2025. A checkout in Brazil without Pix is turning away a large share of customers who expect it as the default.

Two developments make Pix more useful to merchants than a simple bank transfer. The first is Pix Automático, which brings recurring payments to the scheme, opening it to subscriptions and instalment billing that previously required cards. Gr4vy introduced Pix Automático through its dLocal integration, giving merchants access to recurring Pix without building the connection themselves.

The second is speed of adoption for merchants entering the market. Ding, the international mobile top-up service, launched Pix in Brazil through Gr4vy as part of a shift that cut the time to integrate a new gateway or local payment method from three to six weeks down to three days. For a business operating across many markets, that difference determines whether a local method gets launched at all or stays permanently on the roadmap.

UPI (India)

India’s Unified Payments Interface is the largest real-time payment system in the world by transaction count. NPCI data puts UPI at more than 228 billion transactions in 2025, with daily volumes in the hundreds of millions. By some measures UPI accounts for close to half of all global real-time retail payment volume.

The model is different from Pix in one important respect: UPI is heavily QR-driven at the point of sale, and it is built around a layer of consumer-facing apps rather than bank interfaces. For merchants, acceptance usually means displaying a QR code or integrating a UPI collect flow, and UPI AutoPay covers recurring mandates.

As in Brazil, UPI is not a nice-to-have for merchants selling in India. Card penetration is comparatively low, and a checkout built for cards alone reaches a small fraction of the addressable market. Gr4vy’s guide to payment methods in India covers the wider local mix.

FedNow (United States)

FedNow is the newest of the four and the least relevant to merchants today, which is worth stating plainly instead of glossing. Launched by the Federal Reserve in July 2023, it has onboarded more than 1,500 financial institutions, but volumes remain small in relative terms: the Fed reported 2.73 million transactions worth $271.3 billion in the first quarter of 2026. Growth is fast, at roughly 108% year on year, but from a low base.

The composition of that volume tells the real story. The average FedNow transaction is worth close to $99,000, which reflects treasury, payroll, and business-to-business use instead of consumers buying things. The Federal Reserve raised the transaction limit from $1 million to $10 million in late 2025, further signalling where the system is being used. Consumer-to-business acceptance is expected to develop through the Request for Payment capability, but that is a future state rather than a current one.

For a merchant selling in the United States today, FedNow is something to monitor. Cards and wallets remain where the volume is, and building for FedNow acceptance ahead of consumer demand would be premature.

SEPA Instant (Europe)

SEPA Instant Credit Transfer has been running since November 2017, but the significant change is regulatory. Under the EU Instant Payments Regulation, eurozone banks were required to support receiving and sending instant euro transfers by 2025, which removed the patchy availability that had limited the scheme for years. Volumes through the ECB’s TIPS settlement platform grew sharply, reaching 1.355 billion transactions in 2024, a fourfold increase year on year.

SEPA Instant covers euro transfers across a broad set of countries, which makes it unusual among these schemes: it is natively cross-border within the eurozone instead of purely domestic. The limitation is that it handles euro only, so it does not serve non-euro corridors.

Merchant-facing acceptance is still developing. Pay-by-bank products built on SEPA Instant are growing, and the regulatory mandate has removed the main structural barrier, but consumer habit in most European markets still runs through cards and wallets. Gr4vy’s guide to real-time payments across Europe covers the regional picture in more detail.

What real-time schemes mean for merchant costs and settlement

The commercial case for real-time schemes rests on three differences from cards.

Cost. Instant transfers typically cost merchants far less than card interchange, which is the main reason Brazilian merchants moved volume to Pix so quickly. On thin-margin categories the difference is material.

Settlement speed. Funds arrive in seconds rather than in a settlement batch days later, which changes working capital for businesses operating on tight cycles.

No chargebacks. Instant transfers are irrevocable, which removes chargeback exposure. That cuts both ways: it protects the merchant from dispute costs, and it removes the consumer protection that makes buyers comfortable with cards for high-value or delayed-delivery purchases. Merchants adopting these schemes need a refund process, because the card dispute mechanism they may have relied on does not exist here.

Gr4vy’s comparison of real-time payments versus cards works through the tradeoff, and its guide to bank-to-bank payments covers the underlying mechanics.

Independent research suggests the direction of travel is consistent even where adoption is early. The Capgemini Research Institute reported instant payments at 13% of global non-cash transactions in 2022, projecting the share to pass 22% by 2028.

Which schemes should a merchant support?

The answer follows the market more than the technology, and the four schemes fall into two clear groups.

Pix and UPI are effectively mandatory for merchants selling into Brazil and India. Both have majority consumer adoption, both carry lower costs than cards, and in both markets a card-only checkout reaches a minority of potential buyers.

FedNow and SEPA Instant are optional today and worth preparing for instead of rushing. FedNow lacks consumer-to-business volume, and SEPA Instant, while now universally available in the eurozone by regulation, has not yet displaced card and wallet habits at checkout.

The practical difficulty is that this calculus differs in every market a business sells into, and it changes as schemes mature. Ding, operating across more than 140 countries, handled this by using no-code rules to show different methods in different markets, prioritising Pix in Brazil and PayPal in Germany, with each change made through configuration rather than an engineering project. Deciding which methods appear where, and changing that decision as adoption shifts, is the coordination problem that payment orchestration exists to solve. Gr4vy’s guide to local methods versus international card schemes covers the wider decision.

Frequently asked questions

What is the difference between Pix and UPI?

Both are national instant payment schemes with near-universal adoption in their home markets, but they differ in operator and model. Pix is run directly by Brazil’s central bank and handled 63.4 billion transactions in 2024. UPI is operated by NPCI in India, processed more than 228 billion transactions in 2025, and is more heavily QR-driven at the point of sale, built around consumer apps instead of bank interfaces.

Is FedNow used by consumers?

Barely, so far. FedNow launched in July 2023 and has onboarded more than 1,500 financial institutions, but Federal Reserve figures show 2.73 million transactions worth $271.3 billion in the first quarter of 2026, with an average transaction value near $99,000. That profile reflects treasury, payroll, and business-to-business use instead of consumer purchases. Consumer-to-business acceptance is expected to develop through Request for Payment.

Do real-time payments have chargebacks?

No. Transfers on these schemes are irrevocable, so there is no chargeback mechanism. This protects merchants from dispute costs but removes the consumer protection buyers associate with cards, which is one reason adoption is slower for high-value or delayed-delivery purchases. Merchants accepting these methods need their own refund process.

Can you take recurring payments over Pix or UPI?

Yes, on both. Pix Automático brings recurring payments to Pix, and UPI AutoPay provides mandates in India. Both open these schemes to subscriptions and instalment billing that previously required cards. Recurring support on FedNow and SEPA Instant is less developed.

Which real-time payment scheme is the largest?

UPI, by transaction count. NPCI reported more than 228 billion UPI transactions in 2025, with daily volumes in the hundreds of millions, accounting for a large share of global real-time retail payment volume. Pix is second in scale, with 63.4 billion transactions in 2024, though Pix has achieved higher penetration relative to its market’s population.

Are real-time payments cheaper than cards for merchants?

Generally yes. Instant bank transfers avoid card interchange and typically cost merchants significantly less per transaction, which is a primary reason Brazilian merchants shifted volume to Pix so quickly. The saving is most meaningful in low-margin categories and on high-frequency, low-value transactions.

Does SEPA Instant work across borders?

Within the eurozone, yes. SEPA Instant natively supports instant euro transfers across a broad set of European countries, which makes it unusual among these schemes, most of which are purely domestic. Its limitation is currency: it handles euro only, so it cannot serve non-euro corridors.

Should merchants support FedNow now?

For most, not yet. FedNow volumes remain small and skew heavily toward high-value business use instead of consumer purchases, so building acceptance ahead of consumer demand would be premature. Cards and wallets remain where United States volume sits. Monitoring the scheme’s consumer-to-business development is the reasonable position.

Where this leaves merchants

The four schemes share a technical promise and diverge almost completely on adoption. Pix and UPI became primary payment methods because both markets had large underbanked populations, high smartphone use, and central infrastructure designed for consumers from the start. FedNow and SEPA Instant were built into mature card markets where consumers already had a payment habit that worked, and they are growing as infrastructure rather than as consumer products.

For merchants, this makes real-time payments four separate market-by-market decisions instead of a single trend to adopt or ignore, with two already settled and two still open. The businesses handling this well are the ones that can add a method where adoption tips, without that decision costing an engineering quarter each time.

Gr4vy connects merchants to more than 400 payment providers and methods through a single integration, including Pix and Pix Automático in Brazil, so adding a local scheme is a configuration change. To talk through which methods your markets actually need, get in touch with our team.

An acquiring bank sits on the merchant side of a card payment.

When a customer pays by card, the acquirer helps connect the merchant to the card networks, participates in authorization and settlement, and takes responsibility for the merchant relationship within that payment system. It is often called an acquiring bank, merchant acquirer, merchant bank or simply an acquirer.

Most businesses do not spend much time thinking about which institution fills that role. Their relationship may be packaged through a payment service provider (PSP), processor or payment facilitator, making the acquirer almost invisible during day-to-day payment operations.

That changes when payments become more complex.

Approval rates vary between markets. Processing costs increase. A business expands internationally. One acquirer performs better for a particular set of cards than another. Settlement terms start affecting cash flow. Suddenly, acquiring is no longer plumbing that can be ignored.

Understanding what an acquiring bank does is the first step toward understanding why the choice of acquirer can affect payment performance, cost and international expansion.

What is an acquiring bank?

An acquiring bank is the financial institution on the merchant side of a card transaction. It enables merchants to accept card payments and connects their transactions into card networks such as Visa and Mastercard.

The word “acquiring” refers to the institution acquiring card transactions from merchants and introducing them into the card payment system.

In the traditional four-party card model, the main participants are the cardholder, merchant, issuing bank and acquiring bank. A card network connects the issuer and acquirer and establishes the rules under which transactions take place.

The issuing bank has the relationship with the cardholder. The acquiring bank has the relationship with the merchant.

That merchant relationship can take different forms.

A large enterprise might have a direct agreement with one or several acquirers. Another business might access acquiring through a PSP or payment facilitator that packages multiple payment services into a single commercial relationship.

This distinction is important because an acquiring bank is not simply any company that processes a card transaction. An acquirer participates in the card-network framework as an acquiring institution and takes on responsibilities associated with the merchants it supports.

It also does not mean every merchant has a conventional standalone bank account at the acquirer. Modern PSP and payment-facilitator models can abstract much of the underlying acquiring relationship from the merchant.

You can read more about the merchant account relationship and how it differs from the technology used to transmit payment information.

Where does the acquirer sit in a card payment?

The role becomes easier to understand when following a card transaction from checkout to settlement.

A customer enters their card details and submits a payment. The merchant’s payment infrastructure sends an authorization request toward its processor or acquirer. That request travels through the appropriate card network to the bank that issued the customer’s card.

The issuing bank then evaluates the transaction.

It can consider whether the account is valid, whether sufficient credit or funds are available, authentication results, fraud signals and its own risk rules. It then approves or declines the payment.

That response travels back through the card network toward the acquiring side and eventually reaches the merchant’s checkout.

An approval does not mean all of the money has already moved.

After authorization, the transaction goes through clearing and settlement. Transaction information is exchanged between the parties, financial obligations are calculated and funds are settled between the issuing and acquiring sides of the card system. The merchant then receives settlement according to its agreement with its acquiring provider.

The acquirer therefore operates at a critical point in both the information flow and the movement of funds.

What does an acquiring bank do?

An acquirer’s responsibilities extend well beyond forwarding card transactions.

Underwriting and onboarding merchants

Before entering into a direct acquiring relationship, the acquirer needs to understand the business it is agreeing to support.

That can include reviewing the merchant’s business model, products or services, expected payment volume, average transaction value, countries of operation, chargeback history and exposure to fraud.

Industry matters too. Two businesses with identical payment volumes can present very different risks if one sells ordinary consumer goods and another operates in a category associated with high refund rates, long fulfillment periods or elevated chargeback exposure.

This underwriting process helps determine whether the acquirer wants the merchant in its portfolio and under which commercial conditions.

Those conditions may include pricing, settlement schedules, transaction limits or reserves depending on the merchant’s risk profile.

Connecting merchants to card networks

Acquirers provide the merchant side of the connection into card-network infrastructure.

When a transaction is submitted, the acquiring side ensures the authorization request reaches the appropriate network in the required format. The network then routes it to the issuer responsible for deciding whether the transaction should be approved.

The acquirer also operates according to the rules of the card networks it supports.

This is one reason “acquirer” has a more specific meaning than “payment processor.” A company can provide technical payment-processing services without itself holding the acquiring role within a card network.

Supporting authorization

The issuer ultimately makes the approval or decline decision in a standard card transaction, but the acquiring setup still matters.

The acquirer and processor help ensure the authorization request reaches the issuer correctly, with the right transaction data and configuration. Poor transaction data, incorrect merchant configuration or technical problems in the payment path can all hurt performance before an issuer has a good opportunity to approve the payment.

At scale, businesses therefore look beyond whether an acquirer can technically process a card. They monitor how transactions actually perform through each acquiring relationship.

Clearing and settlement

Authorization answers whether a transaction can proceed. Settlement deals with the financial movement that follows.

The acquirer participates in clearing and settlement with the card network and issuing side, then settles proceeds to the merchant according to the commercial agreement.

Settlement does not always happen immediately after a successful authorization. Timing varies according to provider, geography, currency, business model and contract.

For high-volume businesses, even relatively small differences in settlement timing can affect working capital.

Managing merchant risk

An acquirer takes on financial and network risk by sponsoring or supporting merchants within the card system.

For example, a merchant could accept payment and later become unable to honor refunds or chargebacks. Excessive fraud or dispute activity can also create financial exposure and card-network consequences.

For this reason, acquiring does not end after initial underwriting.

Acquirers continue to monitor their merchant portfolios for fraud, disputes, chargeback levels and other indicators of risk. A meaningful change in transaction behavior can result in closer monitoring or changes to the acquiring relationship.

Handling chargebacks and disputes

The acquirer also represents the merchant side of the card dispute process.

When a cardholder disputes a transaction through their issuing bank, the dispute moves through the network toward the acquiring side. The merchant can then be asked to accept the chargeback or provide evidence supporting the original transaction.

The acquirer passes relevant dispute information between the merchant and the card-network process and operates within the network’s deadlines and rules.

This is another area where acquirer quality can matter operationally. Reporting, dispute tooling, notification speed and support all affect how efficiently a merchant can respond.

Supporting compliance

Acquirers operate within card-network rules and payment-security requirements. They also have responsibilities related to the compliance of the merchants in their portfolios.

The exact responsibilities vary by network, market and commercial setup, but areas such as PCI DSS, fraud monitoring, merchant identification and card-network compliance all intersect with the acquiring relationship.

For the merchant, this means an acquiring agreement is more than a contract for transaction processing. It places the business inside a regulated and rules-based payment ecosystem.

Acquiring bank vs. issuing bank

The simplest way to distinguish an acquiring bank from an issuing bank is to look at which side of the transaction each represents.

Suppose a customer uses a credit card issued by Bank A to buy something from a merchant that uses Bank B as its acquirer.

Bank A is the issuer. It provided the customer’s card and determines whether that customer’s transaction should be approved.

Bank B is the acquirer. It supports the merchant’s card acceptance and receives the transaction on the merchant side of the network.

The card network connects the two.

Our guide to what a card issuer does covers the other side of this relationship in more detail.

Acquiring bank vs. payment processor vs. PSP

Acquirers, processors and PSPs are frequently treated as interchangeable terms because one company can perform several of these roles.

The functions themselves are different.

An acquiring bank is the institution responsible for the merchant’s acquiring relationship within the card-payment system.

A payment processor provides the technology and infrastructure used to process transactions. It can transmit authorization messages, connect with card networks and support clearing and settlement processes.

A processor can work for an acquirer without being the acquirer itself.

A payment service provider, or PSP, packages payment capabilities for merchants. Depending on the provider, this can include gateway technology, processing, acquiring access, fraud tools, alternative payment methods, reporting and other services.

Some PSPs are also acquirers in certain markets. Others connect merchants to separate acquiring institutions.

A payment facilitator introduces another variation. Instead of every smaller business forming a direct acquiring relationship, the payment facilitator can onboard sub-merchants under its sponsored arrangement with an acquirer.

This is why a payment stack cannot always be understood by looking at company names alone. One provider may occupy several layers.

For a deeper breakdown, see card networks versus payment processors, what a PSP does and the payment processor’s role.

How the acquirer affects approval rates and cost

The acquiring relationship becomes much more visible when a business starts looking closely at payment performance.

An acquirer cannot force an issuer to approve a transaction. The issuer owns that decision.

But the path a transaction takes to that issuer can still influence the outcome.

Acquirers and approval rates

Different acquirers can produce different approval-rate results for the same business.

There are several possible reasons.

An acquirer may have stronger domestic coverage in a particular country. It may support local routing or transaction configurations more effectively. The quality and completeness of authorization data can differ. Processing reliability and network connectivity can vary. Different providers can also have different capabilities around retries, authentication and transaction optimization.

For an international business, local acquiring can be particularly relevant.

A transaction processed domestically can sometimes produce better results than one acquired cross-border, depending on the market, issuer, card type and payment setup. Local currency presentation and local routing can also remove some sources of friction.

That does not mean local acquiring automatically produces higher approval rates. Performance should be tested with the merchant’s actual transaction mix.

This is why acquiring across international markets is an important part of lifting approval rates for businesses operating across several regions.

Acquirers and payment costs

Acquiring also contributes directly to the cost of accepting cards.

A card transaction can include interchange paid to the issuer, card-network fees, acquiring charges, processor charges and other fees depending on the payment stack and transaction.

The acquiring component can vary according to transaction volume, geography, card type, channel, merchant category, risk profile and commercial agreement.

Cross-border transactions can introduce additional costs. Currency conversion and international settlement can add another layer.

As volume grows, businesses should therefore look beyond the headline percentage quoted in an acquiring contract.

They need to understand the effective cost of different transaction types, how fees change across markets and whether the acquiring setup continues to make sense as the business grows.

That makes optimizing acquirer fees a payment-performance exercise rather than a simple procurement negotiation.

How to choose an acquiring bank

There is no universally best acquiring bank. The right choice depends on where a business operates, what it sells and how its customers pay.

Market coverage

An acquirer should support the countries, currencies, card networks and transaction types the business needs.

For a company operating internationally, “global coverage” deserves closer examination.

A provider may technically process transactions from a country without offering domestic acquiring there. Another may have strong local acquiring in a limited number of markets.

Those differences can matter for payment cost and performance.

Approval-rate performance

Businesses should evaluate acquiring performance using their own transaction data.

An acquirer that performs well for domestic debit cards in one country may not lead on international credit cards in another. Performance can also vary by issuer, card network, transaction value and channel.

This makes averages less useful than segmented data.

Pricing

Acquirer pricing needs to be assessed as part of the full processing cost.

Businesses should understand which charges are acquiring markup, which are interchange or network fees, how cross-border transactions are priced, what currency-conversion charges apply and whether additional fees exist for refunds, disputes or other services.

Transparent pricing makes it much easier to compare providers accurately.

Risk appetite

Acquirers do not all assess industries in the same way.

Some specialize in certain merchant categories or transaction models. Others may impose stricter limits or avoid particular verticals altogether.

A business with subscriptions, high average order values, future delivery or elevated chargeback exposure may therefore receive very different commercial terms from different acquirers.

The relationship needs to fit the merchant’s actual risk profile rather than only its current payment volume.

Settlement terms

Settlement timing can have a material impact on cash flow.

Businesses should understand how frequently funds are settled, whether reserves or delays apply, which currencies can be settled and where those funds can be paid.

For a multinational business, settlement requirements can also affect treasury and foreign-exchange decisions.

Reliability and support

An acquirer is part of the path every transaction using that acquiring relationship needs to traverse.

Reliability therefore matters.

Businesses should consider processing uptime, incident response, reporting quality, dispute support and the speed at which operational issues are resolved.

The impact becomes especially clear during an outage. If every card transaction depends on one acquiring path, an acquiring or processing failure can become a checkout-wide problem.

Do you need more than one acquirer?

For smaller businesses, one acquiring relationship may be sufficient.

The calculation changes as transaction volume and geographic coverage grow.

Large businesses may work with several acquirers so they can process transactions locally in different countries, negotiate different commercial arrangements, reduce dependency on a single provider or route transactions according to performance.

A multi-acquirer setup also creates the possibility of comparing approval rates and costs instead of treating one provider’s performance as the baseline.

The challenge is complexity.

Every additional acquiring or processing connection can introduce another integration, contract, set of credentials, reporting format and operational dependency.

Payment orchestration provides a way to manage those connections through a common layer. Transactions can be routed between providers according to geography, payment method, cost, performance or other rules without hard-coding one acquiring path into the checkout.

For larger businesses, using more than one acquirer can therefore become a deliberate performance and resilience strategy rather than simply the result of adding providers over time.

Frequently asked questions

What is an acquiring bank in simple terms?

An acquiring bank is the financial institution on the merchant side of a card payment. It enables the merchant to accept card transactions and participates in authorization, clearing and settlement through the card networks.

Is an acquirer the same as an acquiring bank?

Yes. “Acquirer,” “acquiring bank,” “merchant acquirer” and “acquiring financial institution” are commonly used to describe the same core role. The exact terminology can vary between payment providers and card networks.

What does an acquirer do in a card transaction?

The acquirer provides the merchant-side connection to the card-payment system. It receives transactions from the merchant or its payment provider, helps route authorization requests toward the card network, participates in clearing and settlement, manages merchant risk and supports processes such as disputes and chargebacks.

What is the difference between an acquiring bank and an issuing bank?

The acquiring bank serves the merchant side of the transaction. The issuing bank serves the cardholder side. The issuer provides the customer’s card and decides whether to approve or decline the transaction, while the acquirer enables the merchant to accept it.

Who pays the acquiring bank?

The merchant ultimately pays for acquiring services through the commercial fees associated with accepting card transactions. The exact fee structure varies according to the provider and pricing model.

Is an acquiring bank the same as a payment processor?

No. An acquirer holds the merchant-side acquiring role within the card system. A processor provides technology that handles payment transactions and communications between the relevant parties. One company can provide both services, which is why the terms are sometimes confused.

Is an acquiring bank the same as a PSP?

Not necessarily. A PSP provides payment services to merchants and may bundle gateway, processing, acquiring access and other capabilities. Some PSPs also operate as acquirers in particular markets, while others work with separate acquiring banks.

Does the acquiring bank approve card payments?

The issuing bank normally makes the final approval or decline decision. The acquiring side sends the authorization request through the appropriate payment infrastructure and returns the issuer’s response to the merchant.

Can a merchant have more than one acquiring bank?

Yes. Larger businesses often use multiple acquirers across countries, currencies or transaction types. They may also route transactions between acquirers to improve resilience, manage costs or improve payment performance.

How does an acquiring bank make money?

Acquirers earn revenue through the fees charged for acquiring and related payment services. Pricing structures vary and may include transaction-based charges, percentage markups, fixed fees or additional charges for services such as currency conversion and dispute handling.

Why your acquiring relationship matters

Acquiring can be easy to ignore when every transaction runs through a single provider and payments are working as expected.

At scale, it becomes much harder to treat the acquirer as a commodity.

The acquiring relationship can affect where transactions are processed, how quickly funds settle, what card acceptance costs, how disputes are handled and how reliably payments continue during provider problems. Different acquirers can also produce different results across countries, issuers and card types.

That makes the question less about finding one universally “best” acquiring bank and more about building an acquiring setup that matches the business.

Gr4vy gives businesses a single orchestration layer for connecting and managing multiple payment providers. With routing controlled independently from any individual provider, merchants can change or add acquiring paths without rebuilding their checkout around a single acquirer.

As payment volume, geography and complexity grow, that flexibility makes acquiring something a business can actively optimize rather than simply inherit from its first payment provider.

Contact Gr4vy to learn how payment orchestration can help you build a more flexible multi-acquirer payment strategy.

Brazil is a market where a card-first payment strategy can quickly fall short.

Pix, the instant payment system launched by Banco Central do Brasil in November 2020, has changed how people move money and pay businesses. More than 170 million individuals now use Pix, representing around 80% of Brazil’s population, and more than 7 billion Pix transactions were made in January 2026 alone.

Its impact extends directly to ecommerce. In 2025, Pix accounted for 42% of ecommerce transactions in Brazil, overtaking credit cards according to data cited by Gr4vy in its 2026 Pix Automático announcement.

That does not mean cards have become unimportant. Brazil still had 253.8 million active credit cards at the end of the second half of 2025, and paying for purchases in installments remains deeply embedded in consumer behavior.

For international businesses, the result is a payment market that looks quite different from the US or much of Europe. Pix, credit card installments, Boleto Bancário, wallets, local acquiring, Brazilian reais and payment-provider coverage all affect how a checkout performs.

Understanding these differences is essential when deciding which payment methods in Brazil to support and how to build the infrastructure behind them.

How Brazilians pay online in 2026

Brazil has developed one of the world’s most active digital payment markets. Pix sits at its center, but consumers move between instant bank payments, cards, installments, wallets and Boleto depending on what they are buying and how they want to pay.

That makes payment-method preference more contextual than a simple ranking.

Someone buying a relatively inexpensive item on their phone may choose Pix because the transaction can be completed immediately through their banking app. A customer making a much larger purchase may prefer a credit card because it allows the cost to be divided across several monthly payments. A recurring service faces another set of requirements entirely.

This is why businesses expanding internationally need to understand how payment preferences differ by country rather than treating cards and a handful of global wallets as a universal checkout.

Brazil is also highly connected. The U.S. International Trade Administration estimates that more than 94% of the Brazilian population uses the internet and describes Brazil as the world’s fifth-largest internet economy.

That digital reach has created favorable conditions for mobile-first payment methods. Pix was designed around instant account-to-account transfers that can be initiated through a smartphone, while digital banking and wallet providers have made managing different payment methods from a phone increasingly familiar.

The important point for an ecommerce business is that localization in Brazil goes deeper than translating the checkout and displaying prices in reais. The payment mix itself needs to reflect how Brazilians actually transact.

Pix: Brazil’s leading payment method

Pix is an instant payment system created and managed by Banco Central do Brasil. It allows funds to move between participating accounts in seconds and operates 24 hours a day, including weekends and holidays.

Its adoption has been unusually fast. By the fifth anniversary of Pix in November 2025, Banco Central reported nearly 170 million users. The system had processed BRL 11 trillion in transactions during 2024 alone.

For anyone entering Brazil, Pix is no longer an alternative payment method sitting beside the main checkout options. For many transactions, it is the expected way to pay.

How Pix payments work

At checkout, a business creates a Pix payment request. The customer can typically complete it by scanning a QR code or using a Pix copy-and-paste code in their bank or payment app.

The customer authenticates the transaction within that environment. Once approved, the payment moves through the Pix infrastructure and the recipient receives the funds almost immediately.

This changes the checkout flow compared with a card transaction. There is no card number to enter, expiry date to validate or card authorization request to send through an issuer and card network.

Banco Central designed Pix for a broad range of uses, including ecommerce and mobile commerce, person-to-person payments, business payments, bills and government payments. Its payment messages also support information that can help businesses reconcile transactions received through the system.

For an online seller, the practical advantage is that the payment status can be confirmed quickly. Inventory, order confirmation and fulfillment logic can respond to that confirmation rather than waiting for a slower bank-transfer process.

Why Pix became so popular

Pix addressed several points of friction at once.

It made immediate transfers available around the clock. It allowed customers to initiate payments using familiar identifiers and QR codes. It was built into banking and payment apps consumers were already using.

Its reach is now difficult to separate from Brazil’s broader financial system. Banco Central has linked Pix adoption with the financial inclusion of more than 70 million people who had not previously used traditional electronic transfers.

For ecommerce, familiarity matters. Asking Brazilian customers to use Pix does not require introducing an unfamiliar fintech product at checkout. The payment happens through institutions and apps that are already part of their financial lives.

Pix costs and settlement compared with cards

Pix can also change the economics of accepting a payment.

A traditional card transaction involves several participants and potentially multiple fees. Pix uses an account-to-account model with a different cost structure and fewer steps between payer and recipient.

That does not mean Pix is always free for businesses. Banco Central allows financial and payment institutions to charge business customers for Pix services, and institutions must disclose those charges. Actual merchant costs therefore depend on the provider and commercial agreement.

The more important difference is structural. Businesses can evaluate Pix alongside cards based on payment cost, conversion, customer preference, settlement and operational requirements instead of assuming the same method should handle every transaction.

Pix Automático for recurring payments

For years, one of the clearest limits of Pix in ecommerce was recurring billing. Standard Pix transactions generally required the customer to actively approve the payment.

Pix Automático changes that model.

With Pix Automático, the payer grants an authorization once. A business can then submit future recurring charges according to that authorization, while the customer’s financial institution schedules and executes payments under the agreed rules. Banco Central positions the system for recurring expenses such as subscriptions, insurance, schools, gyms, utilities and other regular bills.

That opens Pix to business models where cards have historically been much easier to use.

Gr4vy added support for Pix Automático for recurring payments through its dLocal integration in May 2026. Once a customer provides the initial authorization, merchants can manage recurring Pix transactions and mandates within their orchestrated payment environment.

For subscription businesses entering Brazil, this matters. Supporting local payment preferences no longer has to mean restricting Pix to one-time purchases while pushing recurring customers toward cards.

Credit cards and installments in Brazil

Pix may lead the market, but credit cards remain central to Brazilian commerce.

Banco Central reported 253.8 million active credit cards at the end of the second half of 2025.

One reason cards remain important is parcelamento, the practice of dividing a purchase into monthly installments.

Installments are common enough that a business can lose more than a payment method when it fails to support them. It can remove a purchasing option customers rely on to make more expensive products affordable within their monthly budget. The U.S. International Trade Administration identifies monthly installment payments as a key feature for Brazilian consumers.

Why parcelamento matters

Brazilian card installments are especially relevant for higher-value purchases.

Instead of paying the full purchase price in a single billing cycle, a customer may be offered several installments at checkout. A R$1,200 purchase, for example, might be presented as six monthly payments rather than one R$1,200 charge.

From the customer’s perspective, the decision is therefore not simply “card or Pix.” The question can become “pay R$1,200 now with Pix or spread the purchase over several card payments.”

That changes how payment-method performance should be analyzed.

Pix may have a strong overall transaction share while card installments remain highly important for a particular product category, average order value or customer segment.

Businesses unfamiliar with the model should first understand how installment payments work and then confirm exactly how their Brazilian acquirer or payment provider supports parcelamento.

How card installments work for merchants

Installment implementation depends on the acquiring and payment-provider setup.

The customer sees the number of installments available during checkout and selects an option. Behind that interface, the merchant needs a provider capable of processing the transaction correctly under the relevant Brazilian card and acquiring arrangement.

This is one place where copying a checkout configuration from another market can cause problems. A card integration that technically accepts a Brazilian credit card does not automatically recreate the local experience customers expect.

Businesses should decide how many installments to offer, whether interest applies, how installment options interact with order value and how those transactions appear in reporting and reconciliation.

Pix versus cards for higher-value purchases

Businesses should resist treating Pix adoption as evidence that cards can be pushed to the side.

Pix is strong when a customer wants an immediate account-to-account payment. Cards can serve a different financial need by giving customers access to credit and installment options.

That means the right payment mix depends partly on ticket size.

For lower-value purchases, an immediate Pix payment may be an easy choice. At higher values, the ability to split the purchase can materially change the appeal of a card.

The useful metric is therefore not simply which payment method has the greatest national market share. Businesses need to see conversion, average order value, payment cost and approval performance for their own transactions.

Boleto Bancário

Boleto Bancário has been part of Brazil’s payment landscape for decades.

A boleto is a standardized payment document that contains the information required to pay a bill or purchase. Historically, customers could pay boletos through banks, online banking, ATMs and other authorized channels.

For ecommerce, Boleto offered an important option to customers who did not have a credit card or did not want to use one online.

Its role has changed as Pix has expanded.

Pix gives consumers many of the benefits that made Boleto useful while adding immediate payment confirmation. A traditional boleto does not offer the same instant experience, creating more time between checkout and confirmation and increasing the possibility that a customer generates the boleto but never completes the payment.

Boleto has not disappeared, however. It continues to be part of Brazil’s payment infrastructure and can still be relevant for particular customer groups, billing scenarios and business models.

The distinction between the two methods has also become less rigid. Banco Central modernized boleto rules in 2025 so that a boleto can include a QR code allowing the customer to make the payment through Pix.

That is a useful example of how Brazil’s local payment infrastructure is evolving rather than simply replacing one method with another.

For international businesses, the broader lesson is why local payment methods versus international card schemes cannot be assessed only by global brand recognition. A locally familiar method may solve a specific checkout, access or billing problem that an international card does not.

Digital wallets and other payment methods in Brazil

Digital wallets also form part of the Brazilian checkout.

Local platforms such as Mercado Pago have helped make wallet-based payments familiar, while bank apps increasingly bring several financial functions into a single mobile experience.

The category can be difficult to separate neatly from the underlying payment rails.

A customer may think of a wallet or banking app as the way they pay, while the actual transaction uses a stored card, account balance or Pix. For a merchant, those distinctions matter because each route can produce different costs, authorization behavior, settlement processes and data.

This is another reason a payment strategy based on a static list of logos can be misleading.

Businesses should look at which methods customers select, how those payments actually move, where transactions fail and whether adding another visible option creates incremental conversion or simply shifts volume between methods already available.

How to accept payments in Brazil as an international merchant

Knowing which payment methods Brazilians use is only the first part of the problem.

The next question is how an international business gives customers access to those methods without creating an isolated Brazilian payment stack that becomes difficult to operate.

Provider coverage, local acquiring, currency, settlement, local requirements and reporting all need to be considered.

Local entity and payment-provider considerations

An international merchant does not necessarily have one universal route for accepting Brazilian payment methods.

Requirements depend on the payment method, provider, acquiring arrangement and business model. Some providers specialize in giving international businesses access to local payment methods and handling parts of the cross-border flow. Other setups may involve a local entity or local acquiring relationship.

This should be established before checkout development begins.

A business can otherwise reach the end of an integration only to discover that the desired local method is unavailable under its existing contract, settlement country or legal structure.

Pix is a good example. The consumer-facing experience may look simple, but an international merchant still needs a payment provider or partner that gives it appropriate access to Pix acceptance.

Local versus cross-border acquiring

Cards introduce another decision.

With cross-border acquiring, a transaction from a Brazilian-issued card may be processed through an acquiring relationship outside Brazil. Local acquiring processes the transaction through a domestic setup.

The distinction can affect how a transaction is routed, the currencies involved, processing costs, settlement and authorization performance.

There is no rule that every transaction must use the same arrangement. Businesses with sufficient volume may use different acquiring relationships based on market and transaction characteristics.

Understanding local versus cross-border acquiring is therefore part of building a Brazilian card strategy rather than a separate infrastructure discussion.

Accepting Pix

To accept Pix online, the checkout needs to connect to a provider that supports the payment method and the merchant’s operating model.

Gr4vy currently supports one-off Pix payments in Brazil through Adyen and recurring Pix Automático payments through dLocal.

With an orchestration layer, local methods can sit alongside cards and other payment services rather than requiring the merchant’s ecommerce platform to maintain separate payment logic for every provider.

That becomes increasingly useful as the payment stack grows. The business can introduce a Brazilian method while keeping payment data, routing logic and transaction visibility within the broader payment environment.

Currency, settlement and reconciliation

Brazilian customers generally expect a localized purchase experience, including clear pricing in Brazilian reais.

Behind that experience, an international merchant needs to understand what happens after the customer pays.

Which currency is processed? Which currency is settled? Does conversion happen before or after settlement? Which provider handles foreign exchange? How quickly are funds available? How are refunds returned? How does the finance team reconcile Pix, cards, installments and Boleto in its reporting?

These questions have direct operational consequences.

Pix can confirm in seconds. A card has its own authorization, capture and settlement lifecycle. Boleto may behave differently again. Installment transactions introduce information that finance teams need to understand when matching customer purchases with payment and settlement records.

The best practices for international payments therefore include the processes behind the checkout as well as the methods displayed to customers.

Which payment methods should you offer in Brazil?

There is no single payment mix that works for every business in Brazil.

Pix and cards are strong starting points for most ecommerce operations, but the weight given to each should reflect what the business sells and how customers buy it.

For everyday ecommerce purchases, Pix provides a locally familiar, immediate payment experience. Cards remain important for customers who prefer card rewards, credit or a familiar stored credential.

For higher-ticket retail, card installments deserve particular attention. A checkout that accepts cards but does not provide the installment experience customers expect may technically support the payment method while still being poorly localized.

For subscriptions and memberships, cards remain relevant, but Pix Automático creates a new option for recurring bank-based payments. Businesses that previously excluded Pix from subscription checkout because of repeated customer authorization can now reassess that decision. Banco Central designed Pix Automático specifically to automate recurring charges after the customer provides an initial authorization.

Boleto can remain useful where the customer base or billing model supports it, although businesses should measure actual usage rather than include it only because it has historically been associated with Brazilian ecommerce.

The same principle applies to wallets. Add them where customer demand and performance justify the integration.

For global companies, the infrastructure behind these choices matters. Connecting each Brazilian payment provider directly to the checkout can create another set of integrations, reporting workflows and dependencies for engineering teams to maintain.

Payment orchestration provides another model. Businesses can connect providers through a common layer and change the payment mix as local requirements evolve. That makes adding local methods without separate integrations easier as the company enters new countries or changes providers.

The objective is not to show every possible payment method. It is to give Brazilian customers the right options for the transaction they are trying to make.

Frequently asked questions

What is the most popular payment method in Brazil?

Pix is Brazil’s most widely used electronic payment method by transaction count and has more than 170 million individual users. Banco Central reported more than 7 billion Pix transactions in January 2026. In ecommerce specifically, data cited by Gr4vy put Pix at 42% of Brazilian ecommerce transactions in 2025.

Is Pix more popular than credit cards in Brazil?

Pix has overtaken cards by transaction count and has become central to Brazilian ecommerce, but credit cards remain widely used. Brazil had 253.8 million active credit cards at the end of the second half of 2025. Cards are particularly important for purchases where customers want to pay in installments.

Can international businesses accept Pix?

Yes. International businesses can accept Pix when they work with a payment provider or payments setup that supports Pix for their business model and operating structure. The exact requirements depend on the provider. Gr4vy, for example, supports one-off Pix transactions through Adyen and Pix Automático through dLocal.

Do you need a Brazilian bank account to accept Pix?

Not in every commercial setup. Cross-border payment providers can enable international merchants to offer Brazilian payment methods without requiring the merchant to build the same banking and acquiring setup as a domestic company. Requirements vary by provider, settlement arrangement and legal structure, so businesses should confirm them before integration.

What is Boleto Bancário?

Boleto Bancário is a standardized Brazilian payment document used to pay for goods, services and bills. Customers can pay a boleto through supported banking and payment channels. Updated Banco Central rules also allow boletos to include QR codes for payment through Pix.

Why are installments popular in Brazil?

Installment payments allow customers to spread the cost of a purchase over several monthly payments and are a well-established part of Brazilian card usage. They can be particularly relevant for higher-value purchases where paying the entire amount immediately would be less attractive. The U.S. International Trade Administration describes monthly installments as a key feature for Brazilian consumers.

Does Pix support recurring payments?

Yes. Pix Automático allows recurring payments after the customer provides an initial authorization. Businesses can then submit recurring charges according to that mandate without asking the customer to manually approve every payment.

What is the difference between Pix and Pix Automático?

A standard ecommerce Pix payment is typically initiated and approved by the customer for an individual transaction. Pix Automático adds a mandate-based model for recurring billing. The payer authorizes the arrangement once, after which future payments can be executed automatically under the conditions of that authorization.

Are credit cards widely used in Brazil?

Yes. Credit cards remain one of Brazil’s major payment methods despite the rapid growth of Pix. Banco Central recorded 253.8 million active credit cards at the end of the second half of 2025.

What currency is used for ecommerce payments in Brazil?

Brazil’s currency is the Brazilian real, or BRL. International businesses selling to Brazilian customers should consider displaying and accepting local currency where their payment setup allows it, while also reviewing how their provider handles foreign exchange and settlement.

Build a payment strategy for Brazil

Entering Brazil requires more than enabling international cards and translating a checkout.

Pix has reshaped everyday payments. Installments continue to influence how Brazilians use credit cards, particularly for larger purchases. Boleto remains part of the local ecosystem, while Pix Automático is extending instant payments into subscriptions and other recurring business models.

The right setup depends on the customers you serve, what you sell and how your payment providers operate in Brazil.

Gr4vy gives businesses a way to manage those choices through a single payment orchestration layer, including support for one-off Pix payments through Adyen and Pix Automático through dLocal. As payment preferences or provider requirements change, merchants can adapt their payment stack without rebuilding the checkout around each individual provider.

If Brazil is part of your expansion plans, contact Gr4vy to discuss how to build a localized payment setup around the methods Brazilian customers actually use.

A payment aggregator is a company that lets businesses accept card and digital payments without opening their own merchant account, by processing their transactions under one shared master merchant account instead. Stripe, Square, and PayPal are the best-known examples: a business signs up, gets approved in minutes, and starts taking payments the same day, because the aggregator has already done the heavy lifting of securing the acquiring relationship and pooling many businesses under its own account.

That speed and simplicity is why aggregators now onboard a large share of the businesses accepting payments online. It also comes with tradeoffs that matter as a business grows. This guide explains what a payment aggregator is, how the model works, who the major examples are, how it compares to a traditional merchant account, and where its benefits give way to limits.

What is a payment aggregator?

A payment aggregator is a payment service provider that aggregates many businesses, its sub-merchants, under a single master merchant account rather than setting each one up with its own account at an acquiring bank. When a business signs up with an aggregator, it is onboarded as a sub-merchant under the aggregator’s umbrella and begins accepting payments almost immediately, skipping the traditional merchant account application, underwriting, and approval process that can take days or weeks.

The model exists to remove friction. Opening a dedicated merchant account historically meant an application to an acquiring bank, a credit and risk review, and a wait before approval. Aggregators collapse that into a quick signup because the aggregator, not the individual business, holds the relationship with the acquirer and assumes much of the associated risk. The business trades some control and some margin for the ability to start taking payments right away.

How do payment aggregators work?

A payment aggregator sits between its sub-merchants and the wider card payment system, presenting many businesses to the acquirer as activity under its own master account. The mechanics break down into a few steps.

Onboarding. A business signs up with the aggregator and provides basic details. Instead of a full merchant account underwriting process, the aggregator performs a lighter-weight risk check and approves the business as a sub-merchant, often within minutes.

Processing under the master account. When the sub-merchant takes a payment, the transaction is processed under the aggregator’s master merchant account. To the acquiring bank, the volume flows through the aggregator rather than appearing as a standalone merchant.

Fund flow and payout. The aggregator receives the settled funds from the payment and then pays out to the sub-merchant, typically on a set schedule, after deducting its fees. Because the funds pass through the aggregator, payout timing is set by the aggregator rather than by the business.

Risk and compliance. The aggregator carries responsibility for monitoring transactions, managing fraud and chargeback risk across its pool of sub-merchants, and maintaining PCI DSS compliance for the shared infrastructure. This is part of what the sub-merchant is effectively outsourcing.

Because all the sub-merchants share the aggregator’s master account and, in the pure aggregator model, its merchant identifier, the individual business does not have its own dedicated merchant account or, often, its own unique merchant ID. That shared structure is the defining characteristic of aggregation and the source of both its advantages and its limits.

Payment aggregator examples

The businesses most people already use are payment aggregators, even if the term is unfamiliar.

Stripe onboards businesses through a fast signup and processes their payments under its aggregated model, and is especially associated with online and developer-led integrations. Square does the same for in-person and small-business payments, pairing quick onboarding with point-of-sale hardware. PayPal aggregates a vast number of businesses and individuals, letting them accept payments without individual merchant accounts. Other providers such as Adyen and various regional players operate similar models.

What these examples share is the core promise of aggregation: sign up quickly, skip the traditional merchant account process, and start accepting payments almost immediately, with the provider handling the acquiring relationship and much of the risk and compliance behind the scenes.

Payment aggregator vs traditional merchant account

The clearest way to understand aggregation is to compare it to the alternative it replaced: opening a dedicated merchant account.

A traditional merchant account is an account a business holds directly with an acquiring bank, obtained through an application and underwriting process. It gives the business its own merchant identifier, a direct acquiring relationship, more control over payment operations, often better pricing at higher volumes, and more stable, predictable processing. The cost is a slower, more involved setup and more responsibility on the business.

A payment aggregator gives the business none of its own dedicated account but near-instant onboarding, a simple flat-rate pricing model, and no need to manage an acquiring relationship. The cost is less control, shared risk with other sub-merchants, payout timing set by the aggregator, and pricing that becomes less competitive as volume grows.

The rule of thumb: aggregation optimizes for speed and simplicity at lower volumes, while a dedicated merchant account optimizes for control, stability, and cost-efficiency at higher volumes. Gr4vy’s guide on merchant accounts versus payment gateways covers the merchant-account side of this in more detail.

Payment aggregator vs payment facilitator

These two terms are often used interchangeably, and the confusion is understandable because they are closely related. The short version: a payment facilitator (PayFac) is a specific, formally recognized model under the card networks’ rules, in which the facilitator registers with the card networks and onboards sub-merchants, typically assigning each its own sub-merchant identifier. “Payment aggregator” is the older, broader term for any provider that processes payments for multiple businesses under a master account, historically with everyone sharing a single merchant ID.

In practice, most modern providers people call “aggregators” are also registered payment facilitators, which is why the terms blur together. The technical distinction is mainly in how sub-merchants are identified and in the formal card-network designation the PayFac model carries. For most businesses choosing a provider, the practical experience (fast onboarding, no own merchant account, provider-managed risk) is similar either way.

Benefits and drawbacks of payment aggregators

Aggregation is genuinely useful for the right business, and genuinely limiting for others, so it is worth being clear about both sides.

The benefits are speed and simplicity above all. Onboarding is near-instant, there is no merchant account application to navigate, pricing is usually a simple flat rate that is easy to understand, and the aggregator handles the acquiring relationship, much of the fraud and chargeback risk, and PCI compliance for the shared infrastructure. For a new or small business, this removes most of the barriers to accepting payments.

The drawbacks grow with the business. Because sub-merchants share the aggregator’s master account, one business has little control over payment operations and is subject to the aggregator’s risk decisions, which can include sudden holds or account freezes if the aggregator’s automated risk systems flag activity. Payout timing is set by the aggregator rather than the business. Flat-rate pricing that is convenient at low volume becomes expensive relative to interchange-plus pricing at high volume. And the shared structure offers less stability and less room to optimize authorization rates or route across providers than a business gains once it has its own acquiring relationships.

When a payment aggregator is the right fit

A payment aggregator is usually the right choice for businesses that are starting out, processing modest volume, or that value speed and simplicity over control and cost optimization. For a business that wants to accept payments today without navigating merchant account underwriting, aggregation is hard to beat.

The fit weakens as a business grows. Rising volume makes flat-rate pricing more expensive, the lack of control over risk decisions and payouts becomes a bigger operational exposure, and the inability to route across providers or optimize authorization rates starts to cost real revenue. At that point businesses typically graduate toward their own acquiring relationships and, often, toward managing multiple providers through a payment orchestration layer that routes each transaction for the best cost and approval outcome. Gr4vy’s guide comparing payment orchestration and payment aggregators works through that transition, and its overview of payment orchestration explains the model businesses tend to move toward.

Frequently asked questions

What is a payment aggregator in simple terms?

A payment aggregator is a company that lets businesses accept card and digital payments without opening their own merchant account. It processes many businesses’ transactions under one shared master merchant account, so a business can sign up and start taking payments almost immediately. Stripe, Square, and PayPal are common examples.

How does a payment aggregator work?

The aggregator onboards a business as a sub-merchant under its master merchant account after a light risk check, usually within minutes. When the sub-merchant takes a payment, it is processed under the aggregator’s account, and the aggregator then pays out the funds to the business on a set schedule after deducting fees. The aggregator handles the acquiring relationship, risk monitoring, and PCI compliance for the shared infrastructure.

What are examples of payment aggregators?

Stripe, Square, and PayPal are the best-known payment aggregators, along with providers like Adyen and various regional players. These are companies that onboard businesses quickly and process their payments under an aggregated model, without requiring each business to have its own merchant account.

What is the difference between a payment aggregator and a merchant account?

A traditional merchant account is held directly by a business with an acquiring bank, giving it its own merchant identifier, more control, and often better pricing at scale, but it requires an application and underwriting. A payment aggregator processes the business’s payments under the aggregator’s shared master account, offering near-instant onboarding and simple pricing, but with less control, shared risk, and pricing that becomes less competitive as volume grows.

What is the difference between a payment aggregator and a payment facilitator?

The terms are closely related and often used interchangeably. A payment facilitator (PayFac) is a formally recognized model under the card networks’ rules, in which the facilitator registers with the networks and typically assigns each sub-merchant its own sub-merchant ID. “Payment aggregator” is the older, broader term, historically with all sub-merchants sharing a single merchant ID. Most modern aggregators are also registered payment facilitators, so in practice the experience is similar.

Is a payment aggregator safe?

Reputable payment aggregators maintain PCI DSS compliance and invest heavily in fraud and risk management, so the payment processing itself is secure. The main risk for a business is operational rather than technical: because funds and accounts are managed by the aggregator, a business can be subject to sudden holds or account freezes if the aggregator’s risk systems flag its activity, which is a consideration as processing volume grows.

Why do payment aggregators freeze or hold funds?

Because an aggregator carries the risk for all the sub-merchants pooled under its master account, its automated risk systems monitor for unusual activity, sudden spikes in volume, elevated chargebacks, or patterns associated with fraud. When flagged, the aggregator may hold funds or freeze an account to protect itself and the pool. This is one of the tradeoffs of the shared-account model compared with having a dedicated merchant account.

When should a business move away from a payment aggregator?

A business typically outgrows an aggregator when its volume makes flat-rate pricing expensive, when the lack of control over risk decisions and payouts becomes a real operational exposure, or when it needs to optimize authorization rates and route across multiple providers. At that point businesses usually move toward their own acquiring relationships and often adopt a payment orchestration layer to manage multiple providers.

The bottom line on payment aggregators

A payment aggregator is the fastest way for a business to start accepting payments, because it removes the merchant account application entirely and processes the business under its own shared account. For new and smaller businesses, that speed and simplicity is exactly the right tradeoff, and it explains why the best-known payment brands, Stripe, Square, and PayPal, are all aggregators.

The model’s limits are the mirror image of its strengths. The shared account that makes onboarding instant also means less control, shared risk, aggregator-set payouts, and pricing that grows expensive with volume. As a business scales, those tradeoffs tend to tip the other way, and the business moves toward its own acquiring relationships and, frequently, toward managing multiple providers through payment orchestration to optimize cost and approval rates across all of them.

Gr4vy is a cloud-native payment orchestration platform that connects merchants to more than 400 payment providers and methods through a single integration, for businesses that have grown beyond what a single aggregator can offer. To talk through what comes after an aggregator for your business, get in touch with our team.

(Updated – August 2026)

With customer expectations and the complexity of global payments overwhelming businesses, the need for payment orchestration services is about to scale unimaginably. Gone are the days when all could be bundled through one PSP or standard payment gateway. While payment orchestration consolidates multiple payment methods, it simultaneously routes transactions intelligently, thus enabling global scalability.

With a projection that eCommerce is estimated to top $7 trillion in 2025 alone globally, the need for orchestration to enable operational efficiency, drive costs further down, and improve the customer experience has never been greater.

What is payment orchestration?

Payment orchestration means that companies are joined with various payment service providers, gateways, and financial services to bring all their payments in one place. Payment Orchestration: The “Command Center” Unlike the gateway technology of the Payment Gateway that bridges customers to payment providers, orchestration serves as an “advanced command center” for everything related to payments.

Manage, through one API, the configuration of payment routing, multiple methods of payments, workflow automation, security, and regulatory requirements of the payments, such as PCI DSS. Merchants seek control, cost reduction, and a high approval rate, which is, in simple words, what payment orchestration platforms like Gr4vy work on.

Learn more about payment orchestration.

Top 10 benefits of payment orchestration in 2026

1. Increased payment flexibility and support for multiple payment methods

Today’s consumer expects to pay by the method of their choice, be that credit cards, e-wallets, BNPL, or even cryptocurrencies. In this regard, payment orchestration can enable merchants to offer a wider variety of payment methods without accomplishing the daunting task of complex integrations.

Why It Matters:

• It improves customer satisfaction, with reduced cart abandonment.
• Supports location-dependent payment methods such as iDEAL in the Netherlands and Boleto in Brazil.

Learn more about alternative payment methods.

2. Higher transaction success rate

With payment orchestration, businesses can enable intelligent routing to achieve higher approval rates. Slightly different, if one PSP had declined a transaction, it would automatically switch to retry via another, so fewer of those payments fail.

Why it matters:

• Increased revenue because of reduced payment failures.
• This is failover protection if the first PSP is unable to process the payment.

Explore tips to improve your approval rates.

3. Cost reduction and fee optimization

The higher volume of payments that are processed within a company, the more payment fees increase, including cross-border ones. Payment orchestration helps online merchants reduce their payment fees via availing of lower-fee PSPs or through rerouting with local acquirers.

Why it matters:

• Reduces Interchange, Assessment, and PSP fees
• Route payments to providers with the lowest transaction fees.
• Learn how to save on online payment processing fees.

4. Central payment management

It means that it enables the merchant to run all their payments from one place without necessarily keeping different PSP dashboards. Because of orchestration, all transactions and all KPIs could be viewed from one single point of view.

Why It Matters:

• Real-time transparency into the payment activity.
• Reporting, reconciliation, and dispute management also become easier.

5. Improved data security and compliance towards PCI-DSS.

PCI DSS compliance is mandatory for merchants handling cardholder data. Payment orchestration platforms like Gr4vy handle PCI compliance, enabling businesses to operate more securely without the heavy operational burden.

Why It Matters:

• Eases the pain of PCI DSS certification.
• Offloads the liability of dealing with cardholder data to the orchestration provider.
• Learn more about compliance with PCI DSS.

6. Scaling faster and expanding internationally

The larger an e-commerce business is, the more local payment options are needed, and so is their compliance with local legislations. Payment orchestration allows for seamless scaling into new markets.

Why it matters:

• Support for local payment methods across international markets.
• Help enterprises scale up faster by reducing operational friction.

7. Faster time-to-market for new payment integrations

It takes a few weeks, sometimes even months, before new payment providers are integrated. Payment orchestration allows the option to onboard new PSPs fast due to the existing prebuilt integrations.

Why it matters:

• Least technical debts and time spent on development.
• Merchants can expand into more regions more quickly.

8. Dynamic payment workflows

Furthermore, when it comes to the rules-based workflow, the merchants can customize the unique payment logic. They can set the high-value transaction routing rules with a PSP or include on-the-fly fraud detection for suspicious payments.

Why it matters:

• Operational flexibility for unique logics of paying.
• Provide workflow conditionality without any coding.

9. Enhanced customer experience

Payment friction is among the top causes of cart abandonment. Through one-click payment, quicker checkout, and the ability to support customer-preferred ways of payment, payment orchestration facilitates this.

Why it matters:

• Reduces friction at check-out; increases conversions
• Drives customer loyalty with faster, frictionless payment experiences.
• Learn not to abandon checkout.

10. Reduced compliance hassle and regulatory support

Above all, compliance in matters concerning payment is tough the moment it goes cross-border. It automates compliance in orchestration processes: PCI DSS, PSD2, and GDPR.

Why it matters:

• Releases the regulatory burden from the merchant.
• Ensures operating compliance with ever-evolving regulations across a multitude of regions. 

Learn more about Compliance and Regulations. 

Frequently Asked Questions 

1. What is a payment orchestration platform? 

It’s a place where all the processes around payments are managed centrally. Thus, it can enable the same businesses to connect to several sources of payments, manage payment routing, and optimize transaction flows. 

2. How does the idea of payment orchestration differ from that of a payment gateway? 

The answer is straightforward: a payment gateway is a bridge for the customer and PSPs, while payment orchestration provides the capability to manage multiple PSPs, routes, and means of paying. 

3. How does the payment orchestration help decrease the cost of the payables? 

It guides the routing of the payments towards PSPs, which charge less and helps in negotiating volume in return for better rates. 

4. Why is payment orchestration so important for any e-commerce? 

It improves the success rate of each transaction, reduces part of the costs, and improves the customer experience; it will also enable new trends and changes in regulations. 

5. How can I incorporate payment orchestration into my business? 

For instance, on the Gr4vy platform, a business can integrate with one API and in return, manage PSPs, payment methods, and workflows. 

Payment orchestration stopped being a “nice-to-have” and has grown into a “must” for every business because it resolves all three problems in one stroke-operational efficiency, global growth, and lower payment costs. Advantages abound, from supporting multiple payment methods to added security and compliance; in many ways, payment orchestration shapes the face of 2026 payments. 

Contact Gr4vy today to understand how payment orchestration will increase your success rate, decrease your costs, and future-proof your business for 2026.

(Updated – August 2026)

Payment orchestration is a technology layer that connects a merchant to multiple payment service providers, acquirers, and payment methods through a single integration, and routes each transaction to the option most likely to serve it best. Instead of building and maintaining a separate integration for every provider, a merchant connects once to the orchestration layer and controls how payments are routed, retried, and reconciled across all of them from one place.

That single idea, a control layer sitting between the merchant and its many payment providers, is what the rest of this guide unpacks: what payment orchestration is, how it works step by step, what it is genuinely good for, where its limits are, and how to tell whether a business actually needs it.

What is payment orchestration?

Payment orchestration is the practice of managing multiple payment providers through one unified platform that decides how each transaction is processed. The orchestration layer connects to a merchant’s payment service providers (PSPs), acquirers, gateways, payment methods, and fraud tools, and coordinates them, so the merchant operates one integration and one set of rules rather than a tangle of separate connections.

The category has grown quickly as payments have become more complex. Independent research from Grand View Research valued the global payment orchestration platform market at USD 1,386.9 million in 2023 and projects it to reach USD 6,520.4 million by 2030, a compound annual growth rate of 24.7%. That growth reflects a simple pressure: as businesses add providers, payment methods, and markets, managing each connection separately becomes unsustainable, and a coordinating layer becomes the practical way to keep control.

The essential distinction to hold onto is that orchestration is a layer rather than a processor. It does not replace a merchant’s PSPs or acquirers; it sits above them and decides which one handles each transaction. That is why orchestration is often described as a control layer or a payment orchestration layer, and it is the reason a business can adopt orchestration without abandoning the payment relationships it already has.

How does payment orchestration work?

Payment orchestration works by inserting a coordinating layer between the checkout and the payment providers, and applying rules and real-time data to route each transaction. Following a single payment through the layer shows what it does at each step.

Transaction initiation. A customer chooses a payment method at checkout and confirms the payment. The transaction enters the orchestration layer instead of going directly to a single hard-wired provider.

Routing decision. The orchestration layer evaluates the transaction against the merchant’s rules and live data, weighing factors such as the card type, the customer’s country, the cost of each available provider, and each provider’s recent approval performance. It then selects the provider most likely to approve the transaction at the best cost. This routing logic is the core of orchestration, and Gr4vy’s guide on intelligent payment routing covers how it is built and tuned.

Authentication and fraud checks. Where required, the layer applies authentication such as 3D Secure and passes the transaction through the merchant’s chosen fraud tools before it is sent for authorization.

Authorization. The selected provider sends the transaction to the customer’s issuing bank for approval, and the approve-or-decline response returns through the layer.

Retry and fallback. If the transaction is declined for a reason that another provider might approve, the orchestration layer can automatically retry it through an alternative provider or apply fallback logic, recovering payments that a single-provider setup would simply have lost.

Reconciliation and reporting. The layer records the transaction and consolidates data across every provider into one unified view, so reporting and reconciliation happen in one place instead of provider by provider.

The whole authorization sequence happens in the moment the customer waits, while the routing intelligence and the unified data operate continuously behind it.

What is a payment orchestration layer?

A payment orchestration layer is the technical framework that performs the coordination described above. It is the software that connects to all of a merchant’s providers, holds the routing rules, applies retries and fallback, stores payment credentials in a provider-agnostic way, and unifies reporting. When people refer to a payment orchestration platform, the orchestration layer is the engine inside it doing the work. The layer is what lets a merchant add or change a provider through configuration instead of a new engineering integration each time.

Benefits of payment orchestration

The benefits of payment orchestration come down to a few areas that matter directly to revenue and operations. Each follows from the same underlying capability: routing across many providers instead of depending on one.

Higher authorization and approval rates

Because the orchestration layer can send each transaction to the provider most likely to approve it, and retry declines through an alternative, it recovers revenue that a single-provider setup loses to avoidable declines. As a documented example, the Australian retailer Baby Bunting secured a 2.8% uplift in authorization rates within four months of moving to an orchestrated dual-acquirer setup with failover routing. Gr4vy’s guide on how to increase payment approval rates covers the mechanisms in more depth.

Lower payment processing costs

Routing introduces competition among providers and lets a merchant send each transaction along the lowest-cost path that will still get it approved, using local acquiring to avoid cross-border fees where possible. This turns payment cost from a fixed expense into something the business can actively manage.

Access to more payment methods and markets

The orchestration layer gives a merchant access to a wide range of payment methods, currencies, and local acquirers through one integration. Gr4vy, for instance, connects merchants to more than 400 payment providers, methods, and anti-fraud services. Adding a new method or entering a new market becomes a configuration change instead of a fresh engineering project, which is what makes fast expansion feasible.

Resilience and no single point of failure

Depending on one provider means one point of failure: if it has an outage, payments stop. By connecting several providers and rerouting around any that fail, orchestration removes that single point of failure and keeps payments flowing when a provider degrades. For a business where downtime is lost revenue, this resilience alone can justify orchestration.

Unified data and control

Running many providers separately fragments reporting and forces every change through engineering. Orchestration consolidates data across all providers into one view and lets payments teams build and adjust routing rules without code, which is the operational independence orchestration is meant to deliver.

Payment orchestration platform capabilities

A payment orchestration platform typically bundles the orchestration layer with the tools a merchant needs to run it. The core capabilities to expect are a single integration to many providers and methods; a routing engine that can be configured without code; retry, failover, and fallback logic; provider-agnostic vaulting and tokenization of payment credentials; support for authentication such as 3D Secure; fraud-tool integration; and unified reporting and reconciliation across every connected provider.

Platforms differ in how they are architected, and the architecture has real consequences for security and control. Some platforms run all merchants together in a shared, multi-tenant environment. Others, such as Gr4vy, deploy a dedicated, single-tenant instance for each merchant, which isolates each merchant’s data and payment traffic and gives greater control over data residency and configuration. This distinction matters most for larger merchants and those in regulated markets, where data isolation and sovereignty are genuine requirements rather than nice-to-haves.

What payment orchestration does not solve

It is worth being clear about the limits, because orchestration is sometimes described as if it fixes everything, and it does not. Orchestration coordinates and routes payments; it does not, by itself, do the following.

It does not eliminate the underlying costs of the payment providers themselves; each provider’s fees still apply, and orchestration manages how they are used instead of removing them. It does not replace a merchant’s need for acquiring relationships or a merchant account. It cannot approve a transaction that every available provider would decline for a legitimate reason, such as genuinely insufficient funds. And it does not run itself: getting value from orchestration requires configuring the routing rules thoughtfully and maintaining them as provider performance changes. Understanding what orchestration does not do is as important as understanding what it does, because it sets realistic expectations for what adopting it will and will not change.

Challenges of payment orchestration

Alongside the benefits, adopting payment orchestration carries real challenges that a business should weigh honestly.

The first is implementation effort. Connecting a merchant’s existing providers into the orchestration layer takes configuration, testing, and integration work, and every provider added carries its own requirements. The second is cost: an orchestration platform carries its own fees (setup, subscription, or per-transaction), which sit on top of the underlying provider costs, so the case for orchestration rests on the routing and resilience gains outweighing that added layer of cost. The third is technical involvement: while good platforms let payments teams manage routing without code, the initial integration and ongoing operation still call for technical capacity. The fourth is dependency: placing an orchestration layer at the center of the payment stack means the platform’s own reliability and neutrality matter, which is why the platform’s uptime and whether it profits from routing decisions are worth scrutinizing during evaluation.

None of these is a reason to avoid orchestration, but each is a reason to adopt it deliberately, with a clear view of the effort and cost against the expected gain.

Do you need a payment orchestration platform?

Payment orchestration is not necessary for every business, and the honest answer to whether a business needs it depends on its situation.

The case for orchestration is strongest for businesses that sell across multiple countries, where local acquiring and local payment methods materially improve approval rates and reach; businesses using or planning to use more than one PSP or acquirer; businesses where payment downtime is costly enough that resilience justifies the investment; high-volume businesses where routing on cost and recovering declined transactions produces meaningful savings; and subscription businesses where recovering failed recurring payments directly reduces involuntary churn.

The case is weaker for small, single-market businesses with modest volume, a single provider that meets their needs, and no near-term plans to add providers or markets. For them, a single well-chosen PSP may be entirely sufficient, and the added cost and complexity of orchestration would not pay for itself yet. The right approach is to match the decision to the business’s actual payment complexity rather than adopting orchestration for its own sake.

Payment orchestration vs a single PSP

The most common alternative to orchestration is simply using one payment service provider that bundles a gateway, processing, and acquiring together. A single PSP is simpler to manage and can be a good fit for businesses with straightforward needs. The tradeoff is that it means one set of approval rates, one pricing relationship, and one point of failure, with limited ability to route for performance or add providers as the business grows. Orchestration trades some of that simplicity for control, redundancy, and the ability to optimize across many providers. For the detailed comparisons, see Gr4vy’s guides on payment orchestration vs a payment processor and payment orchestration vs payment aggregators.

How to choose a payment orchestration platform

If a business decides orchestration fits, the evaluation should weigh depth of coverage in its priority markets rather than raw connector count; the sophistication of the routing and recovery logic; whether the platform is genuinely neutral or profits from where transactions route; data ownership and portability; security and compliance, including PCI DSS Level 1 certification; reliability and redundancy; and how much the team can control without engineering involvement. Gr4vy’s guide on PCI DSS compliance and payment orchestration covers the security dimension, and the fuller set of evaluation criteria is worth working through before committing to a platform.

Payment orchestration and agentic commerce

Looking ahead, one of the developments making orchestration more relevant is the rise of agentic commerce, where AI agents shop, compare, and transact on a consumer’s behalf. Existing payment stacks were not built for agent-initiated transactions, and merchants need a way to identify, route, and control them separately from ordinary traffic. Because orchestration already sits at the control layer, it is well positioned to do this: agent transactions can be marked, routed through their own rules, sent to different providers or fraud tools, and held to specific limits, all without rebuilding the payment stack. Gr4vy has built an early version of exactly this, described in its guide on payment orchestration for agentic commerce. It is a useful illustration of the broader point that an orchestration layer lets a business adopt new payment developments through configuration rather than re-engineering.

Where payment orchestration is heading

Payment orchestration began as a way to manage the growing complexity of digital payments, and it has become the control layer through which many merchants run their entire payment operation. The core value has stayed constant: connect many providers through one integration, route each transaction intelligently, add resilience, and keep ownership of the data and the decisions. What changes is the range of things that control layer can do, from lifting approval rates and cutting costs today to coordinating agent-initiated transactions as commerce shifts toward AI.

For a business, the practical question is not whether orchestration is impressive in the abstract but whether its own payments are complex enough to benefit: multiple providers or markets, meaningful volume, costly downtime, or recurring billing to protect. Where those conditions hold, orchestration turns a fragmented, engineering-bound payment operation into one a team can control and optimize directly.

Gr4vy is a cloud-native payment orchestration platform that connects merchants to more than 400 payment providers and methods through a single integration, with each merchant running in its own dedicated instance for control over data and configuration. To talk through whether orchestration fits your payment operation, get in touch with our team.

A customer sees a charge on their card statement they do not recognize, or a purchase that never arrived, and instead of contacting the merchant they call their bank and ask for their money back. A few days later the merchant finds the sale reversed, the goods gone, and a fee deducted on top. That reversal is a chargeback, and the sequence of events that produced it, from the cardholder’s call to the final resolution, is a defined process with fixed stages, deadlines, and rules set by the card networks.

Most explanations of chargebacks jump straight to how to prevent them. This one does something different: it walks through what a chargeback actually is and how the dispute moves through the system from start to finish, because understanding the mechanism is what makes everything else, the reason codes, the deadlines, the decision of whether to fight one, make sense.

What is a chargeback?

A chargeback is a forced reversal of a card payment, initiated by the cardholder’s bank rather than by the merchant. When a cardholder disputes a transaction with the bank that issued their card, the bank can reverse the payment, pull the funds back from the merchant, and return them to the cardholder, while the dispute is investigated under the card network’s rules.

The mechanism exists for consumer protection. In the United States its legal foundation is the Fair Credit Billing Act of 1974, which gave cardholders the right to dispute billing errors and unauthorized charges. The card networks (Visa, Mastercard, American Express, and Discover) built their own dispute frameworks on top of that principle, and those frameworks are what govern how a chargeback plays out today.

The essential thing to grasp is who initiates it. A chargeback comes from the issuing bank, at the cardholder’s request, and it happens whether or not the merchant agrees. That single fact, that the reversal is imposed from outside rather than granted by the merchant, is what separates a chargeback from a refund and what makes it costly and adversarial in a way a refund is not.

What is the difference between a chargeback and a refund?

A refund and a chargeback both return money to the customer, but they travel opposite paths. A refund is voluntary and merchant-led: the customer contacts the business, the business agrees, and it returns the money directly. The process is cooperative, there is no penalty, and no third party is involved.

A chargeback is involuntary and bank-led: the customer bypasses the merchant, goes to their issuing bank, and the bank forces the reversal. The merchant usually pays a chargeback fee on top of losing the sale, the transaction counts against the merchant’s chargeback ratio, and the card networks are directly involved. A refund is a customer-service outcome; a chargeback is a dispute with financial and reputational consequences for the merchant. Because the two are so often confused, Gr4vy covers the distinction in more detail in its guide on refunds versus chargebacks.

How the chargeback process works, stage by stage

A chargeback is not a single event but a sequence, and the sequence matters because each stage has its own actors, deadlines, and decisions. Here is how a typical card dispute moves from the cardholder’s first complaint to a final resolution.

Stage 1: The cardholder disputes the transaction

The process begins when a cardholder contacts their issuing bank to dispute a charge. They might claim the transaction was fraudulent, that the goods never arrived, that the product was not as described, that they were charged twice, or that a subscription they thought they had cancelled was billed again. The cardholder does not need the merchant’s involvement or agreement to start this; they simply tell the bank they want the charge reversed.

Stage 2: The issuing bank reviews and assigns a reason code

The issuing bank examines the cardholder’s claim and, if it decides the dispute is valid enough to proceed, provisionally credits the cardholder and assigns a reason code that categorizes the dispute. This code (more on the categories below) is the bank’s shorthand for why the chargeback is being raised, and it determines what evidence the merchant will need if they choose to fight it. At this point the funds are pulled from the merchant’s account through the acquiring bank.

Stage 3: The acquirer notifies the merchant

The dispute travels from the issuing bank, through the card network, to the merchant’s acquiring bank, which notifies the merchant of the chargeback along with its reason code and the amount reversed. The merchant now learns that a sale has been pulled back, why the cardholder says it should be reversed, and how long they have to respond. This is usually the first moment the merchant knows a dispute exists.

Stage 4: The merchant accepts or represents the chargeback

The merchant now faces a decision. They can accept the chargeback, absorbing the loss and the fee, which is often the rational choice for a low-value transaction or one the merchant knows it cannot win. Or they can contest it through a process called representment, submitting evidence to the issuing bank that the charge was legitimate. That evidence depends entirely on the reason code: proof of delivery for a “goods not received” claim, proof of authentication for a fraud claim, records of a cancellation policy for a subscription dispute. Representment has to be built to answer the specific claim the reason code describes, under a tight deadline.

Stage 5: Arbitration by the card network

If the merchant represents and the issuing bank rejects the evidence, the dispute can escalate. The cardholder’s bank may file a second chargeback, and if the two banks still disagree, the case can go to arbitration, where the card network itself reviews the evidence and makes a binding decision. Arbitration carries fees and risk for whichever side loses, so it is usually reserved for higher-value disputes where the amount justifies the cost. Most disputes resolve before this stage, but it is the backstop that settles the ones that do not.

Chargeback reason codes explained

The reason code assigned in Stage 2 is the pivot the whole dispute turns on, so it is worth understanding what these codes are. A chargeback reason code is a standardized identifier that the issuing bank attaches to a dispute to describe why the cardholder says the charge should be reversed. Each card network maintains its own set of codes with its own format: Visa uses codes under its Visa Claims Resolution framework, Mastercard uses four-digit numeric codes, and American Express and Discover each have their own systems.

Despite the different formats, the codes across all networks fall into roughly four categories:

The first is fraud, where the cardholder claims they did not authorize the transaction. The second is authorization, covering transactions that should not have been approved, such as a charge on a card that was already declined or over its limit. The third is processing errors, operational mistakes like charging the wrong amount, billing twice, or failing to process a credit. The fourth is consumer disputes, where the cardholder acknowledges the purchase but has a complaint, such as goods not received, a product not as described, or a cancelled service still being billed.

One caution that experienced merchants learn quickly: the reason code reflects what the cardholder told their bank rather than a verified fact. A cardholder may select or be assigned a code that does not match what really happened, sometimes out of confusion and sometimes deliberately. The code tells the merchant what claim they have to rebut and what evidence will count, which is why reading it carefully before responding matters more than the label suggests.

How long does the chargeback process take?

Chargebacks operate on the card networks’ deadlines instead of the merchant’s, and the full cycle can stretch over weeks or months. A cardholder generally has a set window after the transaction or statement to raise a dispute, often up to 120 days depending on the network and the reason, though for some claim types it can be longer. Once a chargeback is filed, the merchant typically has a limited response window, frequently around 20 to 45 days depending on the network, to submit representment evidence.

From there, the issuing bank takes time to review any evidence, and if the dispute escalates to a second chargeback or arbitration, additional weeks are added. In practice, a straightforward chargeback that the merchant accepts closes quickly, while a contested one can take two to three months or more to fully resolve. The precise deadlines vary by card network and reason code, which is one reason cross-border merchants dealing with multiple networks find dispute management complex to run.

Who pays for a chargeback, and what does it cost?

When a chargeback succeeds, the merchant bears the cost, and that cost is larger than the sale itself. The merchant loses the transaction amount, which is returned to the cardholder. On top of that, the acquirer typically charges a chargeback fee for processing the dispute, which the merchant pays regardless of whether they win or lose the case. If physical goods were shipped, the merchant has usually lost those too.

Beyond the direct costs, every chargeback counts toward the merchant’s chargeback ratio, the proportion of its transactions that end in disputes. Card networks monitor this ratio, and merchants who exceed the networks’ thresholds can face monitoring programs, additional fines, higher processing costs, and in severe cases the loss of their ability to accept card payments. This is why chargebacks are treated as a serious operational risk rather than an occasional cost of doing business: the fees and lost goods are visible, but the threat to the merchant’s processing standing is often the more consequential exposure.

What is friendly fraud, and why is it rising?

A growing share of chargebacks are not fraud in the traditional sense at all. Friendly fraud, also called first-party misuse, happens when a legitimate customer disputes a charge for a purchase they actually made and received, to get their money back while keeping the goods or service. Sometimes it is deliberate abuse; sometimes it is genuine confusion, such as not recognizing a merchant’s billing name on a statement or forgetting about a subscription.

Friendly fraud is difficult for merchants because it arrives disguised as a legitimate dispute, often under a fraud reason code, even though the transaction was valid. Industry research points to this category growing: the Merchant Risk Council’s 2026 Global eCommerce Payments and Fraud Report, a survey of 1,278 merchants across 37 countries, found that around 64% of merchants reported increasing first-party misuse. Because the transaction really did happen, the merchant’s defense in representment rests on evidence that the cardholder received what they paid for, which is why records like delivery confirmation, usage logs, and authentication data matter so much. Gr4vy’s guide on payment fraud prevention strategies covers how merchants detect and respond to this pattern.

Frequently asked questions

What is a chargeback in simple terms?

A chargeback is a forced reversal of a card payment that the cardholder’s bank initiates after the cardholder disputes the charge. The bank pulls the funds back from the merchant and returns them to the cardholder while the dispute is investigated under the card network’s rules. Unlike a refund, it happens without the merchant’s agreement and usually comes with a fee and a mark against the merchant’s chargeback ratio.

What is the difference between a chargeback and a refund?

A refund is voluntary and handled directly between the customer and the merchant, with no penalty and no third party. A chargeback is involuntary: the customer goes to their issuing bank, which forces the reversal. The merchant typically pays a fee, loses the sale, and has the transaction counted against its chargeback ratio. A refund is a customer-service outcome; a chargeback is a formal dispute with financial consequences.

How does the chargeback process work?

It moves through stages. The cardholder disputes a charge with their issuing bank; the bank reviews the claim, assigns a reason code, and provisionally reverses the funds; the merchant’s acquiring bank notifies the merchant; the merchant either accepts the chargeback or contests it through representment by submitting evidence; and if the banks still disagree, the dispute can escalate to arbitration, where the card network makes a binding decision.

What are chargeback reason codes?

Reason codes are standardized identifiers that the issuing bank attaches to a dispute to describe why the cardholder says the charge should be reversed. Each card network has its own format (Visa, Mastercard, American Express, and Discover all differ), but the codes generally fall into four categories: fraud, authorization issues, processing errors, and consumer disputes. The code determines what evidence a merchant needs to contest the dispute.

How long does a merchant have to respond to a chargeback?

The response window depends on the card network and reason code but is commonly in the range of 20 to 45 days from notification. Merchants have to submit their representment evidence within that window, which is why having documentation organized in advance matters. Missing the deadline generally means the chargeback stands regardless of the merits.

Can a merchant fight a chargeback?

Yes, through a process called representment, where the merchant submits evidence to the issuing bank that the transaction was legitimate. The evidence has to answer the specific claim behind the reason code, such as proof of delivery for a “goods not received” dispute or authentication records for a fraud claim. Whether it is worth fighting depends on the transaction value, the reason code, and the strength of the available evidence.

How much does a chargeback cost a merchant?

A merchant that loses a chargeback loses the transaction amount, typically pays a chargeback fee to its acquirer regardless of outcome, and often loses any goods that were shipped. Each chargeback also counts toward the merchant’s chargeback ratio, and exceeding the card networks’ thresholds can lead to fines, monitoring programs, higher costs, and in serious cases losing the ability to accept cards.

What is friendly fraud?

Friendly fraud, or first-party misuse, is when a legitimate customer disputes a charge for something they actually bought and received, keeping the goods or service while recovering their money. It can be deliberate or the result of genuine confusion, such as not recognizing a billing descriptor. It is hard to counter because it looks like a legitimate dispute, and research indicates it is rising, with most merchants reporting increases.

What happens if a merchant gets too many chargebacks?

Card networks track each merchant’s chargeback ratio. Merchants who exceed the networks’ thresholds can be placed into chargeback monitoring programs, charged additional fines, moved to higher processing costs, and, in severe or sustained cases, lose their ability to accept card payments. This is why keeping the chargeback ratio low is a priority even beyond the cost of individual disputes.

Do chargebacks apply to digital wallets and other payment methods?

Card-based digital wallet transactions (a card loaded into Apple Pay or Google Pay, for example) are still subject to the card networks’ chargeback rules, because the underlying payment is a card payment. Other payment methods, such as bank transfers or certain local payment methods, have their own dispute mechanisms that differ from the card chargeback process, which is one more reason merchants operating many payment methods find dispute handling complex.

Where chargebacks fit in a merchant’s payment strategy

Understanding the chargeback process end to end changes how a merchant treats it. A chargeback is not a random misfortune but a defined procedure with predictable stages, actors, and deadlines, which means it can be prepared for: documentation kept ready for representment, billing descriptors made clear to reduce confusion-driven disputes, delivery and authentication records retained, and reason-code patterns watched for the operational problems they reveal.

The deeper point is that chargebacks sit at the intersection of fraud, customer experience, and payment operations. Some are genuine fraud, some are friendly fraud, and many trace back to preventable friction like an unclear billing name or a confusing cancellation flow. Reducing them is less about fighting each dispute and more about addressing what causes them, which is the subject of Gr4vy’s guides on avoiding and controlling chargebacks and, for European merchants specifically, reducing chargebacks and protecting revenue.

Gr4vy is a cloud-native payment orchestration platform that gives merchants centralized visibility over disputes across every connected provider, along with the fraud tooling, authentication controls, and unified reporting that help keep chargeback ratios in check. To see how consolidated dispute visibility would work across your payment stack, talk to our team.

Payment orchestration sits at the intersection of two fast-moving trends: the shift of nearly all commerce to digital payments, and the growing pressure on merchants to stop losing revenue to failed and falsely declined transactions. The statistics below map both, drawn from independent research firms and, where merchant outcomes are cited, from published case studies with named companies behind them.

Every figure here is attributed to its source. Market and industry data come from independent research organizations such as Grand View Research, Worldpay’s Global Payments Report, Statista, Capgemini, Datos Insights, Juniper Research, and the Merchant Risk Council, rather than from payment vendors quoting one another. Merchant-result figures come directly from Gr4vy’s published case studies and are stated as those case studies report them. Where sources disagree or a number is an estimate, that is flagged, because a statistic is only as useful as its provenance is clear.

Payment orchestration market size statistics

The payment orchestration platform market is small relative to the wider payments industry but growing quickly, and estimates vary by research firm depending on how each defines the category.

• The global payment orchestration platform market was valued at USD 1,386.9 million in 2023, according to Grand View Research.
• Grand View projects the market will reach USD 6,520.4 million by 2030, roughly a fourfold increase over the forecast period.
• An alternative estimate from GM Insights placed the 2023 market at around USD 1.2 billion, close to Grand View’s figure.
• Vantage Market Research sized the market higher, at USD 2.8 billion in 2025, projecting USD 9.7 billion by 2035. The spread across firms reflects different definitions of what counts as orchestration revenue.
• Across every major research firm, the consistent signal is a market growing at double-digit annual rates, placing payment orchestration among the faster-growing payments infrastructure segments.

The takeaway from the market-size data is less about any single headline number and more about the direction and pace: independent researchers disagree on the exact figure but agree the category is expanding quickly.

Payment orchestration market growth and regional statistics

Growth rates and regional share show where orchestration adoption is concentrated and where it is accelerating.

• Grand View Research puts the payment orchestration market’s compound annual growth rate at 24.7% from 2024 to 2030, among the highest in payments infrastructure.
• North America accounted for 31.4% of the global market in 2023, making it the largest region by revenue, according to Grand View Research.
• Asia Pacific is the fastest-growing region at roughly 26% CAGR, per Grand View, driven by rapid e-commerce growth and smartphone adoption.
• India is expected to register the highest country-level growth rate through 2030, reflecting the expansion of digital payments across the region.
• The B2B segment held the largest share of the orchestration market in 2023 at roughly 64%, according to Grand View’s segmentation, while the B2C segment is projected to grow fastest.

Digital payments statistics driving orchestration demand

Payment orchestration exists because digital payments have become the dominant way the world transacts, creating the multi-provider complexity that orchestration is built to manage.

• Total transaction value in the global digital payments market is projected to reach USD 20.09 trillion in 2025, growing at a 13.63% CAGR to USD 38.07 trillion by 2030, according to Statista Market Insights.
• Spending through digital payment methods in e-commerce and in-person shopping grew from USD 1.7 trillion in 2014 to USD 18.7 trillion in 2024, a nearly elevenfold increase over the decade, per Worldpay’s Global Payments Report.
• The total value of digital payments is expected to exceed USD 33.5 trillion by 2030, according to Worldpay.
• Digital payments grew from 34% of e-commerce value in 2014 to 66% in 2024, and from 3% to 38% of in-store value over the same period, per Worldpay.
• Instant payments accounted for 13% of global non-cash transactions in 2022 and are projected to exceed 22% by 2028, according to the Capgemini Research Institute.
• Two-thirds of adults worldwide now use digital payments, and 76% of adults globally now have a bank account or mobile money provider, per the World Bank’s Global Findex.

Digital wallet and payment method statistics

The proliferation of payment methods, and the dominance of digital wallets, is a core reason merchants need to manage many providers and methods at once.

• Digital wallets accounted for 56% of global e-commerce value and 33% of point-of-sale value in 2025, representing over USD 13.8 trillion in combined spending, according to Worldpay’s Global Payments Report.
• In APAC, digital wallets were even more dominant, accounting for 77% of online spending and 62% of in-store spending in 2025, per Worldpay.
• Digital wallet spending is forecast to grow around 10% annually from 2025 to 2030, with payment apps across channels projected to reach USD 23.4 trillion by 2030, according to the Worldpay / Global Payments report.
• Direct credit and debit card use accounted for 20% and 12% of e-commerce payments respectively in 2024 (and 25% and 22% at the point of sale), making cards the second and third most-used methods behind digital wallets, per Worldpay.
• Brazil’s Pix instant-payment system accounted for 42% of e-commerce and 34% of POS value in Brazil in 2025 and has expanded acceptance into markets including Argentina, Chile, Portugal, Spain, and the US, per Worldpay.
• China’s Alipay+ platform connects 1.8 billion users to 100 million merchants across 14 markets, according to Worldpay’s report.

Authorization rate and payment decline statistics

Authorization rates are the metric orchestration most directly targets, and the decline data shows why the opportunity is large.

• The average payment decline rate across industries runs at roughly 7.9% of attempted transactions, with some sectors seeing materially higher rates, according to aggregated industry data.
• E-commerce authorization declines can reach as high as 17% in certain high-risk or high-ticket sectors, per industry analysis.
• Roughly 60 to 65% of declined transactions are estimated to come from legitimate customers instead of genuine fraud, according to industry research on authorization performance, indicating how much declined volume is potentially recoverable.
• Domestic acquiring commonly delivers 10 to 20% higher approval rates than cross-border processing for in-market cards, a gap orchestration addresses through local acquirer routing, per widely cited industry figures.

False decline statistics

False declines, legitimate transactions wrongly rejected, are one of the largest and least-measured sources of lost e-commerce revenue.

• The global average false-decline rate was 1.51% of e-commerce sales in 2024, according to Datos Insights drawing on Cybersource’s E-Commerce Fraud Landscape and Trends report.
• False declines were estimated to cost merchants nearly USD 175 billion in 2024, projected to approach USD 265 billion by 2027, per the same Datos Insights / Cybersource data.
• By comparison, actual e-commerce payment fraud losses were estimated at around USD 48 billion in 2023 by Juniper Research, meaning false declines cost merchants several times more than the fraud that decline systems are trying to prevent.
• These figures are independent estimates and specific numbers vary by source, but the consistent finding across studies is that false declines outweigh actual fraud by a wide margin.

Failed payment and subscription churn statistics

For subscription and recurring-billing businesses, failed payments translate directly into involuntary churn, most of which is recoverable.

• In roughly four out of five cases, failed payments stem from system friction such as false declines, processor issues, and expired credentials, rather than a genuine inability to pay, according to PYMNTS Intelligence research.
• Involuntary churn (subscribers lost to failed payments rather than active cancellation) accounts for an estimated 20 to 40% of total subscription churn, according to aggregated subscription-industry benchmarks.
• The average transaction failure rate for subscription businesses runs near 7.9% across industries, reaching as high as 14.7% in certain sectors, per aggregated 2025 subscription-payment data.
• Industry benchmarks place the median failed-payment recovery rate near 47.6%, indicating that roughly half of failed recurring payments can be recovered with retry and dunning strategies, with top performers recovering considerably more.
• These recovery figures come from a mix of research and vendor datasets and are best treated as directional benchmarks instead of precise universal rates.

Payment fraud statistics

The fraud landscape that decline and authentication systems respond to is shifting, which affects how merchants tune routing and authentication.

• The Merchant Risk Council’s 2026 Global eCommerce Payments and Fraud Report, a survey of 1,278 merchants across 37 countries, found around 64% of merchants reporting increasing first-party misuse (customers falsely claiming a legitimate transaction was unauthorized), with roughly a quarter seeing increases of 25% or more.
• Global digital payment fraud losses were estimated at around USD 41 billion in 2023, up roughly 18% year on year, according to industry data compiled from independent sources.
• First-party misuse is harder for traditional fraud rules to catch than classic stolen-card fraud, which pushes merchants toward more nuanced authentication and routing rather than blunt declines.

Real payment orchestration results from merchant case studies

The most directly verifiable statistics are those tied to a named business and a published outcome. The following come from Gr4vy’s own merchant case studies and are stated as those case studies report them.

• Baby Bunting secured a 2.8% uplift in authorization rates within the first four months of moving to a dual-acquirer setup with failover routing, as reported in its case study. Baby Bunting is Australia’s largest specialty baby-goods retailer. Read the Baby Bunting case study.
• Ding cut the time to integrate a new gateway and add a new local payment method from 3 to 6 weeks down to just 3 days through orchestration, as its case study reports. Ding is a mobile top-up service operating across more than 140 countries, and used orchestration to launch Pix in Brazil and prioritize PayPal in Germany through no-code rules. Read the Ding case study.
• FuturHealth completed its entire orchestration integration in 27 days, implementing dynamic routing across multiple PSPs with built-in retry logic to improve authorization rates and recover previously failed transactions, per its case study. Read the FuturHealth case study.
• Mattilda supports more than 180,000 students across a growing network of private schools in Latin America and selected Gr4vy to power Mattilda Pay, its white-label payment offering, as its case study documents. Read the Mattilda case study.
• Gr4vy connects merchants to more than 400 payment service providers, payment methods, and anti-fraud services through a single integration, turning the addition of a provider or method into a configuration change rather than an engineering project.

These merchant figures are the most concrete evidence in this guide, because each is tied to a named company and a published case study, unlike an industry average.

Payment orchestration statistics at a glance

A consolidated reference of the figures above, with sources.

Frequently asked questions

How big is the payment orchestration market?

According to Grand View Research, the global payment orchestration platform market was valued at USD 1,386.9 million in 2023 and is projected to reach USD 6,520.4 million by 2030, growing at a 24.7% CAGR. Other firms estimate it differently (GM Insights at around USD 1.2 billion in 2023, Vantage Market Research at USD 2.8 billion in 2025), but all show double-digit growth. The variation comes from how each firm defines the orchestration category.

What is the growth rate of the payment orchestration market?

Grand View Research puts the payment orchestration market’s compound annual growth rate at 24.7% from 2024 to 2030, among the highest in payments infrastructure. Other research firms estimate CAGRs from roughly 13% to 25% depending on their market definitions, but all agree on double-digit annual growth.

Which region leads the payment orchestration market?

North America was the largest region in 2023 at 31.4% of global revenue, according to Grand View Research, while Asia Pacific is the fastest-growing region at roughly 26% CAGR, with India expected to post the highest country-level growth rate through 2030.

How much revenue do merchants lose to false declines?

According to Datos Insights, drawing on Cybersource’s 2024 report, the global false-decline rate averaged 1.51% of e-commerce sales, costing merchants nearly USD 175 billion in 2024 and projected to approach USD 265 billion by 2027. For comparison, Juniper Research estimated around USD 48 billion in actual e-commerce fraud losses in 2023, meaning false declines cost merchants several times more than actual fraud.

What percentage of failed payments are recoverable?

PYMNTS Intelligence research found that in roughly four out of five cases, failed payments stem from system friction (false declines, processor issues, expired credentials) rather than a genuine inability to pay, which makes much of the lost revenue recoverable. Industry benchmarks place the median failed-payment recovery rate near 47.6%, with top performers recovering considerably more through retry and dunning strategies.

How much of subscription churn is caused by failed payments?

Involuntary churn (subscribers lost to failed payments rather than active cancellation) accounts for an estimated 20 to 40% of total subscription churn, according to aggregated subscription-industry benchmarks, with some high-risk sectors reporting higher rates. Most of this churn is preventable through better routing, retries, and automatic credential updating.

What share of digital payments comes from digital wallets?

According to Worldpay’s Global Payments Report, digital wallets accounted for 56% of global e-commerce value and 33% of point-of-sale value in 2025, representing over USD 13.8 trillion in combined spending. In APAC the share is higher still, at 77% of online spending in 2025.

How much do authorization rates improve with payment orchestration?

Improvement depends on the business, its markets, and its previous setup, so there is no single universal figure. As a documented example, Baby Bunting reported a 2.8% uplift in authorization rates within the first four months of moving to an orchestrated dual-acquirer setup with failover routing, as stated in its Gr4vy case study. Gains come from routing each transaction to the provider most likely to approve it, plus retries and fallback logic. Domestic acquiring can also deliver 10 to 20% higher approval rates than cross-border processing, a gap orchestration addresses through local routing.

Where do these payment orchestration statistics come from?

The merchant-result figures come directly from Gr4vy’s published case studies (Baby Bunting, Ding, FuturHealth, Mattilda). The market and industry figures come from independent research organizations, including Grand View Research (market size and growth), Statista and Worldpay (digital payments and wallets), Capgemini (instant payments), Datos Insights and Cybersource (false declines), Juniper Research (fraud losses), PYMNTS Intelligence (failure causes), and the Merchant Risk Council (fraud trends). None of the industry figures come from payment vendors.

What the payment orchestration statistics show

Read together, the numbers tell a coherent story. Digital payments have become the dominant form of commerce, with global transaction value measured in the tens of trillions and digital wallets alone accounting for more than half of e-commerce spend. That shift multiplied the providers, methods, and markets a merchant has to manage, which is the complexity payment orchestration exists to handle, and it is why the orchestration market is growing at double-digit rates while remaining small relative to the payments industry overall.

At the same time, the decline, false-decline, and failed-payment figures quantify a large and mostly recoverable revenue leak: false declines alone are estimated to cost merchants far more than actual fraud, and the majority of failed payments come from system friction rather than customers who cannot pay. The merchant case-study results put concrete numbers on what addressing that leak can look like, from Baby Bunting’s authorization uplift to Ding’s collapse in integration time.

For a business weighing whether orchestration is worth evaluating, the most useful exercise is to measure its own equivalents of these figures: its current authorization and decline rates, its false-decline rate, the share of its failed payments caused by system friction, and the time it takes to launch a new payment method or market. Those numbers, measured honestly against the benchmarks above, show how much of the opportunity these statistics describe is actually present in the business.

Gr4vy is a cloud-native payment orchestration platform connecting merchants to more than 400 payment providers and methods through a single integration, with the routing, retries, and unified data behind the merchant results above. To see how these statistics might translate to your own payment operation, talk to our team.

Picture a large retailer on the busiest sales day of its year. Its single acquiring bank has an outage that lasts forty minutes. For those forty minutes, every card transaction fails. Customers have the funds and the checkout works fine; the problem is that the one institution authorized to process the retailer’s card payments is unreachable. The revenue lost in that window is gone, and no amount of checkout optimization would have saved it, because the failure was upstream of everything the merchant controlled.

That scenario, and several less dramatic versions of it, is why a growing number of enterprises no longer rely on a single acquirer. Concentrating all card volume with one acquiring bank means one set of approval rates, one pricing schedule, one geographic footprint, and one point of failure. A multi-acquirer strategy spreads that volume across several acquiring relationships and routes each transaction to the one best suited to approve it. The result is more resilience, better approval rates, lower costs, and broader reach, though running it well introduces real complexity of its own.

What an acquirer is, and why the relationship matters

An acquiring bank, or acquirer, is the financial institution that holds a merchant’s account and processes card payments on its behalf, receiving the funds from the customer’s issuing bank through the card networks and depositing them into the merchant’s account. The acquirer is the merchant’s entry point into the card system: it carries the merchant’s relationship with the card networks, takes on a degree of risk for the merchant’s transactions, and is the destination where settled money arrives.

Because the acquirer sits at this structural position, the acquiring relationship shapes several things at once. The acquirer’s connectivity to issuing banks affects how many transactions get approved. Its geographic reach determines which markets a merchant can serve well. Its pricing determines a meaningful part of the cost of every transaction. And its uptime determines whether payments flow at all. When a merchant has only one acquirer, all of these are fixed by that single relationship. This is a different concern from the number of payment service providers or gateways a merchant uses; the acquirer is specifically the licensed institution that settles the funds, which is why the acquiring layer is worth examining on its own. For the distinction between the acquirer and the other parties in the chain, see Gr4vy’s guide on card network versus payment processor.

What a multi-acquirer strategy is

A multi-acquirer strategy is an arrangement in which a merchant maintains relationships with more than one acquiring bank and directs transactions among them based on criteria such as geography, card type, cost, and performance. Rather than sending every transaction to a single acquirer by default, the merchant can send a Brazilian customer’s card to a local Brazilian acquirer, route a high-value European transaction to whichever European acquirer approves those best, and shift traffic away from any acquirer that is degraded or down.

The strategy rests on the fact that acquirers are not interchangeable. One acquirer may have strong issuer relationships in one region and weak ones in another. One may price certain card types or transaction types more favorably. One may support payment methods or currencies another does not. By holding several relationships and routing intelligently among them, a merchant stops being limited to the strengths and weaknesses of a single acquirer and starts using the best of each.

Why enterprises adopt a multi-acquirer strategy

Research into merchant acquiring behavior consistently surfaces the same handful of motivations. A survey by Edgar, Dunn & Company and ACI Worldwide found that the top three reasons merchants work with more than one acquirer were resilience, reducing operational costs, and improving conversion rates. The same study reported that 85 percent of merchants that moved to multiple acquirer relationships saw an increase in conversion rates, with 23 percent improving conversion by more than 10 percent, and that 71 percent were satisfied or very satisfied with the multi-acquiring approach. Those figures come from that specific study and are worth treating as directional rather than guaranteed, but they line up with the reasons enterprises give in practice.

Resilience and business continuity

The most cited reason is resilience. A single acquirer is a single point of failure: if it has an outage, a business failure, or a change in the kinds of business it is willing to handle, a merchant relying on it alone loses the ability to process payments. Multiple acquirer relationships mean that if one acquirer goes down, traffic can be routed to another and payments keep flowing. For a business where every minute of downtime is lost revenue, this alone can justify the strategy. Gr4vy’s guide on downtime in payments covers the outage risk in more depth.

Higher approval rates

Approval rates vary by acquirer, and the variation is largest across borders. Domestic acquirers commonly achieve meaningfully higher approval rates than cross-border processing for in-market cards, with industry sources frequently citing gains in the range of 10 to 20 percent when a local acquirer is used instead of a foreign one. The reason is that issuing banks tend to trust and approve transactions acquired locally more readily than the same transaction routed through a foreign acquirer, which can look riskier. A merchant with acquirers in its key markets can route each transaction to a local acquirer and recover approvals it would otherwise lose. This is one of the strongest and most measurable benefits, and it connects directly to the wider practice of lifting approval rates covered in Gr4vy’s guide on how to increase payment approval rates in 2026.

Lower costs and stronger negotiating position

Working with a single acquirer means accepting its pricing schedule with little bargaining power. Holding multiple acquirer relationships introduces competition: a merchant can route transactions to the acquirer with the most favorable rates for a given card type, region, or transaction type, and can negotiate better terms because it is not wedded to one provider. Over time, the ability to route on cost and to negotiate from a position of choice produces meaningful savings. Gr4vy’s guide on least cost routing explains the cost-routing mechanics.

Broader geographic and payment method reach

Different acquirers support different markets, currencies, and payment methods. A merchant expanding internationally often finds its incumbent acquirer is strong at home but weak in the new markets it wants to enter. Adding acquirers with strength in those markets, and the local methods they connect to, makes expansion viable in a way a single acquirer cannot. Gr4vy’s guide on card acquiring for international markets goes into the global, local, and cross-border considerations.

Better risk and chargeback management

Holding multiple acquiring relationships also lets a merchant monitor chargeback and fraud patterns across acquirers, identify where problems concentrate, and adjust routing accordingly. Spreading volume also avoids over-concentrating risk with any single acquirer, which matters because an acquirer that sees a merchant’s chargeback ratio climb can change terms or withdraw service.

The real challenges of running multiple acquirers

The benefits are real, and so are the difficulties. The competitor content on this topic tends to skip past the challenges, but they are the reason a multi-acquirer strategy is hard to run without the right infrastructure.

Integration complexity. Each acquirer has its own connection, its own technical requirements, and its own quirks. Integrating and maintaining several acquirer connections directly is a substantial and ongoing engineering effort, and every new acquirer adds to it.

Routing logic. Deciding which transaction goes to which acquirer, and doing it in real time based on geography, card type, cost, and live performance, requires routing logic that has to be built, maintained, and continuously tuned. Static rules decay as acquirer performance shifts.

Stored credentials and tokenization across acquirers. A card stored for use with one acquirer is not automatically usable with another. Without a provider-agnostic way to store credentials, routing a returning customer’s stored card to a different acquirer becomes a problem, particularly for subscriptions and card-on-file transactions.

Fragmented reporting. Each acquirer reports separately, in its own format. Reconciling and getting a unified view of performance across all of them is a real operational burden when done manually.

Compliance across relationships. Each acquiring relationship carries its own compliance obligations, and managing PCI scope, tokenization, and regulatory requirements across several at once adds overhead.

These challenges are exactly why a multi-acquirer strategy and payment orchestration are so closely linked. The strategy is the goal; orchestration is what makes it operationally feasible.

How payment orchestration operationalizes a multi-acquirer strategy

A multi-acquirer strategy without the right infrastructure means absorbing all the complexity above directly: integrating each acquirer, building the routing, solving the stored-credential problem, and stitching together the reporting. A payment orchestration platform is the layer that turns the strategy from an integration burden into a configuration exercise.

Orchestration addresses each of the challenges directly. It connects to multiple acquirers through a single integration, so adding an acquirer is a configuration step rather than a new engineering project. It provides the routing engine that directs each transaction to the best acquirer based on geography, card type, cost, and performance, and lets that logic be adjusted without code. It stores credentials in a provider-agnostic vault so a stored card can be routed to any acquirer, which is what makes multi-acquirer routing work for subscriptions and card-on-file. It handles failover automatically, rerouting around a degraded acquirer. And it unifies reporting across every acquirer into one view.

In other words, orchestration is the practical foundation of a multi-acquirer strategy. The strategy defines what a merchant wants (resilience, better approvals, lower cost, broader reach); orchestration is how a merchant achieves it without taking on unmanageable complexity. This is also why the multi-acquirer question sits inside the broader multi-provider conversation. For the wider strategy across payment service providers, see Gr4vy’s guides on building a multi-PSP payment strategy and multi-PSP credit card processing, and for the routing mechanics specifically, the guide on intelligent payment routing.

When a multi-acquirer strategy makes sense

Not every business needs multiple acquirers, and it is worth being clear about when the strategy earns its complexity.

The case is strongest for businesses that sell across multiple countries, where local acquiring delivers materially better approval rates and access to local payment methods; for businesses where payment downtime is expensive enough that resilience alone justifies a second acquirer; for high-volume businesses where routing on cost and negotiating from a position of choice produces meaningful savings; and for subscription and card-on-file businesses where recovering failed transactions by retrying through an alternate acquirer directly reduces involuntary churn.

The case is weaker for small, single-market businesses with modest volume and no cross-border ambitions, where a single reliable acquirer may be entirely sufficient and the added complexity would not pay for itself. As with most payment stack decisions, the strategy should follow the business’s actual needs rather than being adopted for its own sake.

Frequently asked questions

What is a multi-acquirer strategy?

A multi-acquirer strategy is an arrangement where a merchant maintains relationships with more than one acquiring bank and routes transactions among them based on factors such as geography, card type, cost, and performance. Instead of sending every transaction to a single acquirer, the merchant directs each one to the acquirer best suited to approve it, which improves resilience, approval rates, cost control, and geographic reach.

What is an acquirer in payments?

An acquiring bank, or acquirer, is the financial institution that holds a merchant’s account and processes card payments on its behalf. It receives funds from the customer’s issuing bank through the card networks and deposits them into the merchant’s account. The acquirer carries the merchant’s relationship with the card networks and is where settled money arrives, which is why the acquiring relationship shapes approval rates, cost, reach, and reliability.

Why do enterprises use more than one acquirer?

The most common reasons are resilience (so a single acquirer outage does not stop all payments), higher approval rates (especially by using local acquirers in different markets), lower costs and a stronger negotiating position, and broader geographic and payment-method reach. Research by Edgar, Dunn & Company and ACI Worldwide found resilience, cost reduction, and improved conversion to be the top three drivers, with most merchants that adopted multiple acquirers reporting higher conversion.

Does using multiple acquirers improve approval rates?

It can, particularly across borders. Domestic acquirers commonly achieve higher approval rates than cross-border processing for in-market cards, with industry sources frequently citing improvements in the range of 10 to 20 percent when a local acquirer is used instead of a foreign one, because issuing banks tend to approve locally acquired transactions more readily. Routing each transaction to a well-suited acquirer recovers approvals that a single acquirer would lose.

What is the difference between a multi-acquirer and a multi-PSP strategy?

A multi-acquirer strategy specifically concerns the acquiring banks that hold the merchant account and settle funds. A multi-PSP strategy concerns the payment service providers a merchant works with, which may bundle gateways, processing, and acquiring together. The two overlap, because a multi-acquirer strategy is often implemented through multiple providers, but the acquirer is the specific licensed institution that settles the money, which is why the acquiring layer is worth considering in its own right.

What are the challenges of a multi-acquirer strategy?

The main challenges are integration complexity (each acquirer has its own connection to build and maintain), routing logic (deciding and continuously tuning which transaction goes where), stored credentials across acquirers (a card stored for one acquirer is not automatically usable with another), fragmented reporting (each acquirer reports separately), and compliance across multiple relationships. These challenges are why a multi-acquirer strategy is typically implemented through a payment orchestration platform rather than by integrating each acquirer directly.

How does payment orchestration help with a multi-acquirer strategy?

Payment orchestration connects to multiple acquirers through a single integration, provides the routing engine that directs each transaction to the best acquirer, stores credentials in a provider-agnostic vault so stored cards can be routed to any acquirer, handles failover automatically, and unifies reporting across all acquirers. It turns a multi-acquirer strategy from a heavy, ongoing engineering effort into a configuration exercise, which is why the strategy and orchestration are so closely linked.

Does a multi-acquirer strategy reduce costs?

It can. Holding multiple acquirer relationships introduces competition, letting a merchant route transactions to the acquirer with the most favorable rates for a given card type or region and negotiate better terms from a position of choice instead of being tied to one provider’s schedule. Over time, cost-based routing and a stronger negotiating position can produce meaningful savings, though the size depends on volume and transaction mix.

How does a multi-acquirer strategy help with international expansion?

Different acquirers are strong in different markets. A merchant’s incumbent acquirer may perform well at home but poorly in new markets. Adding acquirers with strength in target markets provides higher local approval rates and access to local payment methods, making expansion viable in a way a single acquirer cannot support. Orchestration makes adding those acquirers a configuration step rather than a fresh integration for each market.

Is a multi-acquirer strategy worth it for a small business?

For a small, single-market business with modest volume and no cross-border plans, a single reliable acquirer is often sufficient, and the added complexity of multiple acquirers may not pay for itself. The strategy earns its complexity for businesses selling across multiple countries, those where downtime is costly, high-volume businesses that benefit from cost routing, and subscription businesses that recover failed payments by retrying across acquirers. The decision should follow the business’s actual needs.

Where this leaves enterprise payment teams

The move from a single acquirer to several is, at its core, a decision to stop being limited by one institution’s approval rates, pricing, reach, and uptime. For an enterprise selling across borders or at scale, those limits translate directly into lost approvals, higher costs, failed expansions, and exposure to outages that a single relationship cannot protect against. The survey data and the consistent experience of large merchants point the same way: spreading volume across multiple acquirers and routing intelligently among them improves resilience, conversion, and cost at once.

The reason more enterprises have not always done it is that running multiple acquirers directly is genuinely hard, between the integrations, the routing, the stored-credential problem, and the fragmented reporting. That difficulty is precisely what payment orchestration removes. The strategy defines the destination; orchestration is the vehicle that makes the journey manageable, turning what would be a standing engineering burden into rules a payments team can configure and adjust.

Gr4vy is a cloud-native payment orchestration platform that connects merchants to more than 400 payment providers and acquiring relationships through a single integration, with the routing, provider-agnostic vault, automatic failover, and unified reporting that make a multi-acquirer strategy practical to run. To explore what a multi-acquirer setup would look like for your markets and volume, talk to our team.