A crypto payment gateway you run alongside your exchange
Online shops, platforms and service businesses accept crypto through your gateway. They create invoices in their own currency, their customers pay on a hosted checkout page, and you earn a fee on every payment and payout.
A second business on the same infrastructure
An exchange already has what a crypto payment gateway needs: wallets on several blockchains, deposit detection, hot wallets for sending, and a team that knows how to run them. The merchant module puts those to work for other businesses.
Merchants sign up, are reviewed by your team and get a dashboard and API keys. Every payment they receive and every payout they request goes through the same network layer as your exchange's deposits and withdrawals, so there is one set of wallets and one set of rules to look after.
Fee per merchant
Charge each merchant a percentage of what they receive.
Same networks
Ethereum, BNB Chain, Polygon, TRON, Solana and TON.
Onboarding
Merchants apply and your team approves them before they can take payments.
Developer ready
REST API, signed webhooks and public docs for merchant developers.
From invoice to confirmed payment
The merchant creates an invoice
In the dashboard or through the API, priced in USD, with an order reference and optional return URL.
The customer opens the checkout
A hosted payment page where they choose a coin and network and see the exact amount, address and QR code.
The rate is held
The amount is fixed for a limited time, with a countdown on the page, so the customer is not hit by price changes while paying.
The payment is detected
The platform finds the transfer on chain, waits for the required confirmations and marks the invoice paid.
The merchant is notified
A signed webhook goes to the merchant's server, and the customer is sent back to the shop.
Merchant dashboard
Merchants see their balance per coin, invoices and their status, received payments, payouts and refunds. They manage API keys and webhook URLs in the same place and can test a webhook before going live.
Every payment ends in a clear status
Customers send the wrong amount and pay late. The gateway handles each case instead of leaving funds in limbo.
| Status | Meaning | What follows |
|---|---|---|
| Pending | Waiting for the customer's transfer | Countdown runs on the checkout page |
| Confirming | Transfer found, waiting for confirmations | Customer sees progress |
| Paid | Right amount, confirmed | Merchant balance credited, webhook sent |
| Underpaid | Less than the invoice amount arrived, beyond the allowed tolerance | The customer sees what is missing; the merchant decides how to settle |
| Overpaid | More than the invoice amount arrived | The extra can be refunded to the customer |
| Expired | No payment before the deadline | A late payment can still be refunded |
Getting money out, safely
Payouts
Merchants request a payout of their balance to their own wallet. Your team approves or rejects it in the admin panel. Approved payouts are sent from your hot wallet, and the transaction hash is stored and shown to the merchant.
Refunds
Full and partial refunds of a paid invoice, refunds of an overpayment, and refunds of a payment that arrived after the invoice expired. Each refund goes through the same review and sending steps as a payout.
No double sends
If the network does not answer while a payout is being sent, the payout is held for review instead of being marked failed and paid again. Your team checks the chain and settles it by hand.
Approve or reject
Every payout and refund waits for your team.
Transaction hash
Stored and shown to the merchant once sent.
Needs review
Unclear network results are held, never resent blindly.
Four refund types
Full, partial, overpayment and late payment.
Built for merchant developers
- A REST API to create invoices, read their status and list payments
- API keys created and revoked by the merchant
- Webhooks signed with HMAC-SHA256, so merchants can check each one came from you
- Automatic retries, with failed deliveries kept for review and resend
- Public documentation pages with request and response examples
Merchants who do not want to write code can create invoices in the dashboard and send the payment link to their customer by email or chat.
Running the gateway
- Review and approve merchant applications
- Set each merchant's fee and see your earnings per merchant and per month
- Browse all invoices, payments, payouts and refunds
- Handle payments that could not be matched to an invoice
- Watch webhook deliveries and resend failed ones
- Collect funds from merchant deposit addresses into your main wallets
- Reports for finance and compliance
Crypto payment gateway questions
Which package includes the payment gateway?
The merchant (payment acquiring) module is part of the Enterprise package. See pricing.
Which coins can merchants accept?
Coins and tokens on Ethereum, BNB Chain, Polygon, TRON, Solana and TON that you enable, for example USDT and USDC on several networks.
How does a merchant get paid?
Payments are credited to the merchant's balance in the gateway. They request a payout to their own wallet, which your team approves and the platform sends.
What happens if a customer pays the wrong amount?
Small differences within a tolerance count as paid. Beyond that, the invoice is marked underpaid or overpaid. The customer sees what is missing on an underpaid invoice, and the extra on an overpaid one can be refunded.
How do merchants know an invoice is paid?
Through a webhook signed with HMAC-SHA256 sent to their server, through the API, and in their dashboard.
How do I earn from the gateway?
You set a fee percentage per merchant. Your earnings show per merchant and per month in the admin panel.
