Choosing Payment Methods

Last updated 22 October 2026. Copy page as text

TL;DR

• US e-commerce starting stack: Cards + Apple/Google Pay + PayPal. Test BNPL if your order values and margin support it
• B2B/SaaS: Cards + ACH. Compare wires when limits or timing matter. SEPA DD for eligible EU recurring payments
• Global: Cards + major wallets + 1-2 local APMs per priority market.
• Payouts: ACH (cheap, slow) vs RTP/FedNow (instant) vs push-to-card (instant to any debit card).
• Pay-ins and payouts have different fraud profiles. Pay-in is chargebacks and friendly fraud. Payout is ATO and misdirected payments.

You're balancing four things: customer preference, cost, fraud exposure, and operational complexity. Here's how to decide.

---

The Decision Framework

1. Customer Preference

What do your customers want to use? Refuse it and you'll lose sales. Survey data and benchmarks help, but your own abandonment rates help more.

2. Economics

Work out the true cost per method:

• Direct fees (interchange, processing)
• Fraud losses and chargebacks
• Settlement timing, which is a cash flow cost
• Operational overhead

3. Fraud Profile

Every method has its own fraud profile. Your risk tolerance shapes what you accept, and so does what your tools can catch.

4. Integration Complexity

Some methods take real engineering time, so weigh that cost against the expected benefit.

5. Settlement Needs

Cash flow tight? Favor the faster-settling methods, or pay for accelerated settlement.

6. Pay-ins vs Payouts

Think about pay-ins and payouts separately. Pay-ins are how customers pay you, and payouts are how you send money out. The best rails differ:

Pay-ins (receiving money):

• Cards + wallets + BNPL for consumer checkout
• ACH / SEPA Direct Debit for recurring and B2B
• Local APMs for international markets

Payouts (sending money):

• ACH for standard payouts, cheap and 1-2 days
• RTP / FedNow for urgent or instant payouts
• Push-to-card (Visa Direct / Mastercard Send) for instant-to-debit-card UX
• Wires for large, urgent, or international

Different fraud profiles. Pay-in fraud is stolen credentials and chargebacks, while payout fraud is ATO and misdirected payments. A marketplace needs strong controls on both sides.

---

The Cannibalization Problem

Adding payment methods doesn't automatically mean more sales. A lot of the adoption is existing customers switching, not new customers converting.

Why This Matters

Worked example, assumed customer behavior: You add BNPL and see 1,000 BNPL transactions in month one. That's not 1,000 new sales. It might be:

• 300 genuinely new conversions, customers who wouldn't have bought
• 700 existing customers who'd have paid with a card anyway

BNPL costs you 5% and cards cost 2.5%. On those 700 transactions you've just paid an extra 2.5% for nothing.

How to Measure Cannibalization

Before launching a new method:

• Baseline your conversion rate, AOV, and payment method mix
• Track cart abandonment by stage

After launching:

• Compare total conversion rate, not just new method adoption
• Watch for drops in other payment method usage
• Calculate true incremental revenue: New method revenue × (1 - cannibalization rate)

Warning signs of pure cannibalization:

• Total conversion rate unchanged despite new method adoption
• Card transaction count drops in step with new method growth
• Same customers switching methods month over month

Quick Example

Worked example, assumed inputs. Before BNPL launch:

• 10,000 orders/month
• 95% cards, 5% PayPal
• 2.8% blended payment cost

After BNPL launch:

• 10,200 orders/month, up 2%
• 80% cards, 5% PayPal, 15% BNPL
• 3.2% blended payment cost

The math:

• 200 incremental orders × $80 AOV = $16,000 new revenue
• Payment cost before: 10,000 × $80 × 2.8% = $22,400. After: 10,200 × $80 × 3.2% = $26,112. Extra cost = $3,712
• Net benefit: $16,000 × 30% margin = $4,800, less $3,712 extra cost = $1,088

