Crypto payments

Crypto payments, accepted through the same API as cards.

topropay brings crypto rails — stablecoins, majors and L2 networks, via connected partner gateways — into the same unified API as cards, wallets and bank rails. Accept crypto on your website or in store. Convert on receipt or hold the asset. Reconcile it all in one ledger.

Book a crypto review Explore the platform
USDC USDT BTC ETH topropay convert · route on receipt LEDGER €189.00
Many tokens in. One ledger entry out.
200+
supported tokens via partner crypto gateways
<1m
typical confirmation for stablecoins on L2s
1
ledger across crypto and fiat methods

Key benefits

Why merchants are accepting crypto payments alongside cards

Five reasons that show up most consistently in conversations with merchants who turn a crypto rail on after running card-only for years.

  1. Borderless settlement, predictable cost

    Crypto rails — stablecoins above all — skip cross-border interchange and FX spreads. For cross-border buyers, that means a flat cost per transaction, not one that swings with the card issuer.

  2. Finality without representment cycles

    A confirmed on-chain transaction has no chargeback window. You can still refund a buyer, but they cannot open a dispute on their own. That is a different reconciliation calendar to plan for, not a worse one.

  3. New buyer segments without a new checkout

    Crypto-native buyers expect a Pay-With-Wallet option at checkout. Add one next to card and BNPL and you reach them — with no second checkout and no second back office.

  4. Optional conversion-on-receipt for treasury sanity

    Would rather not hold crypto on the balance sheet? Conversion-on-receipt turns incoming stablecoins or majors into fiat at the rail's quote. The fiat amount lands in the same ledger as your card receipts.

  5. Same unified API, same reconciliation feed

    Crypto authorisations run through the same unified API as card and wallet ones. Operators see the same dashboard. Finance gets the same export. The rail is new; the workflow is not.

How it works

From buyer-side QR scan to a normalised reconciliation entry

Five stages between the buyer picking a wallet and a normalised ledger row showing up in tomorrow's finance export.

  1. Surface the right wallet option at checkout

    The checkout reads the shopper's market, device class and currency and orders the method list — including the Pay-With-Wallet option for crypto-native buyers in regions where it converts.

  2. Lock the price for the authorisation window

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

  3. Buyer signs from their wallet

    The buyer scans the QR (in-store or web) or taps Pay (in-wallet) and signs the transaction. The connected gateway watches the chain and confirms when the required block depth is reached.

  4. Optional conversion-on-receipt to fiat

    If conversion-on-receipt is on, the gateway converts the received crypto to the merchant's settlement currency at the locked rate. If conversion is off, the asset lands in the merchant's connected wallet as-is.

  5. One ledger row, like every other method

    The platform surfaces the authorisation, settlement and any conversion fee in the same normalised ledger as card receipts — same export, same accounting integration.

Main use cases

Where accept crypto payments online and in store earns its keep

Six merchant shapes that benefit from a crypto rail, with the operational shape that fits each.

  • E-commerce — accepting payments on website

    Online retailers add a Pay-With-Wallet button at checkout next to cards and wallets. Conversion-on-receipt keeps the merchant fiat-only on the balance sheet; the crypto rail just changes who can pay.

  • Subscriptions and recurring billing

    Stablecoin-denominated subscriptions on wallets that support recurring authorisations (or pre-funded merchant wallets that debit on a schedule). Vault tokens track the customer; renewal lives inside the same orchestration as card retries.

  • Marketplaces and platforms

    Sellers in jurisdictions where USDC is a more stable unit of account than the local currency receive payouts in stablecoin via the same orchestration; the platform reconciles per-seller in the same ledger as fiat payouts.

  • Travel, ticketing and high-ticket

    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.

  • 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.

  • In-store and quick-service

    An accept crypto payments in store flow is a QR on the till plus a wallet-side confirmation. The terminal hands off to the connected gateway; settlement and reporting are identical to web flow.

Supported rails

Tokens, chains and settlement rails accessible through partner crypto gateways

