On-chain rails · via licensed partners

Blockchain payment system, unified with fiat on one API.

Accept stablecoins, major tokens and L2-network payments through licensed partner crypto gateways. Optional conversion-on-receipt keeps treasury fiat. Crypto rows and card rows share the same reconciliation feed.

Book a crypto-side review Read the API docs
#01 a4f2… USDC #02 9c81… USDT #03 3e0b… DAI #04 d770… ETH topropay orchestration multi-chain · multi-token · multi-currency
Stablecoin · major · L2 — confirmed on-chain · cleared on-platform.
USDC · USDT · DAI
Stablecoins as the default acceptance rail
BTC · ETH · SOL
Majors plus L2 networks via partners
Conversion
On-receipt fiat conversion, optional
1 ledger
Crypto + fiat in one reconciliation feed

Key benefits

Why this blockchain payment gateway shape pays off

Four properties that show up the moment a merchant adds on-chain rails alongside their fiat acceptance — without making it a separate stack.

Stablecoin acceptance without writing chain code

Partner crypto gateways handle the on-chain mechanics — confirmations, mempool, gas. topropay's API exposes them as a payment method alongside card, ACH and SEPA, so the merchant integrates once.

Conversion-on-receipt keeps treasury fiat

Optional conversion routes every accepted stablecoin or major-token receipt into fiat on settlement. Merchants who want crypto in treasury can opt out per currency and per market.

Multi-chain without per-chain projects

USDC on Ethereum, USDC on Solana, USDT on Tron, DAI on L2 networks — each is a routing-policy entry behind the same API. Adding a chain doesn't change the merchant's checkout code.

One reconciliation across crypto and fiat

On-chain receipts, fiat conversion rows, partner-gateway fees and refund events normalise into the same ledger as card and bank-rail settlements. Finance reads one feed, not two stacks.

How blockchain payment processing works

From wallet broadcast to one reconciliation row in five steps

What actually happens between the buyer signing the on-chain transaction in their wallet and the row appearing in the merchant's unified ledger.

  1. 01

    Buyer picks a stablecoin or token

    The hosted checkout surfaces the chains and currencies the merchant has enabled; the buyer chooses one and the partner crypto gateway issues a deposit address or QR.

  2. 02

    On-chain transaction broadcast

    Buyer signs and broadcasts via their wallet of choice; the partner gateway watches the mempool and confirmations, holding the order pending finality.

  3. 03

    Confirmations & finality

    Per-chain confirmation thresholds (configurable per merchant per chain) gate the move from 'received' to 'cleared'. Reorgs are handled by the partner gateway before clearing.

  4. 04

    Optional fiat conversion

    If the merchant has opted into conversion-on-receipt, the partner gateway swaps the inbound token into fiat at the quoted rate and settles fiat to the merchant.

  5. 05

    Reconciliation in one ledger

    Inbound token row, conversion row, gateway-fee row and net-fiat row all appear in the unified ledger tagged by chain, token, partner gateway and currency.

Main use cases

Where blockchain payment solutions earn their keep

Six recurring merchant shapes that benefit from on-chain rails sitting alongside card and bank acceptance.

  • DTC

    Cross-border DTC accepting stablecoins

    Merchants serving crypto-native buyers across borders surface stablecoin alongside card and bank-rail methods on the same checkout — different payment-processing using blockchain rails per market, one integration.

  • B2B

    B2B cross-border invoicing

    High-ticket B2B invoices to overseas counterparties settle in USDC or USDT; fiat conversion on the merchant side keeps treasury in EUR / USD / GBP.

  • PSP

    PSPs adding crypto to their downstream offering

    Resellers add stablecoin + on-chain acceptance to their downstream merchants without taking on a VASP licence themselves; topropay's partner gateways carry the licensed footprint.

  • SaaS

    SaaS billing in stablecoins

    Subscription merchants offering stablecoin billing alongside card-on-file for international customers who prefer settling on-chain.

  • Plat

    Marketplaces with mixed-rail sellers

    Marketplaces routing fiat or stablecoin payouts per seller — sellers in less-banked geographies receive stablecoin, the rest receive bank rail.

  • Tres

    Treasury / cross-currency liquidity

    Stablecoin rails as an internal treasury tool for moving liquidity between geographies the merchant operates in, alongside fiat conversion as an export step.

Platform features

Capabilities behind the blockchain payment processor relationships

