Options catalogue · one API

Payment gateway options — every acceptance shape on one API.

topropay's unified gateway exposes acceptance as a set of options: secure card, mobile, ACH, ecommerce, international, crypto, recurring and licensed high-risk. Enable the options you need from the dashboard; add more without re-integration.

Book an options review Read the API docs
  • Secure card PCI L1 vault · selective 3DS2
  • Mobile Apple Pay · Google Pay · SoftPOS
  • ACH NACHA · same-day · R-code retries
  • Ecommerce Hosted · fields · SDK checkout
  • International 40+ markets · local rails
  • Crypto Stablecoins · majors · L2 via partners
  • Recurring Network tokens · updaters
  • High-risk Licensed verticals · panel routing
Eight core options · one merchant record · one dashboard.

Key benefits

Why offering the full option menu pays off

Four properties that show up the moment a merchant stops managing a separate provider for each option and starts running them all through one platform.

One integration for every option

Turn options on or off from the dashboard — no re-integration when the merchant enables mobile, adds ACH, or expands into international.

Same PCI posture across options

Every card-shaped option inherits the platform's PCI DSS Level 1 vault and tokenisation. The merchant doesn't re-scope PCI when a new option turns on.

Routing tuned per option

Card options route across the acquiring panel; bank-rail options ride the partner rail; crypto options route through licensed partner crypto gateways. One routing engine, per-option policies.

Reconciliation across every option

Settlements, fees, refunds and disputes from every enabled option normalise into one ledger. Daily exports tagged by option, provider, currency and merchant.

How the option menu runs underneath

From option toggle to settled ledger row in four steps

What happens between the merchant enabling an option and a settled row in the reconciliation feed — and where the platform sits inside that chain.

  1. 01

    Pick your options

    The merchant enables the options relevant to their traffic — secure card, mobile, ACH, ecommerce checkout, international rails, crypto, recurring, high-risk panel — from a dashboard checklist.

  2. 02

    Route per authorisation

    The unified routing engine picks the optimal connected provider per authorisation based on BIN, currency, country pair, method and risk signals.

  3. 03

    Cascade & retry

    Soft declines cascade to the next ranked provider inside the same authorisation without surfacing to the buyer. Bank-rail R-codes trigger scheme-aware retries.

  4. 04

    Settle & reconcile

    Settlement files from every provider normalise into one ledger; the merchant's finance team reads one export instead of one per provider.

Every option in detail

The eight core payment gateway options for website and API acceptance

Each option gets a dedicated block — what it covers, what makes it distinctive, and how it inherits the platform's compliance posture.

Secure

secure payment options with a PCI L1 vault underneath

Card capture into the platform vault before any acquirer sees it; PAN never lands on the merchant origin; selective EMV 3DS2 challenges per PSD2 exemption logic; network tokens (VTS, MDES) by default for card.

Mobile

mobile payment options across wallets and SoftPOS

Apple Pay, Google Pay and Click to Pay on the online checkout; SoftPOS / Tap-to-Phone for in-person acceptance via licensed partner terminals; same authorisation engine as web card on the back.

ACH

ach payment options with NACHA mandate handling

US ACH debits (WEB, TEL, PPD, CCD), ACH credits for payouts and same-day ACH where supported. R-code-aware retries; mandate evidence captured at first debit and retained per NACHA rules.

Ecomm

ecommerce payment options across hosted, embedded and SDK

Drop-in hosted checkout, embedded hosted-fields, or low-level SDK — three integration shapes share the same back-end. PCI scope shrinks with hosted; UI control expands with SDK.

Global

international payment options across 40+ markets

SEPA (EU), Bacs (UK), PIX (BR), iDEAL (NL), Bancontact (BE), Interac (CA), PayID / OSKO (AU), plus card acceptance across the connected acquirer panel per market.

Crypto

crypto payment options via licensed partner gateways

Stablecoins (USDC, USDT, DAI), majors (BTC, ETH, SOL) and L2 networks delivered through licensed partner crypto gateways with VASP / MiCA-relevant authorisations. Optional conversion-on-receipt keeps treasury fiat-only.

Recurring

recurring payment options across card and bank rails

Card-on-file with network tokens and scheme account updaters; SEPA Direct Debit and recurring ACH with mandate handling; PIX-Recorrência where supported. Smart retries schedule around soft declines.

High-risk

high risk payment gateway options for licensed verticals

Chargeback-aware routing across the connected panel for licensed high-risk verticals — subscriptions, travel, ticketing, licensed gaming, nutraceuticals. Grey and black-market verticals are out of scope regardless of option shape.

Main use cases

Where mixing payment gateway options earns its keep

