The payment reality of digital commerce
Cross-border checkout fails in two ways merchants rarely see separately. The shopper's preferred method is missing — a Dutch buyer expects iDEAL, a Brazilian buyer expects PIX — so they abandon at the payment step rather than switch to a card. Or the method is offered but the charge routes to an acquirer unlikely to approve it, and a legitimate purchase declines for reasons that have nothing to do with the shopper, the product or their credit history.
Refunds and marketplace payouts compound it. A retailer selling through multiple storefronts, or a marketplace paying out to sellers across markets, often runs collection and payout through separate systems that reconcile on separate schedules — so a return or a seller disbursement takes longer to resolve than the sale itself did, and finance ends up matching two ledgers by hand at month end.
A lot of "global" checkouts still send every card down one acquirer. We route each one to whichever acquirer performs best for it.
How CyberPay helps
Four capabilities, built around where digital commerce actually loses money: at checkout, on refunds, and in marketplace payouts run apart from collection.
Local method coverage per market
iDEAL, PIX, cards and the other methods each market actually uses, added market by market rather than defaulting to cards everywhere and hoping international shoppers adapt.
Acquirer routing for authorization
Each card transaction routed to the acquirer that performs best for it, so authorization holds up across markets with different underwriting appetites instead of dropping wherever a single acquirer is weakest.
Refunds and marketplace disbursements
Refunds and seller payouts run on the same platform as collection, reconciled together rather than through a separate process finance has to match by hand.
Fraud screening tuned to retail
Risk scoring calibrated to the dispute and chargeback patterns retail and marketplace transactions actually produce, rather than a generic model tuned for a different kind of business.
Methods and markets
A storefront or marketplace typically needs a mix of global cards, regional bank-based methods and, increasingly, crypto acceptance for customers who hold it:
- Cards, Apple Pay and Google Pay — global acceptance at checkout, authorized through the acquirer with the strongest record for that traffic.
- Local bank methods — iDEAL, PIX, BLIK and equivalents, cleared where a card isn't the first choice.
- Crypto on-ramp (USDC, USDT) — accepted alongside cards where a customer base calls for it.
- Refunds and marketplace payouts — issued on the same platform used for collection.
CyberPay covers 73 markets across 6 regions — see the full coverage map.
Refunds, chargebacks and marketplace payouts settle through the same reconciliation as pay-ins, whichever method or market a transaction used, so finance is reading one report instead of stitching several together.
Integration
A storefront can launch checkout fast on the Hosted Cashier, or call the Direct API to keep checkout on its own storefront end to end. Pay-ins, refunds and marketplace payouts run on the same integration, with Query-Transactions for reconciliation. Build and test against the sandbox before going live.
Use cases
Three ways digital commerce businesses use CyberPay to hold authorization steady across markets and keep collection and payout on one platform, instead of stitching several systems together as they grow.
A DTC brand expanding into Europe and Latin America
A direct-to-consumer brand moving beyond its home market adds the payment methods each new market expects — SEPA and BLIK in Europe, PIX in Brazil — without a separate integration per region, and routes card transactions for the highest chance of authorization in each, so expansion doesn't mean rebuilding checkout every time.
A marketplace paying sellers
A marketplace collects from buyers across multiple markets and pays sellers out on a schedule, in the seller's own currency where supported, with both sides reconciled on one platform rather than run through separate systems that leave finance guessing at true margin.
A retailer consolidating multiple PSPs
A retailer running several processors to cover different markets or methods moves onto one integration, keeping the same method coverage while gaining a single acquirer-routing layer and one reconciliation report instead of several.
Frequently asked questions
What payment methods do you support for e-commerce?
Cards, Apple Pay, Google Pay, local bank methods including iDEAL, PIX and BLIK, and crypto on-ramp, depending on the market. Coverage spans 73 markets across six regions.
Which markets do you cover?
73 markets across six regions — Europe, Asia-Pacific, Latin America and the Caribbean, Africa, the Middle East and North Africa, and North America. See the full coverage map.
How do refunds work?
Refunds are issued on the same platform used to collect the original payment and reconciled alongside it, rather than through a separate process that finance has to match by hand.
Can you pay out marketplace sellers?
Yes. Seller disbursements run on the same integration used for collection, scheduled or on demand, in the seller's own currency where supported.
What does integration involve?
One integration reaches card networks, local bank methods and crypto acceptance together — you don't add a separate connection per market or method as you expand.
Ready to accept wherever you sell?
One integration for cards, local methods, refunds and marketplace payouts, across every market you sell into.