Cryptocurrency payment processing

Cryptocurrency payment processing, end-to-end: chain, conversion, ledger.

topropay handles the operational pipeline behind cryptocurrency payments — authorisation, on-chain confirmation, optional conversion-on-receipt, AML and Travel Rule, settlement and reconciliation — through licensed partner crypto gateways under one unified API.

Book a processing review Read the API docs
USDC · Base · vault token vt_9421
  1. 0x9421 authorised 189.00 USDC · Base
  2. 0x9422 block + 1 pending event sent
  3. 0x9423 confirmed depth reached
  4. 0x9424 convert → €188.65
  5. 0x9425 settle merchant bank · T+1
5 events · 1 ledger row · audited end-to-end
Stablecoins
USDC, USDT, DAI, PYUSD
L2 rails
Base, Arbitrum, Optimism, Polygon
Travel Rule
where the rail supports it
1 ledger
across crypto and fiat

Key benefits

Why orchestrated cryptocurrency payment solutions beat single-provider stacks

Four outcomes that show up consistently once crypto runs through the same orchestration layer as fiat rather than a separate console.

  1. 01

    Authorisation, confirmation and settlement on one timeline

    cryptocurrency payment processing on the platform treats authorisation, on-chain confirmation, optional fiat conversion and merchant settlement as one event lifecycle. The merchant sees a single normalised state machine for each payment regardless of the underlying chain.

  2. 02

    Conversion-on-receipt to keep treasury fiat-only

    Conversion-on-receipt policies convert incoming stablecoins, majors or L2 tokens to the merchant's settlement currency at the rail's quote — the merchant's balance sheet never carries crypto unless treasury wants it to.

  3. 03

    AML, Travel Rule and address screening

    Connected partner crypto gateways run on-chain address screening, sanctions checks and (where the rail supports it) FATF Travel Rule metadata capture. Flagged authorisations are rejected at the gateway, not at the merchant surface.

  4. 04

    One reconciliation feed across crypto and fiat

    Crypto receipts, conversion fees and settlement amounts roll into the same ledger as card, ACH and bank-rail receipts. Finance closes the month from one export rather than a crypto-side ledger merged manually with everything else.

How it works

From wallet signature to a confirmed ledger row

Six stages between the buyer's wallet signature and a closed reconciliation row. Each stage emits a normalised event for the merchant's back-end to track.

  1. 0x9421 Authorise

    Wallet POST

    The connected gateway receives the authorisation, locks the rate (if quoted in fiat) and broadcasts the transaction to the chain.

  2. 0x9422 Block 1

    First inclusion

    Transaction mined into the chain. The gateway emits a 'pending' event; merchant back-end can show 'payment received, awaiting confirmation'.

  3. 0x9423 Block 2

    1 confirmation

    Required confirmation depth depends on the asset and rail: 1 for L2s on most stablecoins, 3-6 for BTC on Lightning, 12+ for legacy BTC mainnet on high-ticket.

  4. 0x9424 Depth N

    Finality reached

    Gateway emits 'confirmed' event; conversion-on-receipt fires if configured; the merchant ledger records the authorisation as final.

  5. 0x9425 Convert

    Conversion-on-receipt

    If conversion is enabled, the rail converts the asset to the merchant's settlement currency at the locked rate. The fiat amount surfaces in the reconciliation feed.

  6. 0x9426 Settle

    Merchant wallet / bank

    Settlement lands in the merchant's connected fiat bank (after conversion) or in the merchant's wallet (without conversion). The lifecycle row closes.

Model comparison

Stand-alone cryptocurrency gateway vs orchestrated processing

Two valid models. The stand-alone gateway is simpler to buy and limited to one provider's appetite; the orchestrated model trades a slightly larger up-front integration for years of optionality.

Dimension Stand-alone crypto gateway topropay orchestrated processing
Integration Direct integration with one crypto PSP One API across multiple connected partner crypto gateways alongside fiat methods
Reconciliation Separate crypto ledger Crypto and fiat normalised into one ledger keyed off vault tokens
Conversion Manual treasury work, batch conversion or limited auto-convert Conversion-on-receipt per asset per merchant, surfaced in the same reconciliation row
AML / Travel Rule Per-provider posture; merchant carries the integration burden Inherited from the partner gateway with rail-aware Travel Rule metadata
Onboarding Direct underwriting at the crypto PSP Single onboarding through topropay's sub-merchant model for licensed verticals
Multi-rail Often one chain / one asset class Stablecoins, majors and L2 rails — choice per merchant per market

Main use cases

Where accepting cryptocurrency as payment earns its keep

