How to pay with crypto

Checkout is crypto-only. After you place an order you pick a payment rail (coin + network), then send from your own wallet. We show a receiving address, the exact amount to send, and a QR code.

1. Choose the right rail

Only rails that are enabled and have a live receiving address appear on your payment page. Common options include USDT on TRC20 or BEP20, BTC, ETH, SOL, XMR, and — when offered — USDT/USDC on ERC20, LTC, DOGE, or XRP. Pick the rail your wallet can send on. Wrong network = funds can be lost (for example USDT on ERC20 will not arrive on a TRC20 invoice).

2. Address, network, and tags

Copy the address from the payment page (or scan the QR). Double-check the first and last characters.
Send on the exact network named on that page (TRC20 / BEP20 / Bitcoin / Ethereum / Solana / Monero / XRP Ledger, etc.).
XRP: use the classic r… address shown. If the page shows a destination tag, enter that tag in your wallet. Sending without the required tag can delay or prevent matching.

3. Exact amount and time window

Send the exact crypto amount shown for that invoice. The amount is locked for about 30 minutes (the invoice timer on the page). If the timer ends, do not send to the old address — open the order and create a fresh invoice.

Your wallet also pays a network fee (gas) on top. Fee figures on the page are estimates (they vary by network congestion and your wallet settings). We must receive the invoice amount; underpayment goes to manual review.

4. After you send

Waiting for payment — invoice is open; nothing matched yet.
Payment detected / confirming — a matching transfer is seen and waiting for network confirmations (each rail has its own minimum).
Paid – order confirmed — payment matched and confirmed. We do not pack or dispatch until the order is paid.

You can paste a transaction ID (TXID) with “I have paid” when the page asks for it. That helps matching. Many rails can also be detected by watching the address for the fingerprinted amount, but a TXID is still useful when prompted.

5. Pending or manual review

Some payments need a person to check them, for example under/overpayment, ambiguous matches, explorer outages, or Monero when automatic checking is not available on the server. In those cases the page shows a review state — contact Support with your order number and TXID. Do not send a second payment unless Support asks you to.

Network fees, confirmation times, and which rails appear can change. Always follow the amounts and labels on your payment page for that order.