Choose a supported pair
TRON supports USDT only. Available USDT / USDC pairs on other networks depend on enabled channels and configured wallets. Compare the configured contract or mint, not just the token name.
Integration guide
An on-chain success does not prove that a transfer belongs to an order. Check the network, token, address, exact amount and payment window.
Steps to follow
Best for support teams and developers investigating customers who paid USDT / USDC but still see an unpaid or pending order.
Collect the tx hash and identify the network the customer actually used.
Verify the transaction is a successful USDT / USDC Transfer from the configured token contract.
Compare destination address, normalized amount, confirmations, order status, and expiration.
Inspect scanner progress and review records. Eligible difference handling requires active membership; confirmed-payment delivery failures belong in webhook troubleshooting.
BoltUtil checks payments and sends signed callbacks. Your server verifies signatures and order status, deduplicates events, then delivers goods, activates service or credits accounts.
Integration notes
TRON supports USDT only. Available USDT / USDC pairs on other networks depend on enabled channels and configured wallets. Compare the configured contract or mint, not just the token name.
Wrong amounts, expired windows or transfers already associated with another order cannot simply be marked paid.
Qualifying manual transfers can create review records; verify ownership when several orders are candidates. Free merchants can view their own records; accepting or rejecting an association requires active membership. Acceptance confirms payment and triggers the configured callback. Do not fulfill from a screenshot or an approximate amount.
Order network ≟ transfer network
Configured token ≟ actual contract / mint
Order wallet ≟ transfer recipient
Payable amount ≟ received amount
Order window ≟ payment time
Confirmation / scan progress
Transaction association / processing historyExamples are for integration and troubleshooting only. No requests are sent. Use your order data, network configuration and current API documentation.
Read API docsIntegration guide
Qualifying manual transfers can create review records; verify ownership when several orders are candidates. Free merchants can view their own records; accepting or rejecting an association requires active membership. Acceptance confirms payment and triggers the configured callback. Do not fulfill from a screenshot or an approximate amount.
No. Check the configured network and token, destination, payable amount, order window and confirmation progress. Verify callbacks and fulfill only once.
TRON supports USDT only. Available USDT / USDC pairs on other networks depend on enabled channels and configured wallets. Compare the configured contract or mint, not just the token name.
Create orders, monitor transfers, and notify your backend without asking customers to send screenshots.