Card payments, unified.
Process global card schemes through one Paytone integration. Tokenization, 3-D Secure 2, network-level optimizations, and recurring support all sit behind the same payment object — without provider-specific glue code.
Every major card scheme, plus the regional ones that matter.
Paytone supports the global networks digital businesses depend on and the regional schemes that actually convert in local markets.
Visa
Visa credit, debit, and commercial cards across every region we process in, with full support for token services and account updater flows.
Mastercard
Mastercard credit and debit with network tokens, Maestro support, and 3-D Secure 2 fall-through for issuers across Europe, the Americas, and APAC.
American Express
Amex consumer and corporate cards with the higher-ticket considerations Amex transactions typically carry — routing aware, reconciliation aware.
Discover
Discover and Diners Club for US and select international flows, surfaced through the same token-based vault and lifecycle as every other scheme.
JCB
JCB acceptance for APAC merchants and cross-border traffic from Japanese cardholders, integrated through partner acquirers in supported regions.
Regional schemes
Local card networks where domestic acceptance materially outperforms global schemes — added where merchants ask for them and acquirers support them.
Everything a serious card flow needs.
The features below sit behind the same API call. You don't pick and choose plugins — you turn them on through configuration.
Tokenization
PAN data is replaced with secure tokens at capture. Your systems never see raw card numbers — even your reconciliation pipeline operates on tokens.
3-D Secure 2
Frictionless authentication where issuers allow, step-up challenge only where necessary. Liability shift handled, exemption logic configurable.
Network optimizations
Network token rails, account updater, and scheme-level enhancements applied automatically where the acquirer and issuer both support them.
Recurring & CoF
Cardholder-initiated and merchant-initiated transactions with stored credentials, scheme-compliant indicators, and lifecycle event tracking.
Account updater
Scheme-driven updates to stored cards — keep recurring revenue flowing when issuers reissue cards or change BIN ranges.
BIN-aware routing
Route by BIN, issuer country, currency, and historical approval rate. Each transaction goes to the acquirer most likely to authorize it.
A single call, every scheme.
Card payments share the same payment object as every other method in Paytone. Specify method: "card" and let the routing engine handle scheme detection, acquirer selection, and 3-D Secure flows.
A clean, predictable surface
Send the amount, currency, and customer reference. Paytone identifies the BIN, picks the best acquirer for the geography and currency, and runs 3-D Secure where the issuer requires it. The response tells you which provider handled the transaction.
- Idempotent creates — safe to retry on network errors without duplicating charges.
- Webhooks on every state change with signed payloads.
- SDKs for Node, Python, Go, and Ruby. REST for everything else.
Card payments, on paper.
The capabilities you'll need to brief into a procurement or risk review, summarized.
- Supported regions
- EU, UK, US, Canada, LATAM, APAC, and select MENA markets — exact coverage depends on the acquirers connected to your account.
- Settlement currencies
- Settle in major currencies including EUR, GBP, USD, CAD, AUD, BRL, and others depending on acquirer support.
- Refund window
- Refunds supported within the scheme's chargeback window — partial and full, with idempotent refund creation and webhook lifecycle events.
- Dispute handling
- Chargeback and pre-arbitration events surfaced as webhooks with evidence submission supported through the dashboard and API.
- Recurring support
- Cardholder-initiated and merchant-initiated transactions with stored credential indicators and scheme-compliant transaction types.
- Network token availability
- Network tokens issued via Visa Token Service and Mastercard MDES where the acquirer supports them, with automatic fall-through to PAN.
Run cards on one integration.
Talk to the team about your card volume, your acquirers, and what it would take to consolidate it all behind a single payment object.