Six merchant shapes that benefit from a crypto rail through the orchestration layer.

  • DTC

    Online retail that wants a crypto rail without treasury risk

    Cryptocurrency for payments at checkout, with conversion-on-receipt keeping the merchant fiat-only on the balance sheet. The crypto rail just changes who can pay; reconciliation works the same way.

  • B2B

    Cross-border B2B invoicing in stablecoins

    Invoices to overseas counterparties paid in USDC or USDT clear faster than wire instructions and skip correspondent-bank fees. Treasury chooses whether to hold or convert per invoice.

  • Plat

    Marketplaces paying out sellers in stablecoin

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

  • Sub

    Wallet-pre-funded recurring billing

    Subscribers who pre-fund a merchant wallet have monthly recurring debits drawn from that wallet via stablecoin transfers; the recurring engine handles the schedule and the reconciliation.

  • Trav

    Travel and high-ticket with FX-sensitive buyers

    Stablecoin lane for the buyers who'd otherwise be hit by cross-border interchange and FX; card lane remains for buyers who prefer cards. Both settle into the same booking record.

  • PSP

    PSPs reselling crypto capacity

    Resellers expose payment with cryptocurrency to downstream merchants through topropay's connected gateway portfolio — without integrating each crypto gateway directly.

Platform features

Capabilities behind the cryptocurrency payment platform

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

  • Unified processing API

    One REST surface across crypto and fiat methods — same authorise / capture / refund / void verbs, same webhook event model.

  • Partner crypto gateways

    Crypto rails delivered through licensed partner gateways; topropay routes, abstracts and reconciles.

  • Conversion-on-receipt

    Per-asset conversion policy converts incoming crypto to settlement currency at the rail's quote.

  • Per-rail confirmation policy

    Configurable required-depth per asset and rail — 1 for L2 stablecoins, deeper for BTC mainnet on high-ticket.

  • Travel Rule support

    Where the partner rail supports the FATF Travel Rule, originator and beneficiary metadata is captured and retained per scheme rules.

  • Address screening

    Partner gateways run on-chain address screening against sanctions and risk lists; flagged authorisations are rejected at the gateway.

  • Vault & customer record

    Vault tokens identify the customer across crypto and fiat; refunds, captures and renewals share one customer view.

  • Per-asset routing policies

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

  • Signed webhooks

    Replay-safe webhook delivery for pending / confirmed / converted / settled / refunded across rails.

  • Operator portal

    One dashboard for crypto and fiat: authorisations, refunds, conversion rates and reconciliation.

  • Sandbox parity

    Sandbox that mirrors production crypto flows, including chain-confirmation events and conversion behaviour.

  • Audit log

    Operator actions, conversion-policy changes and refund events logged with actor identity and timestamp.

Trust & compliance

Compliance posture for cryptocurrency payment processing

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 rails
Crypto rails delivered through licensed partner gateways with VASP / MiCA-relevant authorisations in their region of operation.
AML / KYC inheritance
Sub-merchants inherit the partner-gateway AML / KYC posture; merchant-level KYB happens once during topropay onboarding.
Travel Rule metadata
Where the rail supports it, originator and beneficiary metadata is captured and retained per scheme rules and the relevant regulator's record-keeping requirements.
Address screening
On-chain address screening against sanctions and risk lists at the partner gateway; flagged authorisations are rejected before reaching the merchant surface.
Fiat-side 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 process

Add cryptocurrency payment processing without re-platforming your fiat side.

A 30-minute processing review walks through the rails relevant for your buyer base and jurisdiction, the conversion policy that fits treasury, and a sandbox to test against before any commercial commitment.

Book a processing review Read the API docs

Frequently asked

Buyer questions about cryptocurrency payment processing

