Verify the player first
Link playerId, region and package to the order. Frontend input alone must not determine grants.
Payment use cases
Accept stablecoins (USDT / USDC) for credits, items and top-up packages. BoltUtil checks payment; your server verifies the player and order before granting credits or items.
From payment to fulfillment
Best for game stores, credit shops, and digital entertainment platforms.
Verify player, region and package on your server and create an order.
Show checkout with the network, asset and full amount.
Verify the signature and payment status against the original top-up order.
Record the credit in one business transaction to prevent duplicate grants.
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
Link playerId, region and package to the order. Frontend input alone must not determine grants.
You receive stablecoins and grant game benefits. Your system determines the conversion to credits.
Use order uniqueness or transaction protection for grants. Duplicate callbacks must not create extra player balance.
POST /api/v1/order/create
Content-Type: application/json
{
"externalOrderId": "ORDER_DEMO_001",
"amount": 199,
"currency": "USDC",
"network": "BASE",
"notifyUrl": "https://merchant.example.com/webhooks/boltutil",
"returnUrl": "https://merchant.example.com/orders/001",
"metadata": {
"playerId": "player_889",
"region": "region_1",
"package": "gold_500"
}
}This order request body is an example and sends nothing. Actual calls require an API key, timestamp and request signature. Merchant-defined metadata does not replace identity or price checks.
Read developer docsPayment use cases
No. BoltUtil sends the payment result. Your game server handles balances, regions, items and top-up records.
TRON supports USDT. Ethereum, BNB Smart Chain, Polygon, Solana and Base support the configured versions of USDT / USDC. Availability depends on enabled channels and merchant wallets; use the checkout and API response as the source of truth.
Do not fulfill from screenshots or browser returns. Check the order and payment record; qualifying payment differences can enter manual review. Accepting an association and quick processing require active membership. Keep processed orders idempotent to prevent duplicate grants.
Create payment orders, check on-chain transfers and notify your system after confirmation.