Dominant North American payment methods: Beyond cards with crypto

Dominant North American payment methods like cards, digital wallets, and BNPL are fragmented by design: consumer preferences vary by channel, demographic, and use case.

 For enterprises operating in or selling into North America, the hard part isn’t turning on payments, but rather managing cost, fraud exposure, disputes, and cross-border settlement while keeping checkout conversion high. Crypto and stablecoin payments are increasingly evaluated as an additional rail for specific problems: cross-border collection, faster settlement, and reducing FX and intermediary complexity in certain flows.

Optimizing the checkout experience for local markets

North America is a high-expectation market: customers are used to fast checkout, saved credentials, and familiar payment buttons. Practical implications:

Offer multiple payment options by channel

• Ecommerce: cards + major digital wallets are table stakes; BNPL is increasingly expected in certain verticals.
• In-person: contactless card and wallet acceptance is standard.
• B2B: bank transfer rails (e.g., ACH in the US, ACSS in Canada) matter for invoice payments and larger tickets.

Localize the interface, not just pricing

• Language coverage commonly includes English, French, and Spanish depending on where you operate and who you sell to.
• Reduce form friction (address validation, autofill, fewer redirects) to lower cart abandonment.

Use multicurrency intentionally

• Let customers view prices and pay in their local currency when you serve international buyers.
• Be explicit about FX rates and fees to reduce disputes and support tickets.

Where crypto/stablecoins can fit in checkout (without replacing cards):

• As an additional payment option for customers who already hold stablecoins.
• As a pay-by-bank alternative in some cross-border scenarios, where the business prefers digital-dollar settlement over card rails and chargeback exposure.
• As a backend settlement rail even when the front-end experience remains familiar (e.g., user pays via a local method; treasury settles in stablecoins between entities). This is implementation-dependent and requires careful compliance design.

Payment security, fraud, and regulatory compliance (PCI DSS, AML)

North America is a high-fraud environment, especially for card-not-present transactions. In 2023, North America accounted for over 42% of global fraud by value, despite representing less than 7% of banked individuals (Juniper Research). That mismatch drives a security posture that’s both technical and operational.

What enterprises must cover for card payments (baseline)

1. PCI DSS: If you store, process, or transmit cardholder data, PCI DSS compliance is a requirement. Architect to minimize PCI scope wherever possible (tokenization, hosted fields, segregated environments).
2. Strong customer authentication where applicable:Tools like 3D Secure can reduce certain fraud and dispute rates for online card payments, at the cost of potential friction.
3. Disputes and chargebacks: Chargebacks are governed by card network rules and bank processes. You need playbooks for evidence collection (proof of delivery, logs, customer comms) and analytics to identify root causes.

How crypto and stablecoins change the risk model (and what they don’t solve)

1. Chargebacks: Card network chargeback rules don't apply to onchain transfers, but that doesn't mean dispute resolution disappears. The infrastructure needs to support it differently: pre-transaction screening and address risk checks, clear refund policies with defined SLAs, programmatic hold-and-release logic where settlement can be staged rather than instant, and customer support workflows that handle exceptions before they escalate. The Open Money Stack is designed to support these controls at the infrastructure layer, so payment teams can offer dispute resolution without reverting to legacy card-network mechanics.
2. Compliance: Stablecoin acceptance and settlement can trigger obligations under AML programs depending on your role (merchant, marketplace, PSP, money transmitter), geography, and flow design. Treat compliance as a product requirement.

Challenges of cross-border payments and currency conversion

Cross-border payments are where many enterprises start evaluating stablecoins, because the pain is measurable:

• Currency conversion is unavoidable when you sell into multiple markets. The US, Canada, and Mexico operate on floating exchange rates, where market supply and demand drive pricing. Converting via banks, online platforms, or FX brokers introduces tradeoffs (fees, speed, operational risk, counterparty exposure).
• Multicurrency pricing and settlement add complexity. Display currency, settlement currency, and treasury currency may differ. Reconciliation becomes harder across PSPs, acquiring banks, and local payment methods.
• Regulatory and reporting requirements Cross-border collection and FX can require specific recordkeeping, disclosures, and customer transparency around fees and rates.

