Confirmation is not a fixed timer
Networks have different confirmation mechanisms. Display actual progress without promising a fixed arrival time.
Integration guide
Payment pending? Find the stage first
Separate order matching, chain confirmation, webhook delivery and your own fulfillment records before troubleshooting.
Steps to follow
Pending USDT / USDC payment triage flow
Best for merchants and support teams investigating paid-but-pending USDT / USDC orders across the six supported networks.
01 Query the original order: PENDING has no matched payment recorded.
02 PAID means a payment was recorded and confirmation is pending.
03 For CONFIRMED, inspect webhook delivery logs and your receiving endpoint.
04 COMPLETED follows a successful callback response. Check your application’s delivery records separately.
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
What matters before production
Separate payment and delivery states
PENDING has no matched payment recorded; PAID awaits confirmation; CONFIRMED indicates confirmed payment. COMPLETED follows a successful callback response and does not prove that your application has fulfilled the order.
Keep the original payment
Ask for the original transaction hash. Do not request another transfer just because confirmation is pending.
PENDING No matched payment recorded
PAID Payment recorded, awaiting confirmation
CONFIRMED Payment confirmed, inspect callbacks
COMPLETED Callback received a successful response
Check your own fulfillment records separately.Examples are for integration and troubleshooting only. No requests are sent. Use your order data, network configuration and current API documentation.
Read API docsIntegration guide
Questions merchants ask before going live
Does COMPLETED prove delivery?
PENDING has no matched payment recorded; PAID awaits confirmation; CONFIRMED indicates confirmed payment. COMPLETED follows a successful callback response and does not prove that your application has fulfilled the order.
Can a successful transfer alone complete an order?
No. Check the configured network and token, destination, payable amount, order window and confirmation progress. Verify callbacks and fulfill only once.
Do all six networks support both currencies?
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.
Launch a cleaner USDT / USDC payment flow
Create orders, monitor transfers, and notify your backend without asking customers to send screenshots.