In this case, BNPL is worth it, narrowly. With only 50 incremental orders, on the same 3.2% blended cost, payment cost is 10,050 × $80 × 3.2% = $25,728, or $3,328 extra. That is $4,000 × 30% = $1,200 against $3,328: $2,128 down. The math flips negative.

Hidden Costs of More Methods

It doesn't have to cost more per transaction to cost you:

Reconciliation complexity

Each payment method you add is one more data source to reconcile. Five methods means five reconciliation streams, five sets of edge cases, five vendor relationships.

Subscription/recurring limitations

Methods don't all handle recurring equally:

• Cards: excellent (card-on-file, account updater)
• ACH: good (mandates persist)
• PayPal: good (billing agreements)
• BNPL: poor (built for one-time, not recurring)
• Crypto: very poor (no recurring mechanism)

Running a subscription business? A method that handles recurring badly means customers can't easily subscribe. Or you're handling payment method changes at every renewal.

Refund complexity

Refunds don't work the same way everywhere:

• Cards: straightforward, same rails
• ACH: ACH credit back, or a check if the account closed
• BNPL: coordinate with the provider, unwind the installments
• Crypto: which currency? At what rate? To which wallet?
• Vouchers and cash methods: usually manual, or store credit

One-click / conversion optimization

You've tuned your card checkout for one-click. A new method that needs a redirect, a login, or verification may:

• Cut overall conversion. More choices means more friction.
• Train customers onto slower methods
• Break A/B tests and conversion work already done

When Cannibalization Is Acceptable

Sometimes it's fine, and here's when.

Cost reduction

Compare the full card and ACH fees on the same payments. Include any invoice or software fees, plus ACH minimums, caps and return fees. The difference is your saving.

Fraud reduction

High-fraud customers switch from raw card entry to Apple Pay, and your fraud losses drop.

Customer preference

Customers who strongly prefer a method you don't offer may still buy, but they won't be happy about it. Offering it lifts NPS even with no conversion lift.

Competitive necessity

Every competitor offers BNPL and you don't, so you may lose the customer entirely. The math is "cannibalize yourself or lose them."

The Right Approach

1. Don't add methods speculatively. Have a hypothesis about who'll use it and why.
2. Measure incrementality. Track total conversion, not just new method adoption.
3. Count the total cost. Ops overhead, not just transaction fees.
4. Sunset underperformers. If a method adds complexity and no incrementality, it's gone.
5. A/B test when you can. Show the new method to a subset and compare total conversion.

---

Payment Method Matrix

Method	Cost	Speed	Fraud Risk	Chargeback Risk	Best For
Credit Card	High	T+2-3	Medium-High	High	Retail, e-commerce
Debit Card	Medium	T+1-2	Lower	Medium	Retail, everyday purchases
ACH	Varies by provider and plan (examples)	Provider-dependent	Different	Debit return rules	Recurring, B2B
RTP/FedNow	Low	Instant	Emerging	None	Urgent disbursements
Digital Wallets	Medium	T+2-3	Lower	High (via card)	Mobile, e-commerce
BNPL	High	T+1-2	Lower	Provider handles	Fashion, discretionary
Wire	Flat fee	Same day	High (social engineering)	None	Large B2B

---

Fraud, Risk, and Conversion Matrix

