Same address format, different network
A 0x address may exist on several EVM networks. Customers must select Ethereum; address format alone does not identify the route.
Payment integration
Accept USDT / USDC on Ethereum
Receive USDT / USDC directly into your wallet on Ethereum. BoltUtil checks transfers against orders and sends signed notifications after payment confirmation.
Steps to follow
From payment order to fulfillment
For merchants whose customers hold the configured assets on Ethereum. Enable the route and configure a valid wallet first; the example uses USDT.
01 Configure wallets for enabled token / network pairs and retain your private keys.
02 Save a merchant order ID, create the payment order and display checkout with the full payable amount.
03 BoltUtil checks the transfer against network, token, wallet and amount, then waits for confirmation.
04 Your server verifies the callback, checks the order, deduplicates and fulfills.
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
Match the configured token
USDT and native USDC use separate configured contracts. Native ETH and lookalike tokens do not count as stablecoin payment.
Wait for confirmation
A successful transfer and an order confirmation are separate stages. Check configured progress before verifying and fulfilling.
POST /api/v1/order/create
Content-Type: application/json
{
"externalOrderId": "ORDER_DEMO_001",
"amount": 199,
"currency": "USDT",
"network": "ERC20",
"notifyUrl": "https://merchant.example.com/webhooks/boltutil",
"returnUrl": "https://merchant.example.com/orders/001"
}Server-side integration example only; no requests are sent. Supply the API key, timestamp and exact-body signature, and validate local orders and prices.
Read API docsPayment integration
Questions merchants ask before going live
Which assets does the Ethereum route accept?
Enabled Ethereum USDT / USDC routes with valid wallets are supported. Check the version and configured contract or mint, not the symbol alone.
Does BoltUtil hold the payment?
No. Customers transfer directly to your configured wallet. BoltUtil checks orders and payments without custody or access to private keys, seed phrases or withdrawal authority.
Do all networks support USDT and USDC?
TRON supports USDT only. Other networks support the configured USDT / USDC versions. Availability depends on enabled channels and merchant wallets; use the API and checkout response as the source of truth.
Can I fulfill when a customer returns?
returnUrl is navigation, not payment evidence. Use a verified callback or trusted server-side status query, check the order and fulfill once.
How are payment differences handled?
Free merchants can view their own review records. Qualifying manual-transfer differences can create review records; verify ownership when several orders are candidates. Active membership is required to accept or reject an association. Acceptance confirms payment and triggers the configured callback.
Can customers connect a wallet without entering the amount?
Yes. Wallet checkout prepares the recipient, token and complete payable amount on supported networks and devices. Customers review and confirm in their wallet. First use may require unlocking, connection approval or a network switch. QR codes and copied addresses remain available for manual transfer; both methods require on-chain confirmation.
What network fees apply to Ethereum stablecoin transfers?
Wallet transfers on Ethereum require ETH for network fees. Wallet and exchange fees, withdrawal minimums and supported networks vary. Check the current prompt and do not pay on a different network.
Launch a cleaner USDT / USDC payment flow
Create orders, monitor transfers, and notify your backend without asking customers to send screenshots.