Crypto currency payment gateway

Crypto currency payment gateway — crypto + multi-currency fiat on one API.

topropay surfaces crypto rails through licensed partner crypto gateways inside the same unified API as multi-currency fiat. Stablecoins, majors and L2 networks plug in alongside EUR, GBP, USD and regional currencies. Optional conversion-on-receipt keeps treasury fiat-only when the merchant prefers.

Book a crypto review Read the API docs
topropay routing · vault USDC USDT BTC ETH EUR GBP USD BRL AUD JPY CRYPTO RING · partner gateways FIAT RING · multi-currency settlement
Crypto + multi-currency fiat · one orchestration hub.
Crypto + fiat
on one unified API
Stablecoins
USDC · USDT · DAI · PYUSD
Multi-currency
settlement per market
1 ledger
across every connected provider

Key benefits

Why orchestrated multi currency payment gateway wins on crypto + fiat

Four outcomes that show up consistently once crypto rails sit alongside multi- currency fiat on the same orchestration layer instead of in a separate console.

  1. 01

    Crypto currency payment gateway behaviour alongside fiat

    topropay surfaces crypto rails — stablecoins, majors and L2 networks via licensed partner crypto gateways — inside the same unified API as cards, wallets and bank rails. From the merchant's code it's one /v1/payments endpoint with a method field. From the buyer's side it's a Pay-With-Wallet tile next to the card form.

  2. 02

    Multi currency payment processing — crypto and fiat together

    Multi currency payment processing on the platform handles both: fiat in 40+ regional currencies through the connected acquirer panel, plus crypto rails through partner gateways. Settlement currency per acquirer is a policy choice; conversion-on-receipt converts incoming crypto to fiat at the rail's quote.

  3. 03

    Optional conversion-on-receipt for treasury simplicity

    For merchants who don't want to hold crypto on the balance sheet, conversion-on-receipt policies convert incoming stablecoins or majors to fiat at the connected gateway's quote. The fiat amount surfaces in the same ledger as card receipts. The treasury team never carries unsolicited crypto exposure.

  4. 04

    One reconciliation feed across crypto and fiat

    Settlements, conversion fees, refunds and chargebacks across every connected provider — crypto and fiat — normalise into one ledger keyed off vault tokens (cards) and on-chain references (crypto). Finance closes the month from one export. The ledger tags every row with the rail, provider and routing policy.

How it works

From a Pay-With-Wallet click to a normalised ledger entry in five stages

Five concrete stages between the buyer picking a wallet and a normalised ledger row in tomorrow's finance export — most measured in seconds.

  1. 01

    Surface the wallet option at checkout

    The checkout reads the shopper's market and surfaces Pay-With-Wallet inline with cards. Stablecoins and majors light up per market based on the partner gateway's regional coverage.

  2. 02

    Quote and lock the rate

    When the buyer picks crypto, the connected partner gateway quotes the equivalent in the chosen asset and locks the rate for the authorisation window. The merchant sees the fiat equivalent throughout the flow.

  3. 03

    Buyer signs from their wallet

    QR-scan or in-wallet tap; the buyer signs the on-chain transaction. The connected gateway watches the chain and confirms when the required block-depth is reached.

  4. 04

    Convert on receipt — or hold the asset

    If conversion-on-receipt is on, the connected gateway converts the received crypto to the merchant's settlement currency. If conversion is off, the asset lands in the merchant's connected wallet at the rail's normal confirmation depth.

  5. 05

    Reconcile alongside fiat

    The authorisation, settlement and any conversion fee appear in the same normalised ledger as card receipts — same daily export, same accounting integration. No separate crypto-ledger reconciliation needed.

Main use cases

Where digital currency payment gateway flows earn their keep

Six merchant shapes that benefit from a crypto rail alongside fiat — DTC, SaaS, marketplaces, B2B, travel and multi-FX.

  • DTC

    DTC merchants serving crypto-native buyers

    Surface a Pay-With-Wallet option alongside cards on the same checkout. Conversion-on-receipt keeps the merchant fiat-only on the balance sheet; the crypto rail just changes who can pay.

  • Subs

    Subscriptions denominated in stablecoin

    Stablecoin-denominated subscriptions on wallets that support recurring authorisations, or pre-funded merchant wallets that debit on a schedule. Renewal lifecycle runs through the same orchestration engine as card recurring.

  • Plat

    Marketplaces with cross-border sellers

    Sellers in jurisdictions where USDC is a more stable unit of account than the local currency can receive payouts in stablecoin via the same orchestration; per-seller reporting rolls up alongside fiat payouts.

  • B2B

    Cross-border B2B invoicing

    Invoices to overseas counterparties paid in stablecoin clear faster than wire instructions and skip correspondent-bank fees. The invoice and the on-chain receipt share one record in the reconciliation feed.

  • Travel

    High-ticket travel and ticketing

    High-ticket orders see disproportionate FX and interchange cost on cards — a stablecoin lane absorbs that for buyers who want it, without forcing card buyers off cards.

  • Multi-FX

    Multi-currency fiat merchants adding a crypto rail

    Multi currency payment gateway customers running EUR / GBP / USD / BRL on the fiat side typically add the crypto rail as 'one more currency' — same API, same dashboard, same reconciliation, just a different settlement timing.