Method	Typical Cost	Fraud Pattern	Dispute Mechanism	Conversion Impact
Credit Card (CNP)	1.89-2.60% + $0.10 interchange	Stolen cards, synthetic ID, card testing	Network chargeback (120 days on Visa/Mastercard; Amex up to 120, with exceptions; Discover: Not published)	Baseline for e-commerce
Credit Card (CP)	1.51-2.30% + $0.10 interchange	Lost/stolen, counterfeit (reduced by EMV)	Network chargeback (120 days on Visa/Mastercard; Amex up to 120, with exceptions; Discover: Not published)	Baseline for retail
Debit Card	0.05% + $0.21 regulated, 0.70-0.80% + $0.15 exempt	ATO, lost/stolen	Network chargeback + Reg E (60 days)	Slightly lower than credit
Prepaid	Similar to exempt debit	Low for merchants (mule risk in specific verticals)	Network chargeback available	Neutral to slightly lower
Card-Token Wallets	Same as card (often CP rates)	Very low (tokenization + biometrics)	Standard card chargeback	Compare completion on eligible mobile devices
Online Account Wallets	3.49% + $0.49	ATO at wallet level	Wallet provider dispute (buyer-friendly)	Compare total completion and fees; PayPal study below
P2P Wallets	Provider's business-payment schedule	ATO, social engineering	Complex (wallet + underlying funding)	Test on your own customers
ACH Debit	Varies by provider and plan (examples)	Unauthorized debits, ATO	Consumer and business return rules	Lower (bank login friction)
ACH Credit	Bank or payout provider pricing	BEC, misdirected payments	Limited; a fraud recall isn't guaranteed	N/A (push, not checkout)
Pay by Bank (US)	Provider and rail pricing	ATO, social engineering	ACH returns (if ACH-based)	Lower (friction), improving
Open Banking (UK/EU)	Provider's merchant schedule	ATO (mitigated by SCA)	Very limited (push)	Measure checkout completion
RTP/FedNow	Your bank or payout provider's fee	Social engineering, BEC	Rail-specific recovery process	N/A (mostly disbursements)
Push-to-Card	Your payout provider's fee	ATO, misdirected payouts	Ask about eligible recovery routes	N/A (payouts only)
Wire	Your bank's domestic or international schedule	BEC, vendor impersonation	Ask the bank about recall; recovery isn't guaranteed	N/A (B2B only)
BNPL	Provider's merchant agreement	First-party "never pay," return abuse	Provider's terms	Measure total conversion and contribution
Crypto via PSP	Provider's acceptance and conversion fees	Compromised wallets, AML exposure	Provider's terms	Niche
Mobile Money	Provider and market-specific schedule	SIM swap, social engineering	Provider-specific	Essential in covered markets
Carrier Billing	Provider and market-specific agreement	SIM swap, unauthorized charges	Carrier dispute process	Test paid completion
eCash/Vouchers	Provider's merchant agreement	Low (cash payment)	Merchant and provider terms	Count paid vouchers
SEPA Direct Debit	Provider's merchant schedule	Unauthorized mandates	8-week refund right for authorized consumer Core debits	Check mandate completion and returns

Discover doesn't publish its dispute windows. For your own response, work to the date on your notice.

Don't read straight down that cost column. The card rows are interchange, the network's cost before your processor's markup. The wallet, BNPL and carrier rows are the provider's all-in merchant rate, markup included. They aren't the same measurement. Card interchange comes from Visa's US schedule of 18 April 2026 and Mastercard's of 17 April 2026. Blended across a normal card mix, that's about 0.89% + $0.158 in person and 1.36% + $0.152 online. The derivation is published.

---

Fraud Pattern Details by Method

Card-Not-Present (CNP) Credit

• Primary attack: stolen credentials from breaches and dark web purchases
• Secondary: synthetic identity, built from mixed real and fake data
• Pattern: high-velocity testing, then larger purchases reshipped to mules
• Mitigation: 3DS, AVS, CVV, velocity limits, device fingerprinting

Card-Token Wallets (Apple Pay, Google Pay)

• Compare wallet fraud losses with raw CNP on matched customers, devices and order values
• Tokenization kills stored credential theft
• Biometric authentication blocks unauthorized use
• Main risk: social engineering to add a stolen card to the wallet, called provisioning fraud
• Mitigation: network and issuer controls at provisioning, device binding

Online Account Wallets (PayPal, Skrill)

• Primary attack: account takeover via credential stuffing and phishing
• Secondary: first-party "item not received" claims
• Pattern: ATO, change the shipping address, buy high-value items
• Disputes: the wallet provider decides, and usually leans buyer-friendly
• Mitigation: wallet-level 2FA, shipping to confirmed addresses

ACH