Six recurring merchant shapes that benefit from combining multiple gateway options — DTC, SaaS, marketplaces, cross-border retail, utility billing and PSPs.

  • DTC

    DTC brand mixing card + wallet + BNPL

    One checkout surface exposes several options per market; the routing engine picks the highest-EV provider per authorisation.

  • SaaS

    SaaS billing on secure + recurring

    Recurring card on network tokens plus one-off card acceptance for setup fees. The vault token underpins both.

  • Plat

    Marketplace with per-seller option sets

    Some sellers accept card + wallet only; others add ACH or crypto. Each seller's option matrix is independently configurable.

  • Cross-border

    Cross-border retail across markets

    International options unlock per market with the same integration — EU, UK, APAC, LATAM without a per-region checkout project.

  • Utility

    Utility & telco billing on ACH + card

    ACH debits for recurring bills; card for one-off top-ups. Both route through the same reconciliation feed with per-customer statements.

  • PSP

    PSPs reselling the option matrix downstream

    Resellers inherit the full option catalogue and configure per-merchant option sets. The PSP keeps the merchant relationship; the platform handles the per-option message exchange.

Platform features

Capabilities shared across every gateway option

Twelve capabilities the platform ships once and reuses across every option — the primitives that make the option catalogue feel like one product.

  • Unified API across options

    One REST contract for card, ACH, wallet, ecommerce, international, crypto, recurring and high-risk options.

  • Hosted, embedded & SDK shapes

    Three integration shapes share the same back-end — picked per merchant's PCI and UI constraints.

  • Smart routing per option

    Per-option, per-BIN, per-currency and per-country routing across the connected provider panel.

  • Cascade & retry

    Soft declines cascade to the next ranked provider inside the same authorisation; nothing leaks back to the buyer.

  • PCI DSS Level 1 vault

    Card data captures into the platform vault before any provider sees it; PAN never lands in merchant systems.

  • Network tokens & updaters

    Network tokens (VTS, MDES) by default for card; scheme updaters keep saved credentials alive across re-issuance.

  • 3DS2 / SCA orchestration

    Selective EMV 3DS2 challenges per authorisation — PSD2-compliant in Europe without breaking conversion.

  • NACHA & SEPA mandate handling

    ACH and SEPA Direct Debit mandates captured and retained per scheme rules; mandate IDs travel with each recurring option.

  • Crypto via partner gateways

    Stablecoins, majors and L2 networks via licensed partner crypto gateways under the same API.

  • Unified dispute queue

    One queue across options; evidence-pack templates per vertical; automated representment for select scheme types.

  • Risk & fraud controls

    Velocity rules, list management and partner-agnostic fraud-engine connectors layered on top of routing.

  • One reconciliation feed

    Settlements, fees, refunds and chargebacks across every enabled option normalised into one ledger.

Trust & compliance

Compliance posture across every option

One audited environment underpins the orchestration layer; per-option scheme / rail-specific programmes surface in the dashboard so the merchant sees where they stand.

PCI DSS Level 1
Annual on-site assessment plus quarterly ASV scans; sub-merchants inherit the posture across every card option.
Scheme programmes
Visa VDMP / VAMP / VFMP and Mastercard ECP / EFMP positions surfaced per provider; routing weights can rotate around at-risk lanes.
SCA & PSD2
Selective 3DS2 on the authorisation path keeps approval high in Europe without skipping the SCA bar.
Bank-rail mandate posture
NACHA authorisations for ACH, SEPA mandate IDs for SEPA Direct Debit; captured and retained per scheme rules.
Crypto partner-gateway compliance
Crypto rails delivered through licensed partner gateways with VASP / MiCA-relevant authorisations; AML / KYC inherited.
Licensed verticals only
Licensed gaming, regulated financial services and other compliance-bound verticals supported only where current operating licences exist. Grey and black-market verticals are out of scope regardless of option shape.

Ready to pick your option mix

Turn on the payment gateway options your buyers want.

A 30-minute options review covers the acceptance shapes relevant to your traffic, the connected providers behind them, and a sandbox to test each option before any commercial commitment.

Book an options review Read the API docs

Frequently asked

Buyer questions about payment gateway options on topropay

