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.
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 gateway 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 gateway 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.