Alternative Payment Methods: The Complete 2026 Guide

What changed in 2026

A short changelog of the shifts that materially moved acceptance strategy this year. Sourced from published regulator statements and scheme announcements.

What are alternative payment methods?

An alternative payment method (APM) is any way of paying online that isn't an internationally branded credit or debit card. In practice that covers digital wallets, real-time bank transfers, buy-now-pay-later (BNPL), vouchers, cash-based rails, mobile carrier billing, QR-code schemes, and a growing set of account-to-account and crypto-adjacent methods.

The industry uses two closely related terms:

• APM — alternative payment method: anything that isn't a global card scheme.
• LPM — local payment method: an APM that's dominant in one specific country or region (Pix in Brazil, iDEAL in the Netherlands, UPI in India, MB WAY in Portugal, and so on).

Every LPM is an APM. Not every APM is an LPM — global wallets like PayPal, Apple Pay or Google Pay work almost everywhere but still sit outside the card rails.

Why alternative payment methods matter now

In most of the world, cards are no longer the default. Shoppers in Latin America pay with Pix and OXXO. Europeans reach for iDEAL, Bancontact, Blik, SEPA instant, and Klarna. Asian buyers use UPI, GrabPay, GCash, Alipay, and WeChat Pay. If your checkout only speaks Visa and Mastercard, you're leaving revenue on the table — and losing to competitors who localised faster.

The story isn't just consumer preference. APMs often settle faster, cost less, cut fraud, and remove the interchange dependency that makes card economics fragile in low-ticket or high-refund businesses. For teams that own acceptance, APMs are now a first-class strategic lever.

The main types of alternative payment methods

Every APM sits in one of a handful of families. Understanding the family tells you how it clears, how it settles, and where it wins.

How each APM family clears and settles

Every APM family moves money through a different set of intermediaries. The diagrams below strip each family down to its four essential legs — who authenticates the payer, who authorises, who instructs settlement, and how the merchant is paid.

Top alternative payment methods by region

A working shortlist — not exhaustive, but a good starting map. The full, continuously-updated list lives in the Payment Methods List database.

A method being "big" isn't the same as being right for you. Ticket size, refund profile, subscription vs. one-off, KYC posture and settlement currency all change the answer.

Compare 25 major APMs at a glance

A high-level side-by-side across the methods most teams actually pick from. Settlement and chargeback columns use qualitative buckets — the exact operational figures for each method sit inside the individual profile page. Nothing about pricing, cost or interchange is on this page by design.

Every column above uses qualitative buckets, not point-in-time statistics. Exact settlement timing, refund SLAs and observed dispute rates for each method are covered in the founding-partner operational sections of the individual profile pages.

APM refund and reconciliation failure modes

APMs don't fail the way cards fail. The refund and reconciliation edge cases below are the ones that break payment ops teams the first time — worth wiring into your integration test plan before you turn a new method on in production.

1. Method has no native refund primitive

Several cash and voucher rails — OXXO, Boleto Bancário, Konbini, PagoEfectivo, Multibanco Referência — collect money in one direction only. Refunds happen out-of-band: the merchant issues a bank transfer or store credit to the payer, and there is no scheme-side reversal to match against. Recon has to hand-stitch the outbound refund to the original charge.

2. Refund lands off-scheme, unmatched to the original transaction

A2A refunds executed as new credit transfers (SPEI, some Pix refund flows in emergency modes, ACH refund-as-new-credit) arrive at the merchant's bank with no scheme-level reference to the original charge. Reconciliation depends on remittance metadata (end-to-end ID, unstructured reference) surviving intact — not every bank preserves it.

3. Partial refunds change the installment schedule

BNPL partial refunds have to be apportioned across the remaining installments. Different providers apply it differently — pro-rata across remaining installments, applied to the tail, or applied to the head — which silently changes the consumer's next due date and the merchant's expected payout schedule.

4. Wallet-of-wallet routing loses the funding source

Wallets funded from another instrument (Apple Pay on a stored card, PayPal balance topped up from ACH/SEPA, GrabPay/GCash funded from a card) refund to the wallet balance, not the original funding instrument, unless the operator explicitly supports source-preserving refunds. The consumer sees "refunded" in the merchant's system but "no refund" in their bank statement.

5. FX round-trip mismatches

Cross-border APMs where the payer settles in a local currency and the merchant is paid in USD/EUR: refunds executed at a different FX rate leave a residual over- or under-collection. Some MoRs absorb it; some pass it through; some post it as an unallocated adjustment on the settlement file.

6. Reconciliation files disagree with real-time webhooks

Some APMs deliver settlement files at T+1 or T+2 with amounts that differ from the real-time webhook payloads — netted returns, disputed items, retail-network commissions, currency-conversion adjustments. Daily close performed on webhook numbers alone will diverge from the bank statement.

7. Operator dispute programs run parallel to card chargebacks

PayPal, Klarna, Alipay and other operator wallets run their own dispute constructs alongside any underlying card chargeback right. Evidence formats, response windows and reversal mechanics are operator-specific, and a single transaction can be disputed twice — once at the operator, once at the underlying card issuer — with independent outcomes.

8. Recall and return codes settle days after the fact

SEPA R-transactions (SDD returns, ACH R-codes, BACS ARUDDs) can invalidate a settlement days or weeks after the merchant already recognised revenue. Funds recognised on day one get clawed back; the reconciliation has to unwind the original credit and any onward payout to a seller or supplier.

How to choose the right APM mix

The teams that get this right treat APM strategy the way they treat any other portfolio: pick for coverage, cost, conversion and control — in that order — and re-evaluate every quarter.

1. Start from the buyer, not the PSP

Look at where checkouts fail and where competitors' checkouts don't. The dominant local method in a market is almost always non-negotiable; the long tail is a judgment call.

2. Model true cost, not sticker cost

Include scheme fees, interchange, FX, chargeback economics, refund friction and settlement time. A "cheaper" method that pushes settlement out seven days can quietly kill working capital.

3. Weigh approval, not just availability

Two PSPs can both "support" the same LPM and route it very differently. Approval rates on the exact BIN/issuer/method combination are what matter.

4. Own the fallback

Every APM eventually has an outage. Plan the fallback order per country before you need it — and make sure your checkout logic can execute it.

5. Decide what you'll not add

Every extra method is UX weight, ops load, and reconciliation surface. Ruthless is usually right.

Common pitfalls when rolling out APMs

• Relying on PSP marketing pages. Coverage claims are rarely wrong, but they hide the difference between "we can process it" and "we process it well."
• Treating wallets as one category. Apple Pay and WeChat Pay live in the same bucket in slide decks and nothing else.
• Ignoring the refund path. Some APMs don't refund natively; the money returns via bank transfer with manual reconciliation.
• Copy-pasting a European stack into LATAM or MENA. Wrong methods, wrong currencies, wrong KYC — same PSP, still broken.
• No source of truth. APM rules change constantly. Without a single, neutral reference, every team ends up with a different, half-stale spreadsheet.

Why teams use Payment Methods List

PML isn't a PSP, an aggregator, or a marketplace. We don't get paid to route you anywhere. We're the reference the people who own acceptance — heads of payments, PMs, LATAM/EMEA/APAC payments leads — open before every provider call, every pricing negotiation, and every market-entry review.

• Structured data on 310+ APMs and LPMs, refreshed continuously.
• Country, method, PSP and scheme cross-references in one place.
• Neutral by design — no rev-share, no referral fees, no vendor axe.
• Built with input from 70+ expert calls with practitioners.