Twelve capabilities shared across every connected partner crypto gateway — the primitives that make the multi-partner panel feel like one product.

  • Partner crypto gateways Licensed crypto / VASP partners deliver the on-chain rails; topropay handles orchestration on top.
  • Stablecoin acceptance USDC, USDT, DAI, PYUSD across the major chains supported by the partner panel.
  • Major tokens & L2 BTC, ETH, SOL plus L2 networks (Polygon, Arbitrum, Base, Optimism) where the partner supports them.
  • Conversion on receipt Optional swap-to-fiat at the partner gateway; per-merchant and per-currency policy.
  • Configurable confirmations Per-chain confirmation thresholds set in the dashboard; finality bar tuned to merchant's risk tolerance.
  • Hosted, embedded & SDK Crypto methods surface in the hosted checkout, embedded fields and SDK surfaces — same as card.
  • Multi-currency settlement Settlement currencies per market — EUR, USD, GBP, BRL and others where partner connectivity exists.
  • Unified dispute / refund flow Refunds on crypto rails reverse the original receipt against the partner gateway; no chain-level chargebacks.
  • Risk & sanctions screening Sanctions screening on inbound addresses; chain-analytics signals integrated at the partner gateway.
  • Webhook event stream Signed webhooks for received / confirmed / cleared / converted / settled events; replay-safe IDs.
  • One reconciliation feed Inbound token rows, conversion rows and fiat settlement rows in one ledger tagged per chain and token.
  • Audit-grade event log Every state transition on every crypto receipt logged with timestamp, chain, partner gateway and net amount.

Industry relevance

Where blockchain in payment processing earns its keep

topropay's crypto-side posture targets licensed merchants operating across Europe, the UK, APAC and LATAM — cross-border B2B, crypto-native consumer brands, marketplaces with mixed-rail payouts, and licensed financial-services firms layering on-chain settlement onto an existing fiat stack.

  • Cross-border DTC · stablecoin volume
  • B2B cross-border invoicing
  • SaaS · stablecoin billing
  • Marketplaces · mixed-rail payouts
  • Licensed financial services
  • PSPs adding crypto downstream
  • Unlicensed token issuance · out of scope
  • Grey-market crypto exchanges · out of scope
  • Adult / unlicensed gambling · out of scope

Trust & compliance

Compliance posture across partner crypto gateways

On-chain rails are delivered through licensed partner gateways with the relevant VASP / MiCA authorisations. topropay layers orchestration, reconciliation and merchant-side controls on top.

Licensed partner gateways
Crypto / on-chain rails delivered through licensed partner gateways with VASP / MiCA-relevant authorisations. topropay does not hold a crypto-asset-service-provider licence directly.
PCI DSS Level 1 (fiat side)
Fiat-side acceptance — card, ACH, SEPA — runs on the PCI L1 vault; merchants accepting both fiat and crypto inherit the posture for the fiat half.
AML / KYT screening
Inbound on-chain transactions screened via chain-analytics at the partner gateway; sanctioned address lists enforced before clearing.
FATF Travel Rule alignment
Where the inbound transaction triggers Travel Rule reporting, partner gateways carry the required counter-party information per their licence terms.
Sanctions & merchant onboarding
Merchants accepting crypto rails go through the same KYB / sanctions check as fiat-only merchants; high-risk jurisdictions are flagged in underwriting.
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 — including unlicensed crypto-asset issuance — are out of scope.

Ready to add on-chain rails

Add stablecoin and on-chain acceptance to one API.

A 30-minute crypto-side review covers the chains and tokens relevant to your buyers, conversion-on-receipt policy, partner-gateway availability per geography, and a sandbox you can test against before any commercial commitment.

Book a crypto-side review Read the API docs

Frequently asked

Buyer questions about blockchain payment system on topropay