Definitions, option-toggle mechanics, cost differences per option, and the practicalities of running many options through one platform.

  1. 01

    What are the payment gateway options on topropay?

    Payment gateway options on topropay are the acceptance shapes the unified gateway exposes: secure card, mobile (wallets and SoftPOS), ACH, ecommerce checkout (hosted / embedded / SDK), international rails, crypto, recurring and licensed high-risk. Each is a configuration of the same platform rather than a separate integration.

  2. 02

    What are the secure payment options for card acceptance?

    Secure payment options for card acceptance ride the PCI DSS Level 1 vault: card data captures into the platform vault, PAN never lands on the merchant origin, network tokens (VTS, MDES) replace static PANs for storage, and selective EMV 3DS2 fires per PSD2 exemption logic.

  3. 03

    How do mobile payment options work?

    Mobile payment options cover both card-not-present (Apple Pay, Google Pay, Click to Pay on the online checkout) and card-present (SoftPOS / Tap-to-Phone via licensed partner acquirer apps). Both surface on the same merchant record and reconcile into the same ledger.

  4. 04

    Which ach payment options are supported?

    ACH payment options supported include consumer ACH debits (WEB, TEL, PPD), business ACH debits (CCD), ACH credits for payouts, and same-day ACH where the underlying processor supports it. NACHA mandate evidence is captured at first debit; R-code-aware retries handle NSF / R01 / R03 / R04 returns per the merchant's configured policy.

  5. 05

    What ecommerce payment options make sense for a modern retailer?

    Ecommerce payment options for a modern retailer typically combine card (default), wallets (Apple Pay, Google Pay), BNPL (Klarna, Affirm, Clearpay), and one or two regional bank rails per market the retailer sells into. The hosted checkout renders the per-market method list; the SDK path is for retailers who want a fully bespoke checkout.

  6. 06

    How do international payment options work across markets?

    International payment options unlock per market from the dashboard. topropay's connected acquirer panel covers 40+ markets across EU, UK, APAC and LATAM; regional bank rails (SEPA, Bacs, PIX, iDEAL, Bancontact, Interac, PayID) sit alongside cards. The routing engine picks the optimal lane per BIN and country pair.

  7. 07

    Are crypto payment options fully supported?

    Crypto payment options on topropay are delivered through licensed partner crypto gateways rather than a topropay-owned crypto rail. Stablecoins (USDC, USDT, DAI), majors (BTC, ETH, SOL) and L2 networks are supported; optional conversion-on-receipt keeps the merchant's treasury fiat-only. The API surface is identical to fiat options.

  8. 08

    What recurring payment options does the platform expose?

    Recurring payment options include card-on-file with network tokens and scheme updaters, SEPA Direct Debit with mandate handling, recurring ACH with NACHA mandates, and PIX-Recorrência where supported. Smart retries schedule around soft declines; recovery emails are templated per merchant.

  9. 09

    Are high risk payment gateway options available on this platform?

    High risk payment gateway options are available for licensed high-risk verticals — subscriptions, travel, ticketing, licensed gaming, nutraceuticals and similar. Chargeback-aware routing across the connected panel is the key differentiator: authorisations rotate around acquirers whose scheme-programme position is at risk (VDMP / VAMP / ECP).

  10. 10

    Can a merchant enable specific payment gateway options for website checkout only?

    Yes. Payment gateway options for website checkout can be enabled independently of in-person or API-only options. The hosted checkout, embedded hosted-fields and SDK surfaces are all website-facing; the SoftPOS and terminal options serve card-present, invoice pay links serve receivables — each independently switchable.

  11. 11

    How does the platform decide which option to surface for a given buyer?

    The buyer surface is merchant-configured: the merchant chooses which options appear on their checkout for each market, currency and vertical. The platform's role is to render the configured list, capture the buyer's choice, and route the authorisation to the optimal provider for that option. There isn't algorithmic option-selection on the buyer surface — the merchant owns that curation.

  12. 12

    Can options be turned off without affecting other options?

    Yes. Options are toggles on the merchant's dashboard; toggling one off doesn't affect the others. In-flight authorisations under the disabled option complete normally; new authorisations under it are blocked. Reconciliation continues to surface historical activity per option.

  13. 13

    How long does it take to enable an additional option?

    For most options — new mobile wallet, additional currency, additional regional rail — enablement is a dashboard action that takes effect the same day. Options requiring new acquirer relationships (a new licensed acquirer partner in a new market) run on the partner's onboarding timeline, typically 2–4 weeks.

  14. 14

    Do option-specific fees differ?

    Yes. Different options carry different underlying costs — card interchange, scheme fees, ACH per-transaction, crypto network gas — so pricing is per-option rather than a flat blended rate. The platform surfaces per-option effective cost in the reconciliation feed so finance can compare landed cost across options.

  15. 15

    Is topropay a payment gateway, or an aggregator over gateway options?

    topropay is the aggregator / orchestration layer that sits one level above traditional single-provider gateways. The 'payment gateway options' framing describes the acceptance shapes the platform exposes; the underlying acquiring relationships sit with licensed partner acquirers in each region. The merchant sees one API and one contract.

Related

Related on the topropay platform