Platform features

Capabilities behind the digital currency payment system on the platform

What the platform actually ships for crypto rails — beyond the high-level claim, the primitives that make the orchestration stand up alongside fiat.

  • Licensed partner crypto gateways

    Crypto rails delivered through licensed partner gateways with relevant VASP / MiCA-relevant authorisations.

  • Unified crypto + fiat API

    Same /v1/payments endpoint for card, wallet, bank rail and crypto authorisations; same webhook event model.

  • Hosted Pay-With-Wallet surface

    Drop-in wallet pay-sheet that surfaces inline with cards on the same hosted checkout.

  • QR / in-store flow

    Same authorisation surface for in-store QR flows; the till generates the QR, takes the signed transaction, finalises the order.

  • Conversion-on-receipt

    Per-asset, per-merchant conversion policy converts received crypto to settlement currency at the rail's quote.

  • Multi-currency settlement

    Settle in EUR, GBP, USD, BRL, AUD and other supported currencies per acquirer relationship — including crypto-to-fiat conversion.

  • On-chain reference retention

    Every crypto authorisation tags the on-chain transaction hash and block height for audit and counter-party reconciliation.

  • Address screening

    Connected partner gateways run on-chain address screening against sanctions lists; flagged authorisations are rejected at the gateway.

  • Travel-rule support

    Where the connected partner gateway supports the FATF Travel Rule on the rail, the metadata is captured and surfaced in the reconciliation feed.

  • Per-asset routing policies

    Route by asset class — stablecoins on a low-fee L2, BTC on Lightning, ETH on the main chain — from the dashboard.

  • Operator portal

    One dashboard for crypto and fiat: authorisations, refunds and reconciliation across every connected rail.

  • Sandbox parity

    Sandbox crypto flows mirror production, including chain confirmations and conversion behaviour.

Trust & compliance

Compliance posture for crypto currency payment services

Crypto rails carry their own regulatory shape. topropay's posture is to ride partner-licensed gateways with the relevant authorisations and inherit the associated AML / KYC controls on the merchant's behalf.

Partner-licensed crypto rails
Crypto rails delivered through licensed partner gateways with their own VASP / MiCA-relevant authorisations in the regions they cover.
AML / KYC inheritance
Sub-merchants on the platform inherit the partner-gateway AML/KYC posture; merchant-level KYB happens once during topropay onboarding.
Address screening
Connected partner gateways run on-chain address screening against OFAC / EU / UN sanctions lists; flagged authorisations are rejected at source.
Travel rule support
Where the connected rail and counterparty wallet support the FATF Travel Rule (TRP / IVMS101 payload), the metadata flows through.
PCI / fiat posture preserved
Adding crypto rails does not affect the platform's PCI DSS Level 1 posture for the card side; the two domains stay separately attested.
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 rail.

Ready to add a crypto rail

Add a crypto currency rail to a multi-currency stack.

A 30-minute crypto review covers the partner-gateway panel for your buyer base, the conversion-on-receipt policy that fits treasury, and a sandbox to test against before any commercial commitment.

Book a crypto review Read the API docs

Frequently asked

Buyer questions about a crypto currency payment gateway alongside fiat