A sample of what the connected partner crypto gateways expose. Availability per merchant depends on the merchant's vertical and jurisdiction; the dashboard shows the live state.

  • Stablecoins

    • USDC
    • USDT
    • DAI
    • PYUSD
    • USDP

  • Majors

    • BTC
    • ETH
    • SOL
    • MATIC
    • BNB

  • L2 networks

    • Base
    • Arbitrum
    • Optimism
    • Polygon
    • zkSync

  • Settlement rails

    • Lightning (BTC)
    • Tron (USDT)
    • Solana (USDC)
    • Stellar

Model comparison

Single crypto PSP vs orchestration across crypto and fiat

What changes when crypto rails are run as a category alongside cards, instead of as a separate console with its own integration.

Dimension Single crypto PSP topropay orchestration
Model Crypto-only PSP — one provider, one set of supported assets, separate console Crypto rails sitting inside the same unified API as cards, wallets and bank rails — one console
Method coverage Crypto only Crypto + cards + wallets + bank rails + BNPL behind one integration
Conversion Manual treasury work or limited auto-convert Conversion-on-receipt as a policy per asset per merchant
Reconciliation Separate crypto ledger from your card processor's ledger Crypto and fiat normalised into one reconciliation export
Compliance Per-provider AML/KYC posture; merchant carries it AML/KYC inherited from the connected partner gateways and the platform's own posture
Onboarding Separate underwriting at the crypto PSP Single onboarding through topropay's sub-merchant model for licensed verticals

Platform features

Capabilities behind the accept crypto payments API surface

What the platform actually ships for crypto rails — beyond the general orchestration features shared with mainstream merchants.

Connected partner gateways
Crypto rails delivered through licensed partner crypto gateways; topropay routes, abstracts and reconciles.
Unified payments API
Crypto authorisations call the same REST contract as cards; one webhook stream, one event model.
Hosted Pay-With-Wallet
A drop-in pay sheet that surfaces wallet options inline with card and BNPL at the same checkout.
QR / in-store flow
Same authorisation surface for in-store quick-service flows — generate a QR, take the signed transaction, finalise the order.
Conversion-on-receipt
Per-asset conversion policy converts received crypto to settlement currency at the rail's quote.
Tokenised customer record
Vault tokens identify the customer across rails; refunds, partial refunds and renewals share one customer view.
Webhooks & event stream
Signed, normalised webhooks for authorised / confirmed / settled / refunded events into your SIEM or warehouse.
Per-asset routing policies
Route by asset class — e.g. 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 that mirror production, including chain confirmations and conversion behaviour.

Trust & compliance

Compliance posture for accepting crypto payments as a business

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 are 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.

  • Travel rule support

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

  • Address screening

    Connected gateways run on-chain address screening against sanctions lists; flagged authorisations are rejected at the gateway, not in the merchant's surface.

  • PCI / fiat posture preserved

    Adding crypto rails does not affect the platform's PCI DSS Level 1 posture for the fiat side.

  • 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 accept

Add a crypto rail to your checkout — or to your in-store flow.

A 30-minute crypto review covers the rails that fit your buyer base and jurisdiction. We pick the right conversion policy for your treasury. Then you get a sandbox to test in — before any commercial commitment.

Book a crypto review Read the API docs

Frequently asked

Buyer questions about accepting crypto payments through topropay

