BEP20-USDC
BNB Smart ChainBest for member top-ups, game credits, long-term dedicated addresses, and the default USDC collection route.
Website order payments · Ongoing member top-ups
Connect website payments and member top-ups
Create USDC payment orders and verify deposit webhooks to connect website payments and member top-ups.
Collections: subscription only. Payouts: network fees only.
No percentage collection fee or added payout service fee. Sweeps incur the applicable network fee.

After the merchant configures the relevant wallets, each route can be enabled for collection and payout.
Best for member top-ups, game credits, long-term dedicated addresses, and the default USDC collection route.
Covers more wallet users and SOL ecosystem needs as a complement to BSC.
Match the address, asset and network. USDC supports BEP20 and SPL; do not transfer on other networks.
Create an order via API to receive the payment address and amount.
Detect payment and confirm it on the corresponding network.
Notify your business system to continue processing.
Create a payment order to get an address and amount. Confirm your website order through the webhook after the customer's USDC payment.
Wait for on-chain confirmation and verify the webhook before processing the order.
Read the order payment guideBind a dedicated address to each member for USDC top-ups. UUGate recognizes deposits and sends webhooks; your application credits the member balance.
Bind a long-term address on the selected network to a member or business object.
The member deposits the specified asset on the correct network.
Reconcile the webhook and deposit record, processing repeated notifications once.
Use standard APIs, long-term addresses, or imported wallet monitoring depending on your current system.
Use collection order creation, payout order creation, status query, and callback signature verification.
View API docsWooCommerce · Easy Digital Downloads · WHMCS
Plugin installation guideBind each member or business object to a long-term USDC address for continuous deposit recognition.
Learn about dedicated addressesPHP · Laravel / Node.js · Developer tools
This request body creates a fixed-amount collection order. This page does not send a request.
/openapi/payin/ordersRequests also require the merchant UID, API Key, timestamp, nonce, and HMAC-SHA256 signature. Sign on your server and keep the API Key out of browser code.
Use the returned orderNo to query the order, address for payment, and cashierUrl to open checkout. Check status and verified callbacks to confirm the business outcome.
View full API parameters and signed examples{
"chainCode": "BSC",
"tokenSymbol": "USDC",
"merchantOrderNo": "ORDER_EXAMPLE_001",
"amount": "10.00",
"notifyUrl": "https://merchant.example.com/payments/notify"
}| Service | Billing basis | Fee details |
|---|---|---|
| Collections (orders / member top-ups) | Plan subscription | USDC collections are covered by your selected plan, without a percentage or per-collection service fee. |
| Payouts (API transfers) | Charged by network | USDC payouts are billed by network and actual payout count, with no added platform service fee. |
| Fund sweeps | Applicable network fee | No percentage collection fee or added payout service fee. Sweeps incur the applicable network fee. |
The UUGate USDC payment platform creates orders through collection APIs. Its payment gateway recognizes on-chain deposits and sends merchant webhooks. Your system verifies signatures and reconciles orders before crediting or fulfillment; custody wallets, dedicated addresses, payouts and sweeps are managed in one console.
Create orders, query status, and receive callbacks for orders, balance top-ups, and automatic crediting.
Continue into withdrawals, commission settlement, agent rebates, and supplier payouts.
Bind long-term addresses to members, users, or business objects to reduce manual reconciliation.
Connect deposit notifications, fund organization, on-chain network cost, and payer address alerts.
After the merchant configures the relevant wallets, each route can be enabled for collection and payout.
Best for member top-ups, game credits, long-term dedicated addresses, and the default USDC collection route.
Covers more wallet users and SOL ecosystem needs as a complement to BSC.
A route is shown in production only after the merchant has configured the corresponding wallet.
Use standard APIs, long-term addresses, or imported wallet monitoring depending on your current system.
Use collection order creation, payout order creation, status query, and callback signature verification.
View API docsBind each member or business object to a long-term USDC address for continuous deposit recognition.
Learn about dedicated addressesKeep ownership of existing wallets while adding monitoring, recognition, and callbacks.
View wallet integrationThe goal is not only receiving one transfer, but making recognition, notification, sweep, and payout operational.
Identify USDC deposits by order, custody wallet, or dedicated address.
Notify the merchant system after settlement to credit, ship, or update orders.
Sweep funds to designated wallets by policy and reduce scattered address management.
Withdrawals, commission settlement, and supplier payments continue through the API.
USDC is usually the best primary route when the business needs long-term addresses, frequent deposit recognition, and downstream payouts.
Bind addresses to members and credit balances automatically after deposits.
Suitable for frequent small deposits, automatic delivery, and instant activation.
Collection, sweep, and payout can run continuously in one system.
Operate collections, rebates, and batch payouts on the same platform.
BNB Smart Chain (BEP20-USDC) · Solana (SPL-USDC). The payer must use the network specified by the order. The same token on a different network is not the same payment.
Create a collection order with your merchant UID and API Key. Show its address, network, and amount. Verify the callback signature on your server and process each order idempotently before granting access or shipping.
Read API parameters and callback verificationMonthly plans, address quotas, and payout or sweep network fees are separate items. Choose a plan for your address needs and check the selected network's fee before submitting. Network fees follow the platform's current configuration.
Compare current plans and network feesCheck order status, token, network, amount, and transaction hash, then inspect callback delivery and signature verification. Credit repeated notifications only once. A browser redirect or payment screenshot does not confirm payment.
Troubleshoot callbacks and duplicate creditsThis request body creates a fixed-amount collection order. This page does not send a request.
POST https://api.uugate.com/openapi/payin/orders
{
"chainCode": "BSC",
"tokenSymbol": "USDC",
"merchantOrderNo": "ORDER_EXAMPLE_001",
"amount": "10.00",
"notifyUrl": "https://merchant.example.com/payments/notify"
}
Requests also require the merchant UID, API Key, timestamp, nonce, and HMAC-SHA256 signature. Sign on your server and keep the API Key out of browser code.
Use the returned orderNo to query the order, address for payment, and cashierUrl to open checkout. Check status and verified callbacks to confirm the business outcome.
View full API parameters and signed examplesFollow a 10.00 USDC digital-service order. This is an illustrative design, not a customer case. This page sends no requests or payments.
Create a fixed-amount order on your server. Store merchantOrderNo and platform orderNo, then open the returned cashierUrl. A checkout link means creation succeeded.
Show the order network, address, and amount. Wait for chain confirmation; the same token on another network does not pay this order.
Verify rawBody with the original order API Key. Validate identity, amount, and completed status; use a transaction and uniqueness constraint to record once.
After reliably saving payment, grant access once. Duplicate callbacks do not fulfill again. Query the original orderNo if a callback is missing; do not change references to create again.
Order parameters · Callback verification · Integration example and checks · Node.js SDK · PHP / Laravel SDK
UUGate maintains its product and integration documentation. Current API documentation defines parameters, support, and statuses. Contact official support for technical questions. The sources below explain standards and do not imply endorsement of UUGate.
Solana · SPL Tokens · Node.js · HMAC · Contact UUGate technical support
Dedicated address binding is usually better: the address stays stable and deposits are recognized automatically.
Imported wallet monitoring can connect existing wallets without changing ownership while adding recognition and callbacks.
BSC-USDC and SOL-USDC are the current focus, with BSC-USDC as the default recommended route.
Yes. Withdrawals, commission settlement, rebates, and supplier payouts can continue through the USDC payout API.
At UUGate, payment APIs expose order creation and queries; the payment gateway connects orders, on-chain recognition and webhooks. The payment platform also provides the merchant console, custody wallets, dedicated addresses, payouts, sweeps and fee management. Evaluate the workflow and responsibilities behind these terms.
Prepare a merchant UID and API Key, a wallet on the supported network, merchant order references and a public HTTPS webhook endpoint. Keep credentials on the backend, verify webhook signatures and reconcile orders, amounts and networks. Process repeated notifications once and investigate a timeout before retrying creation.
Check payer assets and networks, dedicated address binding, webhooks, duplicate handling, sweeps and transaction exports. Calculate plan charges, address allowance and network fees separately. Verify that a top-up credits once and that callback failures can be recovered.
Begin with test wallets, callback testing, and route configuration before moving collection and payout to production.