How crypto payment gateways work
A crypto payment gateway sits between your checkout and a dozen blockchains. It turns a price into an exact crypto amount, gives the customer somewhere to send it, watches the chain until the transfer is final, and tells your site the order is paid. This post follows one payment through easyway, step by step, with the real numbers the system uses.
1. The invoice
Everything starts with an invoice: an amount, usually in USD, plus your order id and where to send the customer afterwards. Your backend creates it through the API (POST /v1/invoices), or a payment link creates one for each visitor. The invoice gets a hosted checkout page and an expiry time — 60 minutes by default, adjustable from 5 minutes to 24 hours.
2. Turning dollars into an exact crypto amount
On the checkout page the customer picks one of 75 coins on 15 networks. At that moment the gateway locks the crypto amount. Stablecoins such as USDT and USDC are priced at exactly 1 USD. Every other coin is priced from up to four public sources (CoinGecko, Binance, KuCoin and Coinbase), refreshed at most once a minute; a source more than 3 % away from the median is ignored, and if two sources disagree the previous price is kept. If no fresh price is available for 15 minutes, the gateway refuses to quote rather than sell at a stale price. The amount is rounded up, never down, so the merchant is not short-changed by rounding.
3. Somewhere to send it
The hard part of accepting crypto is knowing which customer paid. In easyway the money goes straight to the merchant's own wallet, set per network in the dashboard (Wallets), and the gateway tells invoices apart in one of three ways. On Bitcoin, Litecoin, Dogecoin and Dash the merchant can give an extended public key, and each invoice gets a fresh address of that wallet; no private key is ever needed. On TRON, the EVM chains and Solana the merchant gives one address, and invoices sharing it are told apart by the exact amount: the checkout asks for an amount made unique with a few extra decimals (25.001 USDT, say; the first invoice for an amount gets the round figure). On TON and the XRP Ledger every invoice gets a numeric memo (destination tag on XRP) on the merchant's one address. A transfer that cannot be tied to exactly one invoice is listed as an unmatched transaction for the merchant to assign or ignore.
| Network | Coins | How a payment is matched | Confirmations |
|---|---|---|---|
| TRON | USDT, TRX | Exact amount per invoice | 19 |
| BNB Smart Chain | USDT, BNB, USDC, FDUSD, CAKE, TWT | Exact amount per invoice | 15 |
| TON | USDT, GRAM, NOT, DOGS, CATI, HMSTR | Comment (memo) per invoice | 1 |
| Ethereum | USDT, ETH, USDC, DAI, SHIB, PEPE, PYUSD, LINK, UNI, AAVE, ONDO, ENA, CRV, GRT, SKY, USDS, USDe, MNT, ARB, WLD, MANA, SAND, IMX, GALA, FET, JASMY, SPX, XCN, APE, AXS, CHZ, 1INCH, PENDLE, ETHFI, ZRO, BAT, LPT, ZRX, SUSHI, BAL, COMP, RPL, ANKR, CVX, GLM | Exact amount per invoice | 12 |
| Bitcoin | BTC | New address per invoice (extended public key); exact amount if you set a single address | 2 |
| Litecoin | LTC | New address per invoice (extended public key); exact amount if you set a single address | 4 |
| Dogecoin | DOGE | New address per invoice (extended public key); exact amount if you set a single address | 6 |
| XRP Ledger | XRP | Destination tag per invoice | 1 (validated ledger) |
| Solana | SOL, USDT, USDC, BONK, WIF, RENDER, JUP, PYTH, JTO, RAY, W, FARTCOIN, TRUMP, PENGU, POPCAT | Exact amount per invoice | 1 (finalized) |
| Polygon | POL, USDT, USDC | Exact amount per invoice | 64 |
| Avalanche | AVAX, USDT, USDC | Exact amount per invoice | 10 |
| Base | ETH, USDC | Exact amount per invoice | 30 |
| Arbitrum One | ETH, USDT, USDC | Exact amount per invoice | 240 |
| OP Mainnet | ETH, USDT, USDC | Exact amount per invoice | 30 |
| Dash | DASH | New address per invoice (extended public key); exact amount if you set a single address | 4 |
4. Waiting for the chain
A separate watcher process reads each chain and reports transfers to the addresses, amounts and memos it is watching. A transfer only counts after the number of confirmations in the table above: a few blocks on fast-final chains like TON, Solana and XRP, more on chains where blocks can be reorganised. Until then the checkout shows the payment as "confirming". Each on-chain transfer is counted exactly once — the database refuses a second report of the same transaction.
5. Paid, underpaid or late
When the confirmed amount covers the quote, the invoice becomes paid. Customers often send slightly less (an exchange deducts its fee, for example), so a 1 % underpayment tolerance — adjustable from 0 to 5 % — still counts that as paid. Anything further short makes the invoice underpaid: the received part is recorded and the checkout asks for the rest. A payment that arrives after the invoice expired is still watched for a while, and is recorded as paid with a late flag. The underpaid and late payments guide lists every case.
6. Telling your site
Each status change sends a webhook such as invoice.paid to your server, signed with HMAC-SHA256 over a timestamp and the body, so your code can prove it came from the gateway and is not a replay. If your server is down, the delivery is retried up to 8 times over about 45 hours. Your code checks the signature, looks up the order and fulfils it — see how to verify webhook signatures.
7. Fees and where the money goes
Nowhere in between: easyway is non-custodial. The customer pays straight into the merchant's own wallet, in the coin they chose, and easyway takes nothing from the payment — there is no balance to withdraw and no automatic conversion (a merchant who wants dollars converts on an exchange of their choice). easyway never asks for a private key or seed phrase, so it cannot move, reverse or refund a payment either; refunds are sent by the merchant from their own wallet. The merchant pays for a plan instead, from a free one upwards (see the pricing page). The security page describes this in more detail.
What to look for in a gateway
Whichever provider you use, ask the same questions this post answered: where the price comes from and when it is locked, how many confirmations each coin waits for, what happens on underpayment and late payment, how webhooks are signed and retried, whether it holds your money at all, and what it charges. A gateway that answers them in its documentation is easier to build on. To try easyway's answers yourself, create a test key and run the flow in the sandbox, or read how to accept cryptocurrency payments on your website.