Where stablecoins can help (specific, not universal)

Stablecoins are not a blanket replacement for local payment methods. They can be useful when the business wants:

• Digital-dollar settlement without relying on multiple correspondent banking relationships for every corridor.
• Faster movement of value between entities (e.g., subsidiary-to-HQ treasury operations), subject to internal controls and compliance.
• Reduced FX touchpoints in certain workflows by standardizing on a stable settlement asset (often USD-denominated), while still presenting local currency prices at checkout.

The right question for enterprise teams is: Which part of the flow is failing—authorization, conversion, settlement speed, fees, or reconciliation? Stablecoins tend to address settlement and treasury friction more directly than front-end consumer preferences in North America.

Polygon Labs' Open Money Stack is designed to address these problems. It’s vertically integrated, end-to-end infrastructure for global stablecoin payments, with ramps, onchain settlement, wallets, and chain services all rolled into one place. 

We built it so enterprise payment teams can keep their front-end checkout familiar: cards, wallets, BNPL, whatever converts. At the same time, in the back end, institutions can route settlement through stablecoin rails where the cost and speed gains are clearest. 

The stack handles the bridge between those two worlds: local payment in, stablecoin settlement across borders, local payout out.

Dominant North American payment methods (cards, digital wallets, BNPL): what to support and why

North America does not have a single dominant method across all contexts, but there are clear patterns:

Cards remain foundational

• Major networks (Visa, Mastercard, American Express, Discover) are widely used online and in-person.
• In 2023, credit cards represented 33% of ecommerce transaction volume and 42% of point-of-sale transaction value in North America (excluding Mexico).

Implication: even if you add stablecoins, you will almost certainly still run a card program.

Digital wallets are mainstream (especially ecommerce)

• Digital wallets are growing with mobile and ecommerce adoption.
• In the US, digital wallets accounted for 37% of ecommerce transaction value in 2023.

Implication: wallet buttons reduce friction and can improve conversion, especially on mobile.

BNPL continues to expand

• BNPL providers (e.g., Affirm, Afterpay, Klarna) are growing in penetration.
• The US BNPL market was valued at about $1.6 billion in 2022 and is projected to grow at a 24.3% CAGR from 2023–2030.

Implication: BNPL is a conversion lever for certain segments, but it adds operational considerations (returns, disputes, underwriting decisions by provider).

Bank transfers matter for B2B

• US: ACH
• Canada: ACSS
• These rails are typically cheaper than cards or wires but not instantaneous.

Implication: B2B payment strategy should treat bank rails as first-class, alongside cards.

Implementation checklist for enterprises adding crypto and stablecoins (without breaking what works)

A practical way to adopt stablecoins in North America is to start with constrained, high-signal use cases:

1. Define the scope: Consumer checkout option vs. B2B invoicing vs. internal treasury settlement.
2. Decide the asset and settlement policy: Which stablecoins, which networks, and what your acceptance/refund policy is.
3. Design compliance and controls: AML program alignment, sanctions screening, transaction monitoring, audit logs, and retention.
4. Harden operational workflows: Address management, payment confirmation rules, refund handling, and customer support scripts.
5. Plan reconciliation: Map onchain transaction IDs to invoices/orders; define accounting treatment and reporting.
6. Keep checkout familiar: Do not force crypto where cards/wallets are the expected default; offer it where it reduces friction or cost for a defined segment.

Conclusion

North America’s payments landscape is defined by choice: cards, digital wallets, BNPL, and bank transfers all matter, and fraud and compliance expectations are high. Crypto and stablecoin payments are best evaluated as an additional rail, particularly for cross-border settlement, treasury movement, and specific customer segments, rather than a replacement for dominant North American payment methods.

Polygon’s role in this stack is infrastructure: enabling stablecoin transactions with low fees and predictable settlement behavior, so payment teams can design flows that are faster to settle and easier to operate across borders while keeping security, compliance, and checkout conversion as first-order requirements.

‍