• Primary attack: unauthorized debits, a fraudster pulling from a victim's account
• Secondary: ATO leading to debits that look authorized
• Return codes: R10 (unauthorized), R29 (corporate unauthorized)
• Pattern: fraudster gets routing and account numbers, then starts pulling
• Mitigation: account verification (Plaid and similar), micro-deposits, behavioral analysis

Real-Time Payments (RTP/FedNow/Faster Payments)

• Primary attack: social engineering, or "authorized push payment" fraud
• Pattern: the victim is tricked into sending money. Romance scams, invoice fraud.
• The fraudster targets the sender, not the recipient. Merchants receiving RTP see low fraud.
• Mitigation: Confirmation of Payee, friction on first-time recipients

BNPL

• Primary attack: first-party "never pay." The customer never intends to finish the installments
• Secondary: return abuse. Buy, return, stop payments, keep the refund.
• Pattern: apply at several providers at once, max out the credit
• Mitigation: cross-provider data sharing (still emerging), identity verification

Mobile Money (M-Pesa, etc.)

• Primary attack: SIM swap, where the fraudster takes over the phone number
• Secondary: social engineering. "Send money to unlock prize."
• Pattern: SIM swap, drain the wallet, transfer to a cash-out agent
• Mitigation: carrier security, transaction limits, agent monitoring

---

Conversion Characteristics

Wallet Conversion: What to Check

• Apple Pay / Google Pay on mobile: no card re-entry; compare completion on eligible devices. Stripe's Apple Pay result and scope doesn't establish a lift for both wallets
• PayPal, for PayPal users: saved credentials. PayPal reports 28% higher checkout conversion than other methods in Nielsen-commissioned research covering over 15,000 US consumers and over 99,000 transactions, July to September 2020 (VENDOR, January 14, 2021, accessed October 22, 2026). That's its study, not your forecast
• BNPL: financing spreads the payment; compare total conversion, fees and returns
• Stored card / card-on-file: no re-entry; compare repeat-customer completion with your own baseline

Baseline

• Credit card with manual entry
• Debit card with manual entry

Bank and Voucher Conversion: What to Check

• Pay by Bank / Open Banking: measure bank-login and redirect completion on matched customers. The method alone doesn't establish a lower conversion rate
• ACH: measure setup completion and confirmed payments, including verification steps
• eCash / Vouchers: count paid vouchers separately from vouchers issued
• Crypto: highly variable. Niche audience, heavy friction for everyone else.

You're comparing conversion with cost. A cheaper method can still cost you sales if customers won't complete it. A wallet or BNPL option has to earn its fees. Measure total completion and contribution on your own customers.

---

Rails vs. Products: An Important Distinction

Separate rails from products. Rails are the infrastructure, and products are what your customer actually sees.

Rails (Underlying Infrastructure)

• Card networks: Visa, Mastercard, Amex, Discover
• ACH: the Nacha network for US bank transfers
• RTP: The Clearing House's real-time rail
• FedNow: the Federal Reserve's real-time rail
• SEPA: European bank transfer infrastructure
• Faster Payments: the UK real-time rail
• PIX: Brazil's instant rail, run by the central bank
• UPI: India's Unified Payments Interface, run by NPCI
• SWIFT: messaging for international wires, and not a settlement rail itself
• Blockchain networks: Bitcoin, Ethereum, Solana

Products (Customer-Facing)

• Credit, debit and prepaid cards, built on card network rails
• Apple Pay and Google Pay: a tokenization layer on card rails
• PayPal and Venmo: account wallets that pull from cards or ACH
• Zelle: a product built on RTP or bank networks
• Cash App: cards, ACH, or internal transfers
• Klarna and Affirm: BNPL products, often funded by cards or ACH
• "Pay by Bank" products: built on ACH, Open Banking APIs, or local rails
• Instant card payouts (Visa Direct, Mastercard Send): same card rails, pushed instead of pulled

Why this matters:

• Fraud and dispute rules come from the rail, not the product
• A Venmo payment funded by a card falls under card chargeback rules
• A Venmo payment funded by bank balance follows Venmo's policies
• When you evaluate a payment method, find out which rail it runs on

---

Industry-Specific Recommendations

E-commerce / DTC (US Focus)

• Cards. You don't get a choice
• Digital wallets: Apple Pay, Google Pay, PayPal
• Test BNPL where customer demand, margin and order values justify it
• Local payment methods if you sell internationally

Subscription/SaaS

• Cards, primary
• ACH for B2B customers who prefer it
• Backup payment methods for failed cards

B2B

• ACH for most transactions, for the cost savings
• Cards for small transactions and customers who insist
• Wire for large, urgent payments
• Ask your processor about Visa CEDP, Mastercard Level 2/3 and Amex enhanced data for eligible cards

Marketplace

• Cards and PayPal for buyers
• ACH for seller payouts
• Real-time payments if sellers want instant payouts

Healthcare

• Cards for patient payments
• ACH for insurance reimbursements
• Financing or payment plans for large balances

---

What Should Merchants Actually Use?

Treat this as a default starting stack, then adjust for your business.

US E-commerce / DTC

Must have:

• Credit and debit cards (Visa, Mastercard, Amex, Discover)
• Apple Pay and Google Pay
• PayPal

Add if relevant:

• BNPL (Klarna, Affirm, Afterpay) where a test shows extra contribution after fees and returns
• Venmo or Cash App Pay if your demographic skews young US
• Shop Pay if you're on Shopify. Saved credentials convert well.

Optional / situational:

• Crypto, only for a crypto-native audience or real demand
• Pay by Bank. It's cheaper, but it costs conversion. Worth a look on high-ticket items.

Don't bother (usually):

• Wire transfers. They're not for consumer checkout.
• ACH direct debit for one-time purchases. Too much friction.

B2B / SaaS / Invoice-Based

Must have:

• Cards, for smaller invoices and expense-card customers
• ACH, for larger invoices and recurring payments. The cost savings aren't small.

Add if relevant:

• Pay by Bank or instant bank verification, which makes ACH setup faster
• SEPA Direct Debit for EU customers
• Wire for large one-time payments where ACH limits or timing matter

Optional / situational:

• BNPL or financing, for SMB customers who want to spread payments
• Crypto, only on meaningful demand. It's rarely worth the complexity.

Operational note: for recurring SaaS, turn on card account updater and dunning. Expired cards are the biggest source of involuntary churn.

Global E-commerce / Marketplaces

Must have:

• Cards, for global acceptance
• Major wallets: PayPal, Apple Pay, Google Pay

Add by region:

• EU: SEPA Direct Debit (recurring), iDEAL (Netherlands), Bancontact (Belgium), PayPal/Klarna (Germany)
• UK: Open Banking / Pay by Bank, Direct Debit
• Brazil: PIX (essential), Boleto (declining but still used)
• Mexico: OXXO (essential for unbanked)
• India: UPI (essential), Paytm
• China: Alipay, WeChat Pay (essential for Chinese customers)
• Southeast Asia: GrabPay, GoPay, local wallets
• Africa: M-Pesa, MTN MoMo (essential in covered markets)
• Japan: Konbini, PayPay, JCB

For marketplaces specifically:

• Real-time payouts. RTP/FedNow for US sellers, Faster Payments for the UK.
• Local payout rails in each market
• Payout providers (Stripe Connect, Adyen for Platforms, Payoneer) absorb the complexity

Gaming / Digital Content

Must have:

• Cards
• PayPal

Add if relevant:

• Paysafecard, which matters in gaming, especially the EU
• Carrier billing (Boku and similar) for mobile games and apps
• Crypto, if the audience is crypto-native, Web3, or NFT

Watch out for:

• Gaming runs high chargeback rates, so you'll need strong fraud prevention
• Carrier billing has high fees and excellent conversion

High-Risk / Regulated Verticals

