Non-custodial settlement
Payments go to the merchant wallet you configure. BoltUtil monitors chain activity and does not need to hold user funds.
USDT transaction checker for payment matching
Use BoltUtil transaction diagnostics to understand whether a real USDT transfer can match a merchant order.
- Built for
- Check tx hash
- Built for
- Validate to address
- Built for
- Compare exact amount
What the checker validates
network == order.network
token_contract == USDT_contract
transfer.to == order.destinationAddress
transfer.amount == order.amount
order.status == PENDING
order.expireAt > nowDiagnostic checklist
Best for support teams debugging why a customer transfer did or did not match an order.
- 01
Identify the network and transaction hash.
- 02
Confirm the token contract is USDT on that network.
- 03
Compare Transfer.to with the order destination address.
- 04
Compare raw token amount with the order amount and decimals.
Three USDT networks
Accept USDT on TRC20, ERC20, and BEP20 with a single order API and unified webhook payload.
Webhook-first automation
Your system receives a signed callback when a transaction is detected and confirmed on-chain.
Questions merchants ask before going live
These answers help developers, founders, and support teams understand the payment lifecycle before accepting real USDT payments.
Does BoltUtil custody merchant funds? +
No. BoltUtil is designed as a non-custodial monitoring and notification layer. The merchant configures their own settlement wallet.
How does BoltUtil match a payment? +
The scanner matches network, destination address, exact USDT amount, order status, and expiration window before updating the order.
Which USDT networks are supported? +
The current production focus is TRC20, ERC20, and BEP20.
Related resources
Launch a cleaner USDT payment flow
Create orders, monitor transfers, and notify your backend without asking customers to send screenshots.
Create free account