Daily USDT and USDC Reconciliation: Orders, Wallet Balances, and Fees
Daily reconciliation needs more than a total received. An order can be paid before a member is credited, and funds can leave a collection wallet through a payout or sweep. Keep those records separate so differences have an explanation.
Updated September 27, 2026: practical checks for the merchant dashboard and automatic sweeps.
Start with recent transactions
The dashboard merges receipts, payouts, sweeps, and fee top-ups by creation time and shows the latest four records, with timestamps to the second. Use it to locate recent activity, not as a complete daily report. Select a transaction type to open its list and check dates, status, and asset.
The displayed amount is the order amount, not proof of settlement. Pending or expired orders may still show an amount. Confirm the status alongside the on-chain transaction and business credit. A fee top-up funds the separate fee account, not customer-order revenue. A sweep moves funds between addresses and must not be counted again as a new receipt.
Save sweep rules, then check the outcome
In Settings, choose the sweep destination for each network and asset, enter the trigger threshold and schedule interval, and save. The threshold applies to each source wallet’s available balance, not the combined balance of all wallets. The interval sets how often checks run; saving does not guarantee an immediate transfer.
Review the enabled state, next run time, and latest result. Use Sweep Records to verify status, amount, and transaction hash. Do not treat a planned transfer as settled when the threshold is unmet, network fees cannot be covered, or execution fails. Preserve and investigate discrepancies instead of sending a duplicate transfer to make totals match.
Fix the reporting scope
Choose a timezone, interval, and confirmation policy. Separate TRC20-USDT, BEP20-USDT, BEP20-USDC, and SPL-USDC. Do not merge transactions across networks or silently offset USDT against USDC. Retain order creation, transaction, confirmation, and business credit times to explain payments crossing a reporting boundary.
Match orders to transfers
Link the merchant order number to the API order number, then attach the network, asset, address, and transaction hash. If one transaction contains several transfers, distinguish the individual transfer records; a transaction hash alone may not identify a unique deposit.
Prioritize paid API orders without business credits, credits without matching successful orders, and differences in asset, network, or amount. Give each exception an owner, reason, resolution, and review record.
Read wallet balances from the chain
Merchant wallet balances represent the actual assets at on-chain addresses. Wallet ledger entries support tracing and audit; they are not the final authority for the current balance. Payouts, sweeps, and other transfers can change the balance after collection.
Record the network and query time when checking balances through RPC. Mark failed queries for investigation instead of interpreting them as zero. Do not edit business records merely to hide a mismatch.
Reconcile the fee account separately
The system fee account is separate from the collection wallet. Check fee top-ups and deductions independently from wallet movements. A negative fee balance can restrict collection order creation, payouts, sweeps, OpenAPI order creation, and API Key resets even when a wallet holds assets.
Keep an exception workflow
Recover missed callbacks through queries and idempotent processing. Review underpayments, overpayments, wrong-network payments, and late arrivals against order states and chain evidence. Apply permissions and 2FA requirements to sensitive corrective actions instead of directly forcing a successful status.
Retain the reporting interval, totals by network, unresolved differences, and action history. See the dedicated address solution, consult the API documentation for query fields, and confirm fee rules on the pricing page.
USDT underpayments and overpayments: inspect the original order
First identify the collection mode. A fixed-amount order requires checking expected and received amounts, asset, network and status. A dedicated top-up has no preset expected amount and is credited using paidAmount after confirmation; do not apply ordinary underpayment rules blindly. Compare modes in the payment link guide.
Retain the business reference, orderNo, transaction hash and amount difference. Review confirmations and the order result. Do not mark an underpayment successful from a screenshot or assume an overpayment is a duplicate order. Distinguish individual transfer records within a chain transaction.
Keep original evidence for late, wrong-asset or wrong-network receipts. Follow permissions and current 2FA requirements for order recovery or payouts. Do not edit status or recreate orders to hide differences, or promise automatic refunds or cross-chain recovery. See the notification guide before restoring member credits.