USDC Payment API solution

Add BSC-USDC and SOL-USDC as a dual-stablecoin route beside USDT.

How the USDC payment gateway connects collection and order fulfillment

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.

USDC collection API

Create orders, query status, and receive callbacks for orders, balance top-ups, and automatic crediting.

USDC payout API

Continue into withdrawals, commission settlement, agent rebates, and supplier payouts.

Dedicated addresses and custody wallets

Bind long-term addresses to members, users, or business objects to reduce manual reconciliation.

Callbacks, sweeps, and risk

Connect deposit notifications, fund organization, on-chain network cost, and payer address alerts.

USDC routes currently prioritized

After the merchant configures the relevant wallets, each route can be enabled for collection and payout.

Recommended route

BSC-USDC

Best for member top-ups, game credits, long-term dedicated addresses, and the default USDC collection route.

Additional coverage

SOL-USDC

Covers more wallet users and SOL ecosystem needs as a complement to BSC.

Wallet-based

Shown after configuration

A route is shown in production only after the merchant has configured the corresponding wallet.

Choose an integration path by maturity

Use standard APIs, long-term addresses, or imported wallet monitoring depending on your current system.

API

Standard API integration

Use collection order creation, payout order creation, status query, and callback signature verification.

View API docs

Recommended

Dedicated address binding

Bind each member or business object to a long-term USDC address for continuous deposit recognition.

Learn about dedicated addresses

Wallet

Imported wallet monitoring

Keep ownership of existing wallets while adding monitoring, recognition, and callbacks.

View wallet integration

Closed loop from USDC collection to payout

The goal is not only receiving one transfer, but making recognition, notification, sweep, and payout operational.

Deposit recognition

Identify USDC deposits by order, custody wallet, or dedicated address.

Business callback

Notify the merchant system after settlement to credit, ship, or update orders.

Fund sweep

Sweep funds to designated wallets by policy and reduce scattered address management.

Continue payout

Withdrawals, commission settlement, and supplier payments continue through the API.

Businesses that should make USDC the default route

USDC is usually the best primary route when the business needs long-term addresses, frequent deposit recognition, and downstream payouts.

Member balance systems

Bind addresses to members and credit balances automatically after deposits.

Games and digital content

Suitable for frequent small deposits, automatic delivery, and instant activation.

Cross-border and virtual goods

Collection, sweep, and payout can run continuously in one system.

Agent and commission systems

Operate collections, rebates, and batch payouts on the same platform.

USDC solution FAQ

These are the key questions when evaluating USDC as the default stablecoin route.

Which USDC routes are emphasized?

BSC-USDC and SOL-USDC are the current focus, with BSC-USDC as the default recommended route.

Which mode fits member top-ups?

Dedicated address binding is usually better: the address stays stable and deposits are recognized automatically.

What if I already have USDC wallets?

Imported wallet monitoring can connect existing wallets without changing ownership while adding recognition and callbacks.

Are payout and sweep supported?

Yes. Withdrawals, commission settlement, rebates, and supplier payouts can continue through the USDC payout API.

Payment gateway and platform integration questions

How do payment APIs, gateways and platforms differ?

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.

What does a website need to integrate a USDC payment gateway?

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.

How should membership services choose a stablecoin payment platform?

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.

USDC payment gateway and platform selection guide

How to integrate the USDC payment API and understand fees

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.

Connect the USDC payment API

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 verification

Separate plan and network fees

Monthly 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 fees

Payment arrived but the order did not update

Check 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 credits

USDC collection API request example

This 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 examples

USDC payment API example: collection to fulfillment

Follow a 10.00 USDC digital-service order. This is an illustrative design, not a customer case. This page sends no requests or payments.

1. Save order mappings

Create a fixed-amount order on your server. Store merchantOrderNo and platform orderNo, then open the returned cashierUrl. A checkout link means creation succeeded.

2. Pay on the specified network

Show the order network, address, and amount. Wait for chain confirmation; the same token on another network does not pay this order.

3. Verify and record once

Verify rawBody with the original order API Key. Validate identity, amount, and completed status; use a transaction and uniqueness constraint to record once.

4. Fulfill and compensate

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

Technical references and maintenance

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

Start in test mode, then launch production USDC routes

Begin with test wallets, callback testing, and route configuration before moving collection and payout to production.

Create free account View API docs