Questions buyers ask before committing — covering the processing pipeline, AML posture, conversion behaviour and the regulatory shape per region.

  1. 01

    What does topropay mean by cryptocurrency payment processing?

    Cryptocurrency payment processing on topropay is the operational layer that turns a wallet-initiated transaction into a merchant ledger row — authorisation, on-chain confirmation, optional fiat conversion, settlement and reconciliation. The platform routes via licensed partner crypto gateways and reconciles their output into the same ledger as fiat receipts.

  2. 02

    How does the cryptocurrency payment gateway shape differ from a stand-alone PSP?

    A stand-alone cryptocurrency payment gateway provides the chain-side infrastructure for one provider, and the merchant integrates against that provider directly. topropay sits one layer above — multiple partner crypto gateways behind a single unified API, with routing, conversion policy and one reconciliation feed shared with the fiat side.

  3. 03

    What is the cleanest path to start using cryptocurrency for payments?

    The cleanest path to start using cryptocurrency for payments is: enable the relevant assets (typically USDC on Base or Solana, plus USDT on Tron for cross-border, plus BTC if the buyer base wants it), turn conversion-on-receipt on per asset to keep treasury fiat-only, and ship a Pay-With-Wallet button in the hosted checkout. Most merchants are live in a single sprint.

  4. 04

    What does payment by cryptocurrency mean in the API contract?

    Payment by cryptocurrency in the API contract is one of the supported method values on the same /v1/payments endpoint — the merchant sets method to the relevant crypto identifier, the platform routes through the connected partner gateway, and webhook events follow the same shape as card and bank-rail events.

  5. 05

    What cryptocurrency payment solutions are typical for merchants new to the rail?

    Cryptocurrency payment solutions for new-to-crypto merchants typically pair stablecoin acceptance (USDC, USDT) with conversion-on-receipt and a hosted Pay-With-Wallet checkout. That ships fast, keeps treasury fiat-only and gives the merchant production data before they commit to a deeper integration shape.

  6. 06

    What's the operational shape of payment cryptocurrency processing on the platform?

    Payment cryptocurrency processing on the platform runs as: a quote step (lock the rate in fiat for the authorisation window), the buyer signs from their wallet, the gateway watches the chain to the required depth, an authorised event fires on the merchant webhook, conversion-on-receipt (if enabled) fires next, and the reconciliation row closes once settlement lands.

  7. 07

    How is payment with cryptocurrency reconciled alongside fiat methods?

    Payment with cryptocurrency reconciles into the same ledger as fiat receipts. Each row carries the rail tag (crypto-USDC-base / crypto-BTC-lightning / card-EUR / etc.) plus the connected gateway ID and any conversion event. Finance can filter by rail or look at the consolidated picture from the same export.

  8. 08

    What does the cryptocurrency payment system actually expose to engineering teams?

    The cryptocurrency payment system exposes the same primitives engineering teams already use for card: authorise, capture, refund, void, cancel; signed webhooks for state changes; idempotency on POST endpoints; vault tokens identifying the customer. The crypto specifics — chain confirmation depth, quote locks, conversion-on-receipt — are configurable per asset rather than coded into your back-end.

  9. 09

    How does the platform let merchants accept cryptocurrency payments without holding the asset?

    To accept cryptocurrency payments without holding the asset, the merchant turns conversion-on-receipt on for every enabled crypto. Incoming stablecoins, majors and L2 tokens all settle to the merchant's chosen fiat currency at the rail's quote; the merchant's wallet never carries non-fiat balances.

  10. 10

    How does topropay compare to a stand-alone cryptocurrency gateway provider?

    A stand-alone cryptocurrency gateway ships one provider's infrastructure; topropay's orchestration sits across multiple partner crypto gateways and routes between them, much like the fiat-side acquirer panel. The merchant integrates once and benefits from multi-provider depth without managing multiple integrations.

  11. 11

    What's the value of treating topropay as a cryptocurrency payment platform vs a payment-method add-on?

    Treating topropay as a cryptocurrency payment platform — rather than bolting crypto onto a fiat-only stack — collapses the integration surface: same vault, same webhooks, same reconciliation, same operator portal. Adding a new crypto asset later becomes a dashboard step rather than a fresh integration project.

  12. 12

    Are cryptocurrency payment services available alongside the platform's other categories?

    Cryptocurrency payment services on topropay sit inside the wider service catalogue alongside card, ACH, subscriber and merchant payment services. Crypto is one category among many — turn it on when it fits the merchant's buyer base, leave it off when it doesn't.

  13. 13

    What does the platform consider the best cryptocurrency payment gateway choice for a given merchant?

    The best cryptocurrency payment gateway choice for a given merchant depends on geography, buyer base and asset preference. The orchestration model makes the question less binary: the merchant picks the assets and chains they want to accept, and the platform routes via the connected partner gateway best-equipped for each. The 'best' becomes per-asset rather than per-merchant.

  14. 14

    Can a merchant accept cryptocurrency as payment for high-ticket items where confirmation depth matters?

    Yes — to accept cryptocurrency as payment for high-ticket items, configure deeper required confirmation depth per asset (e.g. 6+ for BTC mainnet, 1 for stablecoins on most L2s). The platform waits for the configured depth before emitting the 'confirmed' event; the merchant order-management system holds the order until that fires.

  15. 15

    What's the regulatory posture for accepting cryptocurrency as payment in EU vs other markets?

    Accepting cryptocurrency as payment in the EU is generally covered by MiCA-relevant authorisations on the partner gateway side from late-2024 onwards; in the UK, FCA-registered crypto-asset firms are the standard pattern. Other markets vary — topropay 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