Questions buyers ask before committing — supported tokens, conversion behaviour, refunds, chargebacks, multi-currency fiat coverage and the regulatory shape.

  1. 01

    How does topropay support a crypto currency payment gateway model?

    topropay surfaces crypto rails through licensed partner crypto gateways that plug into the unified payments API. The merchant integrates against one REST surface; the partner gateway handles the on-chain side; topropay routes, abstracts, reconciles and reports. From the merchant's perspective it's a crypto currency payment gateway behind the same integration shape as card.

  2. 02

    What does crypto currency payment mean in practice on the platform?

    Crypto currency payment on the platform means the buyer pays in a supported on-chain asset (USDC, USDT, BTC, ETH, etc.) via the connected partner gateway. The merchant sees the fiat-equivalent amount throughout the flow; conversion-on-receipt converts to the merchant's settlement currency on credit, if the merchant prefers fiat.

  3. 03

    Is topropay a multi currency payment gateway for fiat too?

    Yes. multi currency payment gateway behaviour is part of the platform — settlement currency per acquirer relationship is a policy choice (EUR, GBP, USD, BRL, AUD and others), and authorisations can capture in the buyer's currency with settlement in the merchant's. Crypto rails sit alongside that fiat handling rather than as a separate system.

  4. 04

    How does multi currency payment processing handle both fiat and crypto?

    Multi currency payment processing on topropay runs both through the same routing, vault and reconciliation engine. Fiat authorisations route through the connected acquirer panel; crypto authorisations route through the connected partner crypto gateways. The reconciliation feed normalises both into one ledger with rail / currency / provider tags per row.

  5. 05

    What does the crypto currency payment services category cover?

    Crypto currency payment services on the platform cover the full lifecycle: hosted wallet checkout, in-store QR flow, conversion-on-receipt, address screening, on-chain reference retention, partner-gateway-side AML/KYC and unified reconciliation alongside fiat. It's not a separate product — it's a configuration of the unified API.

  6. 06

    How does a merchant accept crypto currency as payment through the platform?

    Merchants accept crypto currency as payment by enabling the crypto methods on their dashboard. The hosted checkout surfaces Pay-With-Wallet inline with cards; the merchant's authorise call uses 'method: crypto' (or the specific asset). The connected gateway quotes, watches the chain, confirms — and topropay fires a normalised webhook just as it would for card.

  7. 07

    Is the digital currency payment gateway framing the same as crypto?

    The digital currency payment gateway framing in industry usage typically covers stablecoins and major cryptocurrencies — the same scope topropay covers via partner gateways. Where 'digital currency' is used in a narrower CBDC (central-bank digital currency) sense, the platform tracks rollouts but doesn't currently route to specific national CBDC pilots.

  8. 08

    What does a digital currency payment system look like operationally?

    Operationally a digital currency payment system on topropay is: connected partner gateway on the chain side, topropay's routing / vault / reconciliation engine in the middle, merchant API and dashboard on the front. Reads as one product; the partner gateway side is transparent to the merchant.

  9. 09

    What chains and tokens does the partner-gateway panel support?

    Supported tokens include USDC, USDT, DAI, PYUSD, USDP (stablecoins); BTC, ETH, SOL, MATIC, BNB (majors); L2 networks like Base, Arbitrum, Optimism, Polygon and zkSync; settlement rails like Lightning (BTC), Tron (USDT), Solana (USDC) and Stellar. Availability per merchant depends on jurisdiction and the partner gateway's coverage; the dashboard shows the live state.

  10. 10

    How does conversion-on-receipt affect the merchant's books?

    Conversion-on-receipt converts the received crypto to the merchant's settlement currency at the connected gateway's quote, so the merchant's books only ever see fiat. The reconciliation row carries the original crypto amount, the conversion rate and the resulting fiat amount — useful for audit but transparent for accounting.

  11. 11

    What about refund flows on a crypto currency payment?

    Refund flows on a crypto currency payment are merchant-initiated through the same /v1/payments/:id/refund endpoint as card. The connected partner gateway initiates a return on-chain to the originating wallet, on the same rail as the original; partial refunds are supported. Refund operations log the operator identity and the on-chain reference for audit.

  12. 12

    Are chargebacks possible on crypto authorisations?

    Confirmed on-chain transactions don't carry the card-style chargeback window — once settled, they're settled. Refunds are merchant-initiated; unilateral chargebacks don't exist on the rail. That's operationally a different dispute calendar, but on net it removes a class of revenue leakage entirely.

  13. 13

    Can the platform handle multi currency payment gateway flows for emerging markets?

    Yes. Multi currency payment gateway flows for emerging markets are handled by combining regional acquirer connectivity (LATAM, APAC, Africa where supported) with stablecoin rails via partner gateways. Merchants accept in local fiat where the local acquirer covers it and stablecoin where the connected partner gateway covers it.

  14. 14

    How does topropay price crypto currency payment services?

    Crypto currency payment services on topropay are priced per-authorisation on top of the underlying partner gateway's economics. The partner gateway's per-transaction fee and any conversion spread pass through transparently on the invoice; topropay's platform fee is a separate line. No platform retainer, no monthly minimum.

  15. 15

    How does the platform stay current with the regulatory shape of crypto payments?

    Crypto regulation moves fast — MiCA in the EU, the FCA's regime in the UK, MAS in Singapore, and so on. topropay tracks the regulatory shape through the connected partner gateways' authorisations and through its own compliance review. Where a regulatory change requires a method or jurisdiction to come off the panel, merchants are notified and routing adjusts accordingly.

Related

Related on the topropay platform