Fiat + crypto on one contract
Cards, wallets and bank rails alongside stablecoins and major tokens through licensed partner crypto gateways. Optional conversion-on-receipt keeps treasury fiat-only where accounting requires it; one reconciliation feed across every rail.
Key benefits
Four properties that show up the moment fiat and crypto stop being two separate checkouts and start being two rails on the same integration.
Card, wallet, bank-rail and crypto endpoints share the same REST contract. The merchant integrates once; the buyer picks fiat or crypto at checkout; the platform handles the per-rail message exchange behind the scenes.
Crypto acceptance runs through licensed partner crypto gateways with VASP / MiCA-relevant authorisations. AML / KYC posture is inherited; the merchant doesn't operate a wallet or run their own crypto compliance stack.
The merchant can settle in fiat regardless of what the buyer paid with. Received crypto converts to the merchant's chosen fiat currency at the partner-gateway's live rate; the merchant's treasury sees a clean fiat balance.
Crypto and fiat receipts normalise into the same daily ledger, each row tagged with rail, currency, provider and conversion rate. Finance reads one feed instead of stitching CSVs across worlds.
How the payment gateway for crypto side works
The chain of events between the buyer picking crypto at checkout and the merchant's finance team reading a settled row in the unified ledger.
The hosted checkout surfaces card, wallet, bank rail and crypto side-by-side. The buyer picks; the choice determines which downstream provider carries the authorisation.
For crypto flows, the partner-gateway issues a live-quote for the invoice amount in the buyer's chosen token; a QR code or wallet-connect handoff completes the send.
The partner-gateway watches the chain for confirmations at the merchant-configured depth (usually 1–3 blocks for most tokens; higher for BTC on-chain deposits).
If conversion-on-receipt is enabled, the partner-gateway converts the confirmed crypto amount into the merchant's chosen fiat currency at the live rate; conversion rate is recorded on the transaction.
Fiat settlement lands per the partner-gateway's schedule (typically T+1 to T+3 for most rails). The reconciliation feed carries every crypto and fiat row into the same ledger for finance.
Main use cases
Six recurring merchant shapes that combine fiat and crypto acceptance — DTC, SaaS, B2B, exchange on-ramps, Web3 apps and PSPs reselling downstream.
DTC brands that want a crypto-native segment plug the gateway crypto surface into the same checkout as card and wallet. No separate integration for crypto; no wallet operations.
SaaS merchants that bill customers in USDC / USDT alongside card-on-file subscribers; conversion-on-receipt keeps the merchant's revenue recognition in fiat where accounting requires it.
B2B counterparties that prefer stablecoins for cross-border payments avoid FX spreads and correspondent-bank delays. The gateway crypto surface handles receiving; conversion or hold-in-crypto is per-merchant policy.
Crypto exchanges accepting fiat pay-ins (card, ACH, SEPA, wallets) for on-ramp deposits ride the same platform their pay-outs / off-ramps sit behind. Licensed jurisdictions only.
Web3 apps with fiat-side users use the same checkout to accept card / wallet / bank rail for buyers who don't want to touch crypto directly, and native token flows for buyers who do.
PSPs and resellers inherit the fiat + crypto contract and offer it downstream to their merchant portfolio. The PSP keeps the merchant relationship; the platform handles the per-rail exchange.
Platform features
Twelve capabilities grouped into crypto rails, fiat + orchestration and operator & finance. Each applies whether the merchant leans crypto-heavy or fiat-heavy.
USDC, USDT, DAI, PYUSD on major networks; per-token acceptance toggles per merchant.
BTC, ETH, SOL plus Polygon, Base, Arbitrum and other supported L2 networks.
In-page wallet-connect for browser wallets; QR handoff for mobile wallets; live-quote per invoice.
Merchant-configurable block-confirmation depth per token; live-quote refresh window per rate move.
Visa, Mastercard, Amex, Apple Pay, Google Pay, SEPA SDD, ACH and regional rails alongside crypto.
One REST contract for authorise, capture, refund, dispute — same shape whether the rail is fiat or crypto.
Card data captures into the platform vault before any acquirer sees it; PAN never lands in merchant systems.
Card authorisations cascade across connected acquirers on soft decline; crypto flows go direct to the partner-gateway.
Optional live-rate conversion of received crypto to the merchant's chosen fiat currency at the partner-gateway.
Merchants that prefer to hold received crypto can bypass conversion; settlement lands in-token on a merchant-controlled wallet.
Crypto and fiat receipts, fees, refunds and conversion rates in one normalised ledger; daily exports.
Operator-side refund controls create a new on-chain transaction to the original sender address (or the last-known refund address held by the merchant).
Industry relevance
topropay's fiat + crypto posture targets licensed merchants operating across Europe, the UK, APAC and LATAM — DTC brands adding a crypto-native segment, SaaS merchants billing in stablecoins alongside cards, B2B counterparties settling in stablecoins, licensed crypto-exchange on-ramps, and Web3 apps that need a fiat pay-in surface alongside their native token flows.
Trust & compliance
One audited environment underpins the fiat side; licensed partner-gateways carry the crypto side. Sub-merchants inherit the relevant posture per rail rather than carrying separate certifications themselves.
Ready to add crypto without a project
A 30-minute coverage review covers the tokens relevant to your buyers, the licensed partner-gateway available in your geographies, conversion-on-receipt vs hold-in-crypto, and a sandbox to test against before any commercial commitment.
Frequently asked
Definitions, on-chain mechanics, conversion-on-receipt, jurisdiction coverage, wallet compatibility and how disputes work when the payment cleared on chain.
Gateway crypto on topropay is the crypto-side surface of the unified acceptance API — the merchant integrates one contract and gets fiat card / wallet / bank rail acceptance and licensed partner crypto acceptance under the same authorise, capture, refund and dispute endpoints. Crypto flows ride licensed partner crypto gateways; the merchant doesn't run wallet operations or independent crypto compliance.
A crypto-only payment gateway crypto product handles only crypto rails and expects the merchant to bring their own fiat acceptance separately. topropay's model integrates both: fiat and crypto share the vault, the reconciliation feed and the dispute queue, so the merchant reads one ledger instead of two, and finance sees crypto receipts alongside fiat receipts row-for-row.
Yes. The payment gateway for crypto side supports major stablecoins (USDC, USDT, DAI, PYUSD) across their common networks, plus BTC, ETH, SOL and L2 networks (Polygon, Base, Arbitrum). Per-token acceptance is a merchant toggle in the dashboard; new tokens are added as the licensed partner-gateways add support.
The merchant's checkout acts as the gateway to crypto for buyers who prefer to pay with tokens they hold. The merchant doesn't hold buyer funds or operate a wallet — the partner-gateway carries the on-chain leg, confirms the transaction, and hands settlement (or converted fiat) back to the merchant. Legal and compliance responsibility for buyer funds sits with the licensed partner-gateway, not the merchant.
Yes, for licensed exchange operators. A payment gateway for crypto exchange on-ramp accepts fiat pay-ins (card, ACH, SEPA, wallets) that fund a user's exchange account balance; topropay's fiat rails cover the pay-in side, and the exchange's own systems handle the on-chain credit. Only exchanges with the relevant operating licences in the merchant's target geographies are in scope.
Yes. A payment gateway with crypto and fiat side-by-side is the default hosted-checkout shape: cards, wallets, bank rails and enabled crypto methods appear on the same page; the buyer picks; the platform routes the choice to the appropriate downstream provider. The merchant's UI doesn't fork per rail.
When conversion-on-receipt is enabled, the partner crypto-gateway converts the confirmed crypto amount into the merchant's chosen fiat currency at the live rate available at confirmation. The rate, timestamp and quoting partner-gateway are recorded on the transaction and visible per row in the reconciliation feed. Merchants who prefer to hold crypto can bypass conversion and settle in-token to a merchant-controlled wallet.
The partner-gateway issues a live-quote at the moment the buyer initiates the payment; the quote is valid for a short window (typically 5–15 minutes depending on token volatility). If the buyer's on-chain transaction confirms within the window, the quoted amount holds. If it expires, the invoice re-quotes and the buyer confirms the new amount before completing.
On-chain refunds create a new outbound transaction from the partner-gateway to the original sender address (or the last-known refund address held by the merchant). Operator-side controls require a reason code on every refund; the on-chain transaction hash is recorded in the ledger against the original invoice. Card-side refunds continue to run against the vault token as usual.
On-chain confirmations happen in minutes-to-hours depending on the token; fiat settlement (after conversion-on-receipt) follows the partner-gateway's schedule, typically T+1 to T+3 for most rails. Merchants holding in-token settle to the merchant-controlled wallet as soon as the partner-gateway has confirmed the receipt at the merchant's configured confirmation depth.
Fiat + crypto acceptance together is available in jurisdictions where the licensed partner-gateways hold the relevant VASP / MiCA / equivalent authorisations. Coverage spans much of the EU, UK and select APAC and LATAM markets; a 30-minute coverage review confirms availability in the merchant's specific target geographies before any commitment.
Buyers need whatever wallet they normally use to hold the token they're paying with — MetaMask, Coinbase Wallet, Trust Wallet, Ledger, Rainbow, mobile wallets on the buyer's network of choice, etc. The checkout supports wallet-connect for browser wallets and QR handoff for mobile wallets. No new-wallet download required.
The licensed-verticals-only posture applies to both fiat and crypto rails. Adult content, unlicensed gambling and grey / black market activity are out of scope regardless of whether the buyer pays in fiat or in crypto. Licensed gaming, regulated financial services and other compliance-bound verticals are in scope where the operator holds the relevant licences.
On-chain crypto transactions don't have unilateral chargebacks the way card transactions do — once confirmed, they're final. Disputes on the crypto side are handled through the merchant's own resolution process (refund on-chain, credit note, etc.). The fiat side continues to use the unified dispute queue with scheme-programme timelines for card chargebacks.
From contract to first crypto acceptance is typically 2–4 weeks: KYB through topropay, activation with the licensed partner-gateway for the merchant's target tokens, sandbox testing, then live traffic. Merchants who already have the fiat side of topropay live can typically add crypto in a matter of days as a dashboard-side enable.
Related