Cross-border payments for a business: a stablecoin playbook
Getting paid by a client in another country usually means an international bank transfer: intermediary banks, a currency conversion you do not control, and money that arrives days later, sometimes short. Stablecoins such as USDT and USDC move the same dollar amount over a public network instead, any day of the week. This post walks through how a business invoices foreign clients in stablecoins with easyway, and is honest about what that does and does not solve.
What changes compared with a bank transfer
A stablecoin payment goes straight from the client's wallet or exchange account to your own wallet, the one you set for that network in the dashboard. There is no correspondent bank in between, no cut-off time and no weekend: the invoice is marked paid once the network has confirmed the transfer, and easyway never holds the money. The sender pays the network fee, and the invoice waits for the exact amount it asked for. Because the invoice is priced in US dollars and stablecoins are counted at exactly 1 USD, a $2,400 invoice asks for 2,400 USDT or USDC (on networks where invoices are told apart by amount, possibly a few thousandths more, such as 2,400.001) — no exchange rate is involved on either end.
Step 1: pick the networks your clients can pay on
USDT on TRON and USDT on BNB Smart Chain are the same dollar, but they are separate tokens on separate networks, and a transfer on the wrong one does not arrive. Ask your client which network their exchange or wallet supports, then accept only those, and set your receiving wallet for each of them (dashboard → Wallets) before you send live invoices; without one the API answers 409 no_wallets_configured or wallet_not_configured. These are the stablecoin options today, with the confirmations needed before a payment counts, the smallest invoice, and how an invoice is recognised on that network:
| Asset id | Stablecoin and network | Confirmations | Min. invoice | Matched by |
|---|---|---|---|---|
USDT_TRC20 | USDT on TRON · TRC-20 | 19 | 0.5 USDT | Exact amount per invoice |
USDT_BEP20 | USDT on BNB Smart Chain · BEP-20 | 15 | 0.5 USDT | Exact amount per invoice |
USDT_TON | USDT on TON · Jetton | 1 | 0.5 USDT | Comment (memo) per invoice |
USDT_ERC20 | USDT on Ethereum · ERC-20 | 12 | 0.5 USDT | Exact amount per invoice |
USDC_ERC20 | USDC on Ethereum · ERC-20 | 12 | 0.5 USDC | Exact amount per invoice |
USDC_BEP20 | USDC on BNB Smart Chain · BEP-20 | 15 | 0.5 USDC | Exact amount per invoice |
USDT_SOL | USDT on Solana · SPL | 1 | 0.5 USDT | Exact amount per invoice |
USDC_SOL | USDC on Solana · SPL | 1 | 0.5 USDC | Exact amount per invoice |
USDT_POLYGON | USDT on Polygon · PoS | 64 | 0.5 USDT | Exact amount per invoice |
USDC_POLYGON | USDC on Polygon · PoS | 64 | 0.5 USDC | Exact amount per invoice |
USDT_AVAX | USDT on Avalanche · C-Chain | 10 | 0.5 USDT | Exact amount per invoice |
USDC_BASE | USDC on Base | 30 | 0.5 USDC | Exact amount per invoice |
USDT_ARB | USDT on Arbitrum One | 240 | 0.5 USDT | Exact amount per invoice |
USDC_ARB | USDC on Arbitrum One | 240 | 0.5 USDC | Exact amount per invoice |
USDT_OP | USDT on OP Mainnet | 30 | 0.5 USDT | Exact amount per invoice |
USDC_OP | USDC on OP Mainnet | 30 | 0.5 USDC | Exact amount per invoice |
USDC_AVAX | USDC on Avalanche · C-Chain | 10 | 0.5 USDC | Exact amount per invoice |
DAI_ERC20 | DAI on Ethereum · ERC-20 | 12 | 0.5 DAI | Exact amount per invoice |
FDUSD_BEP20 | FDUSD on BNB Smart Chain · BEP-20 | 15 | 0.5 FDUSD | Exact amount per invoice |
PYUSD_ERC20 | PYUSD on Ethereum · ERC-20 | 12 | 0.5 PYUSD | Exact amount per invoice |
USDS_ERC20 | USDS on Ethereum · ERC-20 | 12 | 0.5 USDS | Exact amount per invoice |
Network fees differ a lot: the client pays them on the way in, and you pay them again whenever you move the money on from your wallet. Ethereum is the most expensive of these networks. The per-coin pages, such as USDT on TRON and USDC, explain each network in more detail.
Step 2: send an invoice the client can pay from anywhere
Without code, create a payment link or a one-off invoice in the dashboard and send the link. If your billing system creates invoices, call the API: price the invoice in USD, limit it to the networks you chose with allowed_assets, and put your own invoice number in order_id. A lifetime of 1440 minutes (the maximum, 24 hours) suits an invoice sent by e-mail, where the client may not pay right away:
curl -X POST https://api.easyway.cash/v1/invoices \
-H "Authorization: Bearer $EASYWAY_API_KEY" \
-H "Idempotency-Key: inv-2026-0142" \
-H "Content-Type: application/json" \
-d '{"amount":"2400.00","currency":"USD","allowed_assets":["USDT_TRC20","USDT_BEP20"],"order_id":"INV-2026-0142","lifetime":1440,"metadata":{"client":"acme-gmbh"}}'The response contains a payment_url. The client opens it, picks a network, and gets your address (plus a memo on TON), a QR code and the exact amount, which is the invoice's pay_amount. Clients who pay from an exchange should add the exchange's withdrawal fee on top, because the amount that arrives has to match; on networks where invoices are told apart by amount, a short transfer may not be tied to the invoice and shows up as an unmatched transaction you assign by hand. A shortfall on a payment that is matched counts as paid up to your underpayment tolerance (1 % by default, adjustable from 0 to 5 %); anything more is marked underpaid with the remaining amount shown to the client. A payment that arrives after the invoice expired is still recorded and the invoice turns paid, flagged as late.
Step 3: reconcile without guesswork
Every invoice keeps your order_id and up to 20 metadata keys, so a payment always maps back to the right client and invoice number. Your server can react to the signed invoice.paid webhook (see verifying webhook signatures), and for the books you can export payments as CSV from the dashboard, or list them through the API, for any date range. Each payment shows the amount received and the transaction on the network; easyway takes no fee from it, so a 2,400 USDT payment is 2,400 USDT in your wallet.
Step 4: the money is already in your own wallet
Payments arrive directly in your wallet, in the coin and network the client used. easyway never holds them, so there is nothing to withdraw and no withdrawal fee; it also cannot move, reverse or refund a payment for you (a refund is a transfer you send from your own wallet). easyway does not convert to a local currency or pay out to a bank account. If you need local currency, you send the stablecoins to an exchange you already use and sell them there.
What stablecoins do not solve
Be clear-eyed about the trade-offs before you move your invoicing over:
| Concern | What it means for you |
|---|---|
| Your client needs crypto | They must hold USDT or USDC, or buy it on an exchange first. Offer it next to your usual payment method, not instead of it. |
| Taxes and local rules | Receiving crypto is treated differently from country to country. Check with an accountant where you are based; this post is not tax or legal advice. |
| Issuer risk | A stablecoin is a promise by its issuer to stay at $1. The gateway counts it as $1; if a token ever lost its peg, the loss would be yours. |
| Cashing out | Turning stablecoins into local currency happens on an exchange of your choice, with its own fees and limits. |
| Mistakes are final | A transfer on a network the invoice does not accept cannot be reversed by the gateway. Clear instructions (one invoice, one network list) prevent most of them. |
In short
Agree on a stablecoin and a network with your client, invoice in USD so the amount is unambiguous, let the order id and webhooks do the reconciliation, and receive every payment straight into a wallet you control. To try the whole flow without real funds, create a test key and follow the sandbox guide; the pricing page lists the plans, from a free plan to paid plans for more invoices a month.