For gambling, adult content, cannabis (where legal), forex, and the like:

Common patterns:

• Fewer processor options. Expect to pay higher rates.
• Wallets like Skrill and Neteller matter in gambling and forex
• Cash and voucher methods (Paysafecard) cut chargeback exposure
• ACH and bank transfers often beat cards on economics

Key considerations:

• Build relationships with processors who know your vertical
• Watch your chargeback ratios obsessively. Network thresholds don't bend.
• Plan for processor redundancy. Getting cut off isn't rare.

Decision Framework Summary

1. Start with cards plus major wallets. Apple Pay, Google Pay, PayPal.
2. Test BNPL where discretionary purchases, customer demand and contribution justify it.
3. Add local APMs for each significant international market.
4. Consider ACH or Pay by Bank where the savings beat the conversion hit.
5. Add niche methods (crypto, carrier billing, vouchers) only on clear demand.
6. Monitor and adjust on your actual conversion, fraud, and cost data.

The goal is covering what your customers want, without drowning in complexity. Start simple, add the methods that move the needle, and cut the ones that don't earn their operational cost.

---

Push vs Pull and Reversibility

This is the framework that matters most for payment risk:

Method	Push/Pull	Reversible?	Who Can Reverse	Reversal Window
Credit Card	Pull	Yes	Cardholder/Issuer	120 days on Visa/Mastercard; Amex up to 120, with exceptions; Discover: Not published
Debit Card	Pull	Yes	Cardholder/Issuer (Reg E)	60 days
ACH Credit	Push	Limited	Originating bank for qualifying errors	5 banking days from settlement for an error reversal; not a general fraud recall
ACH Debit	Pull	Yes	Receiving bank	Debit return timing
RTP/FedNow	Push	No	Only voluntary refund	N/A
Wire	Push	No	Only bank cooperation	N/A
PIX/UPI/etc.	Push	Very limited	Scheme-specific	Varies
SEPA Credit	Push	Limited	Very limited recall	10 days
SEPA Direct Debit	Pull	Yes	Customer	8 weeks (no questions)

Why this matters:

• Pull methods like cards and direct debit put the merchant at risk. You ship, the customer disputes, the money comes back.
• Push methods like RTP and wire put the sender at risk. Once it's sent, it's gone. Fraudsters love push payments.
• Reversibility sets your dispute exposure. Irrevocable methods have zero chargebacks, and they leave you zero recourse if you're defrauded.

---

Regional Regulation Snapshot

Regulation changes payment economics a lot by region.

United States:

• Regulated debit interchange is capped at 0.05% + $0.21, plus a $0.01 fraud-prevention adjustment for eligible issuers (Federal Reserve, checked 22 October 2026)
• No cap on credit. Consumer credit runs 1.51-2.30% + $0.10 in person and 1.89-2.60% + $0.10 online (Visa 18 April 2026, Mastercard 17 April 2026).
• There isn't much regulation on payment methods overall

European Union:

• Interchange Fee Regulation caps: 0.2% consumer debit, 0.3% consumer credit, intra-EEA
• PSD2 requires Strong Customer Authentication on most e-commerce
• SEPA standardizes payments across Europe

United Kingdom:

• Interchange caps close to the EU, retained post-Brexit
• Open Banking mandates. Banks have to provide API access.
• Heavy adoption of Faster Payments and Direct Debit

India:

• UPI merchant discount rate is zero or near-zero for many categories
• The government subsidizes digital payments to drive adoption
• Check current monthly transaction counts in NPCI's UPI statistics before sizing that market

Brazil:

• PIX is run by the central bank at near-zero cost
• Boleto, the bank slip, still matters for the unbanked
• Card interchange is high by global standards

China:

• Compare the local wallet options your customers already use
• QR code payments are the standard
• Cross-border restrictions limit foreign card acceptance

Why this matters. Evaluating payment economics across borders? Local regulation changes the math. The EU's 0.3% eligible consumer-credit interchange cap isn't an all-in merchant rate. Compare your provider's full country-specific fees, including fixed charges and currency conversion.