Definitions, partner-gateway model, conversion-on-receipt mechanics, AML posture, refund flow and the practicalities of running crypto rails alongside fiat.

  1. 01

    What does blockchain payment system mean in topropay's context?

    A blockchain payment system on topropay means accepting stablecoin and on-chain token payments through licensed partner crypto gateways, alongside fiat (card, ACH, SEPA, wallet) on the same unified API. topropay supplies the orchestration, vault on the fiat side, reconciliation and dashboard; the partner gateways supply the on-chain mechanics and licensing.

  2. 02

    Is topropay itself a blockchain payment gateway?

    topropay is the orchestration layer; the blockchain payment gateway role is filled by licensed partner crypto gateways that topropay connects to. The merchant integrates one API and gets both — the orchestration plus the partner-delivered on-chain rail — without managing two relationships separately.

  3. 03

    How does the payment gateway blockchain side compare with the card gateway?

    The payment gateway blockchain side and the card-gateway side run through the same API surface but underneath behave differently. Card auths clear in seconds with chargeback rights; blockchain receipts clear at the configured confirmation count with no chain-level chargebacks. The platform absorbs the per-rail differences and presents one event stream.

  4. 04

    What does blockchain payment processing actually involve on the platform?

    Blockchain payment processing involves: surface the chain / token options in the checkout, receive the on-chain transaction at the partner-gateway address, watch confirmations to finality, optionally swap to fiat, settle to the merchant. Each step is platform-observable; merchants don't read the chain directly.

  5. 05

    Is there a single blockchain payment processor in the panel?

    There is more than one blockchain payment processor across the partner panel; coverage and chain support varies by partner. Routing across them is policy-driven — for some merchants a single partner is sufficient; for higher-volume or multi-chain merchants the policy picks per chain and token.

  6. 06

    What blockchain payment solutions does topropay bundle out of the box?

    Blockchain payment solutions out of the box include: stablecoin acceptance (USDC, USDT, DAI, PYUSD) on the major chains, major-token acceptance (BTC, ETH, SOL) where the partner supports it, optional conversion-on-receipt to fiat, multi-chain routing, and unified reconciliation alongside fiat. Outgoing payouts on crypto rails are supported via the same partner relationships.

  7. 07

    Why use payment processing using blockchain rather than just card and bank rail?

    Payment processing using blockchain suits cross-border flows where bank rails are slow or expensive, settlement to less-banked geographies, and crypto-native buyer bases. It's not a replacement for card — most merchants run both. Stablecoins reduce volatility exposure compared with major-token acceptance.

  8. 08

    Which blockchain payment processing companies do you partner with?

    The list of blockchain payment processing companies in the connected panel is shared under NDA during onboarding. Coverage criteria — chains supported, licence footprint, fiat-conversion availability — vary per partner; routing across the panel is dashboard-configurable per merchant.

  9. 09

    How does payment processing blockchain handle chargebacks and disputes?

    Payment processing blockchain has no chain-level chargeback mechanism; once a transaction is mined and confirmed, it's irreversible. Disputes are handled commercially between merchant and buyer; refund flows on the platform send a separate on-chain transaction back to the buyer's address, logged in the unified reconciliation feed.

  10. 10

    What's the role of blockchain in payment processing for a typical merchant?

    Blockchain in payment processing for a typical merchant tends to be a complementary rail — a few percent of total volume on most B2C, higher share on B2B cross-border and crypto-native verticals. The role evolves with the buyer base; the platform makes it possible to test a chain without making it the primary rail.

  11. 11

    What's needed to integrate blockchain for payment processing?

    To integrate blockchain for payment processing on topropay, the merchant enables the partner crypto gateway in the dashboard, picks the chains and tokens to accept, configures confirmation thresholds and conversion-on-receipt policy, and tests in sandbox. Most merchants are live within 1–2 weeks of the dashboard enablement.

  12. 12

    Does the platform handle the FATF Travel Rule and other crypto AML requirements?

    Travel Rule reporting on inbound transactions that meet the relevant threshold sits with the licensed partner gateway carrying the transaction, per their authorisations. Chain-analytics screening and sanctioned-address enforcement happen at the partner-gateway level before topropay clears the receipt to the merchant.

  13. 13

    Can refunds run on the crypto side?

    Refunds on the crypto side send a fresh on-chain transaction back to the buyer's address, executed by the partner gateway against the merchant's balance. The refund event is logged in the unified reconciliation feed and tied to the original receipt; gas costs are netted per the merchant's pricing agreement.

  14. 14

    How are exchange-rate moves handled when accepting volatile tokens?

    Conversion-on-receipt is the recommended posture for merchants who don't want exchange-rate exposure: the partner gateway quotes a fiat rate at receipt confirmation, performs the swap, and settles fiat. For stablecoin acceptance the conversion is near-par; for major-token acceptance the rate is locked at the receipt timestamp.

  15. 15

    What about verticals topropay doesn't serve on the crypto side?

    topropay does not serve unlicensed crypto-asset issuance, unlicensed token sales, grey-market crypto exchanges, or merchants whose primary revenue is in non-compliant categories. The partner crypto gateways enforce the same licensed-verticals posture as topropay's fiat-side relationships.

Related

Related on the topropay platform