What Is Payment Acceptance? How It Works and How to Improve Acceptance Rates

Here, "acceptance" refers to payments, not contract law. To trace a specific refund, use the separate acquirer reference number (ARN) guide.

What payment acceptance covers

For online card payments, four core roles usually do the work:

Real setups add layers on top: a payment service provider (PSP) or gateway that connects you to the acquirer, or a payment facilitator that aggregates many small merchants. The four-role picture is the skeleton, not the whole anatomy. Two deeper reads on the plumbing: merchant acquiring explained and payment gateway vs payment processor.

How you accept payments: methods and channels

Acceptance has two dimensions that are easy to conflate. The first is what you can accept — your methods and channels. The second is how often what you accept gets approved — your acceptance rate. Fixing one doesn't automatically fix the other.

The methods side, in brief:

• Cards — accepted through your acquiring setup, online or in person.
• Digital wallets — Apple Pay sends a device-specific token and one-time cryptogram rather than the card number; Google Pay sends either a network token or the encrypted card on file, depending on how the card is stored. Many regional wallets pay from a stored balance or bank account, so not every wallet is card-based.
• Bank payments — pay-by-bank and account-to-account transfers; see our pay-by-bank explainer.
• Buy now, pay later — installment options offered at checkout.
• Local payment methods — market-specific options that matter in particular countries; the full landscape is in our alternative payment methods guide.

Source: Apple, "Apple Pay planning documentation", and Google, "Google Pay API request objects" (how wallet payment credentials are protected), both accessed 12 July 2026.

Which mix you need depends on where you sell and who your customers are. A merchant selling into markets where cards are a minority payment method can have a flawless card setup and still miss most of the opportunity.

Payment acceptance rate: formula, benchmarks, and declines

Your payment acceptance rate is the percentage of attempted payments that get approved. Paystand states the formula as: (successful payments ÷ total attempts) × 100.Payment acceptance rate is often discussed alongside authorization rate and approval rate, but the terms are not inherently identical — what each number counts varies by provider and measurement choice, as the note below explains.

What counts as good? Two attributed reference points, as of July 2026:

• Paystand reports that healthy business-to-business (B2B) acceptance typically sits above 90%.
• Stripe's authorization guide notes that online transactions run roughly 10% lower than in-person ones, because the card isn't physically present.

Source: Paystand, "The Ultimate Guide to Payment Acceptance in B2B" (formula and B2B benchmark) and Stripe, "Optimizing authorization rates" (online vs in-person gap), both accessed 9 July 2026.

Treat both as directional. Your normal depends on market, sector, and payment mix — not on someone else's average. Also check how a number was measured: Adyen notes acceptance and authorization figures can diverge significantly depending on the denominator — gross counts every authorization attempt, retries included, while net counts orders that eventually got approved.

Why payments get declined, and what to check

Stripe's guide groups issuer declines into a handful of causes. Here is that list, turned into a working table:

3DS is the extra bank-verification step — the "confirm it's you" screen. Notice that fraud controls sit on both sides of this table: too little screening and issuers decline you for risk; too much friction and customers abandon. Tuning that balance is acceptance work, not just security work. One more code worth knowing: "05 — Do not honor." Stripe describes it as the issuer's catch-all when it declines without stating why.

Source: Stripe, "Optimizing authorization rates" (decline categories, remediation options, authentication trade-off, and the "05 — Do not honor" code), accessed 9 July 2026.

The cross-border factor

The country where your acquirer processes a payment can affect whether the issuer approves it. Issuers may treat payments processed in another country more cautiously, although the effect varies by market and setup. If you sell internationally, review this early. We break it down in local acquiring vs cross-border acquiring and cross-border acquiring fees.

Source: Stripe, "Optimizing authorization rates" (local acquiring and cross-border approval context), accessed 21 July 2026.

• HaiPay route — If declining cross-border approvals are your specific problem, see Global Credit Card acquiring. In the product page's own words, it is "directly connected to major card networks, delivering stable global acquiring through a distributed architecture."

Source: HaiPay, "Global Credit Card Acquiring" (quoted product description), accessed 21 July 2026.

Merchant of record vs acquirer: who "accepts" the payment?

A merchant of record (MoR) is the legal entity responsible for the sale. Stripe's documentation says the MoR receives the customer's payment and appears on the card statement. It also answers for chargebacks (payment reversals disputed through the card issuer), refunds, and applicable regulations such as sales taxes. Stripe notes that who plays this role depends on the configuration.

That is a different job from the acquirer's. The acquirer moves card money into the seller's account; the MoR is the seller, in the legal sense.

If you sell through an MoR, the MoR remains responsible for refunds, though customer service may be handled by the MoR or a third party it designates.If you run your own payment setup, the sections above are your job description. Exact tax and liability boundaries depend on the model, jurisdiction, and contract — check yours. For the adjacent model where a platform onboards sub-merchants, see our payment facilitator guide.

Source: Stripe Docs, "Merchant of record" (definition, responsibilities, configuration-dependence), accessed 12 July 2026.

Sources

1. Paystand — "The Ultimate Guide to Payment Acceptance in B2B" — acceptance-rate formula and the 90%+ B2B benchmark. Accessed 9 July 2026.
2. Stripe — "Optimizing authorization rates" (guide) — decline categories, the "05 — Do not honor" code, online vs in-person gap, remediation options, and local-acquiring context. Accessed 21 July 2026.
3. Stripe Docs — "Merchant of record" — MoR definition, responsibilities, and configuration-dependence. Accessed 12 July 2026.
4. Apple — Apple Pay planning documentation — encrypted payment token; device-specific account number; one-time cryptogram. Accessed 12 July 2026.
5. Google — Google Pay API request objects — tokenizationSpecification; CRYPTOGRAM_3DS / PAN_ONLY authentication methods. Accessed 12 July 2026.
6. HaiPay — "Global Credit Card Acquiring" — product description quoted in the cross-border section. Accessed 21 July 2026.
7. Adyen Knowledge Hub — "Payment acceptance rate" — acceptance vs authorization definitions; gross/net denominator divergence. Accessed 22 July 2026.
8. Stripe Docs — Card verification checks — street-address verification supported for most cards issued in the US, Canada, and the UK. Accessed 22 July 2026