Webhook tester for crypto payment callbacks

Before accepting production payments, verify that your webhook endpoint receives payloads, validates signatures, and returns a successful response.

Built for
Payload preview
Built for
Signature check
Built for
Delivery result
Webhook payload example
{
  "externalOrderId": "ORDER_2026_001",
  "status": "CONFIRMED",
  "amount": "199.000000",
  "currency": "USDT",
  "network": "TRC20",
  "txHash": "0x...",
  "confirmations": 20,
  "destinationAddress": "T..."
}

Webhook test flow

Best for developers preparing a production integration or debugging failed webhook delivery.

  1. 01

    Configure your webhook URL and secret.

  2. 02

    Send a test payload.

  3. 03

    Verify the signature in your backend.

  4. 04

    Return a 2xx response and inspect the delivery log.

Non-custodial settlement

Payments go to the merchant wallet you configure. BoltUtil monitors chain activity and does not need to hold user funds.

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