---

The Issuer's Perspective

How issuers see each method shapes what you should do.

What Issuers Care About

Interchange revenue. Credit cards generate the most interchange. Debit generates less, and ACH generates none. Issuers want customers on credit cards.

Fraud losses. Issuers eat fraud losses on unauthorized transactions. They prefer secure methods (chip, tokenization, biometrics) over manual entry.

Dispute costs. Processing chargebacks costs issuers real money in staff time, systems, and investigation.

Float. On credit cards, issuers front the money before collecting from cardholders. On debit, it comes out of existing deposits.

Customer experience. Declines frustrate cardholders. Issuers want high approval rates, but not at the price of fraud.

Why This Matters for You

Issuers influence:

• Approval rates on your transactions
• Which fraud signals get transactions declined
• Chargeback outcomes. Issuers often side with the cardholder.
• Card reissuance, which'll break your stored credentials

High fraud rates, excessive chargebacks, or odd transaction patterns get you flagged. Issuers start declining more of your transactions, and some block your MID entirely.

From the issuer side, merchant reputation matters. Check whether your approval rate changes alongside fraud and disputes, holding issuer and transaction mix steady.

Building Issuer Trust

• Keep chargeback rates well below network thresholds
• Use modern security features: 3DS, tokenization
• Give cardholders a descriptor they'll recognize
• Respond promptly to fraud alerts and retrieval requests
• Don't retry declined transactions over and over

---

Operational Considerations

Reconciliation Across Methods

Each payment method reconciles differently.

Cards. Match batch totals to processor reports to bank deposits. Account for fees deducted from settlement.

ACH. Track origination files against returns, and monitor return rates by customer and type.

Real-time payments. Individual confirmation for each transaction. Simpler to reconcile, but higher volume.

Mixed methods. More methods means messier reconciliation, so build systems that handle multiple sources.

Reporting and Analytics

Track key metrics by payment method:

• Volume and value
• Acceptance and approval rate
• Decline reasons
• Fraud rate
• Chargeback and return rate
• Settlement timing
• Effective cost

Hypothetical comparison: ACH returning 3% while cards charge back 1%? Compare the reasons, loss amounts and customer segments before moving volume. Wallet transactions running half the fraud rate? Check comparable orders and costs before prioritizing wallet checkout.

Disaster Recovery

What happens when a payment method fails?

Card processor outage. You'll want a backup processor, or the ability to fail over. ACH delays. Ask your provider whether Same Day ACH is available and what confirmation and payout timing it offers. Don't treat a pending debit as paid Bank issues. Keep relationships with more than one bank. Network outages. They're rare, but carrying Visa, Mastercard and Amex gives you redundancy.

Write the contingency plans down, because a payment outage hits revenue directly.

---

Next Steps

Building your initial payment stack?

1. Card Payments - Start with card fundamentals
2. Digital Wallets - Add Apple Pay, Google Pay, PayPal
3. Cheat Sheet - Quick reference for all methods

Optimizing payment costs?

1. Bank Transfers - ACH for lower-cost recurring payments
2. Real-Time Payments - RTP/FedNow for instant, low-cost payouts
3. Interchange Optimization - Reduce card processing costs

Expanding payment options?

1. Alternative Methods - BNPL, local APMs, crypto
2. International Payments - Cross-border method selection
3. Going Global - Market-specific recommendations

See Also

• Cheat Sheet - All key tables in one place
• Card Payments - Deep dive on card economics
• Real-Time Payments - RTP, FedNow, push-to-card
• Alternative Methods - BNPL, local APMs, crypto
• Digital Wallets - Apple Pay, Google Pay, PayPal
• Bank Transfers - ACH and bank payment methods
• Checkout Conversion - Conversion optimization
• Fraud Prevention - Fraud considerations by method
• Chargeback Prevention - Reducing disputes
• Going Global - International considerations
• Benchmarks - Method performance targets