How to accept USDT on your website: a step-by-step guide

Accepting USDT is simpler than it sounds. The customer already holds the coin, so your job is to show them an exact amount, an address that belongs only to this order, and to know the moment the transfer is confirmed. A payment gateway does those three things for you.

1. Decide what you need from a gateway

Look at four things: which networks the customer can pay on, what the fee is on each, how you learn that an order is paid, and what you receive. With CryBit the customer picks a coin and a network on the payment page, the fee is shown live before they pay, you get a webhook when the invoice is paid, and the money lands on your balance in USDT.

2. Create a merchant and test it

Register, add a site or an app and send it for review. Sandbox mode works at once: you can create test invoices and mark them as paid on the payment page without moving any money. Live accepting, API keys and payouts open after the review.

3. Create an invoice for every order

An invoice is a payment request with an amount, a currency and a lifetime. Send your own order number in order_id so you can match the payment later. You can price in your own currency, such as RUB, USD or EUR, or directly in USDT. The customer is sent to the payment page.

4. Let the customer choose the network

USDT lives on many networks and the customer usually holds it on one of them. TRON is the most common, BNB Chain and the Ethereum layer-2 networks are cheap, Ethereum suits larger amounts. Offering several networks means fewer abandoned payments.

5. Wait for confirmation, then fulfil

Do not ship on the customer's word or on a screenshot. Ship when the invoice status becomes paid, which happens after the network confirms the transfer. Rely on the webhook or on a status request, not only on the browser event on your page.

6. Get paid

Coins other than USDT are converted at the market rate and USDT is credited to your balance. You can pay out to your own address. The amount you book does not depend on the coin price a minute later.

Common mistakes

• Using one static wallet for all orders, so payments cannot be told apart.
• Confirming an order from the browser instead of the server.
• Offering only one expensive network.
• Forgetting that the invoice expires: create a new one instead of reusing an old address.

See how the whole path works on the how-it-works page, and the exact API calls on the developers page.