Questions buyers ask before committing — covering definitions, the API surface, on-website and in-store flows, and the compliance posture behind partner crypto gateways.

  1. 01

    How does topropay support crypto payments — directly or via partners?

    Crypto rails are delivered through licensed partner crypto gateways that plug into topropay's unified payments API. topropay routes the authorisation, abstracts the gateway surface and reconciles the settlement into the same ledger as fiat. The merchant integrates against one API regardless of whether the underlying rail is a card processor or a crypto gateway.

  2. 02

    What does accepting crypto payments look like from a merchant integration perspective?

    Accepting crypto payments looks like adding a method to the unified API — same authorisation call, same webhook event model, same vault-token-based refund flow. The hosted checkout surfaces a Pay-With-Wallet option alongside cards; the SDK exposes the same primitives for embedded surfaces.

  3. 03

    Is there a difference between accepting payments in crypto and accepting fiat-equivalent payments?

    Accepting payments in crypto carries the on-chain confirmation calendar, optional conversion-on-receipt and no chargeback window. Accepting fiat-equivalent payments via conversion-on-receipt means the merchant's books only ever see fiat — the crypto leg is settled to fiat before it reaches the merchant's wallet.

  4. 04

    What's the typical posture for accepting crypto payments for business at scale?

    Accepting crypto payments for business at scale usually means stablecoins on a low-fee L2, with conversion-on-receipt to the merchant's settlement currency. That gives the merchant a crypto-accepting checkout without the treasury complexity of holding volatile assets.

  5. 05

    Can I accept crypto payments for business without holding any crypto?

    Yes — accept crypto payments for business in fiat-only mode by turning conversion-on-receipt on for every supported asset. Incoming USDC, USDT, BTC and ETH all settle to the merchant's chosen fiat currency at the rail's quote; the merchant's balance sheet never carries crypto.

  6. 06

    How do I accept crypto payments on website specifically?

    Accept crypto payments on website by enabling the wallet option in the hosted checkout, or by embedding the same authorisation flow via the SDK. The buyer chooses Pay-With-Wallet, scans a QR or taps Pay in their wallet, and the on-chain confirmation triggers a normal authorised event in your back-end.

  7. 07

    What kinds of crypto payments for business does the platform handle?

    Crypto payments for business categories supported include one-off e-commerce checkouts, subscriptions on supported wallets, marketplace payouts in stablecoin, B2B invoicing, and in-store QR flows. Per-asset and per-rail policies (stablecoin vs major, mainnet vs L2 vs Lightning) are dashboard-configurable.

  8. 08

    How does accepting payments on website with crypto interact with our existing card flow?

    Accepting payments on website with crypto runs through the same hosted checkout as card; the buyer sees a Pay-With-Wallet button next to the card form. The two flows share vault tokens for customer identity and settle into the same reconciliation feed, so finance closes the month from one export.

  9. 09

    Which crypto payments companies does topropay compare to?

    Crypto payments companies typically fall into two camps: direct gateway providers (BitPay, Coinbase Commerce, NOWPayments and similar) and orchestration layers. topropay is the latter — it integrates with multiple crypto gateways and routes between them, similar to how we orchestrate card acquirers. The merchant gets multi-provider depth without having to manage multiple integrations.

  10. 10

    What is the cleanest path to accept crypto payments online with a global buyer base?

    Accept crypto payments online with a global buyer base by enabling stablecoins on the L2 networks the buyer base uses (USDC on Base or Solana, USDT on Tron) and one or two majors (BTC on Lightning, ETH on mainnet). Conversion-on-receipt keeps treasury simple; per-asset routing keeps fees low.

  11. 11

    Can I just receive payments in crypto without converting?

    Yes — receive payments in crypto without converting by turning conversion-on-receipt off for the assets you want to hold. The asset lands in the merchant's connected wallet at the rail's normal confirmation depth; the merchant's treasury team handles any subsequent conversion or hold posture.

  12. 12

    Is there a dedicated accept crypto payments API or is it the same API as cards?

    Same API. There is no separate accept crypto payments API to integrate against — the unified payments API exposes crypto as a method and the integration shape is identical to enabling, say, BNPL. SDK helpers cover wallet-deeplink generation, QR rendering and chain-confirmation events for in-app surfaces.

  13. 13

    What about accept crypto payments in store for physical retail?

    Accept crypto payments in store with the same authorisation engine. The till generates a QR for the buyer's wallet; the connected gateway watches the chain; the platform issues an authorised event to the till when the required confirmation depth is reached. Same surface as web flow, just a different entry point.

  14. 14

    What does crypto merchant payments add over a single crypto PSP?

    Crypto merchant payments through topropay add multi-gateway routing, unified reconciliation across crypto and fiat, conversion-on-receipt policies as a per-asset configuration, and the operational shape of the rest of the platform (vault tokens, signed webhooks, one operator portal). A single crypto PSP gives the rails; the orchestration layer turns them into a managed accept-crypto product.

  15. 15

    Is accepting crypto payments as a business legally straightforward in our markets?

    Accepting crypto payments as a business depends on the merchant's jurisdiction and vertical. In EU/UK markets MiCA-relevant authorisations on the partner gateways cover most flows; in the US and APAC the picture is more state- or country-specific. topropay's compliance team flags the relevant constraints during onboarding so the merchant doesn't go live on a rail that's not legally clean for their setup.

Related

Related on the topropay platform