Non-custodial settlement
Payments go to the merchant wallet you configure. BoltUtil monitors chain activity and does not need to hold user funds.
Recover failed payment webhooks
Webhook delivery can fail when merchant servers return errors. BoltUtil records delivery attempts and supports resend workflows for payment recovery.
- Built for
- Delivery logs
- Built for
- Retry status
- Built for
- Manual resend
Webhook resend checklist
1. Fix endpoint
2. Verify signature handling
3. Return HTTP 2xx
4. Resend the payment webhook
5. Confirm local order fulfillmentRecovery flow
Best for support and operations teams that need reliable fulfillment after temporary endpoint failures.
- 01
Inspect the webhook log for response code and error message.
- 02
Fix the merchant endpoint.
- 03
Resend the webhook from the dashboard or API.
- 04
Confirm the merchant backend returns success.
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