Settlement in practice

The complete merchant settlement workflow: from successful payment to USDT receipt and reconciliation

After a customer pays, which records should the merchant check, who confirms the amount and how can USDT receipt be verified? Following one channel order, this article turns preparation, order checks, conversion, transfer and reconciliation into actionable checks. 稳付pay provides Alipay, WeChat Pay and aggregate channels, with real-time USDT settlement under the parties' agreement. Confirm the specific conditions and procedure during onboarding.

Preparing to integrate 稳付pay: see the collection developer documentation and use the actual fields for MD5 signing, order creation, queries and callbacks. Technical staff provide merchant gateways and keys separately; payout APIs are not currently available.
Contents

Step 1: determine whether this business process needs platform settlement

This settlement workflow applies when customers pay through a payment channel and the service provider subsequently settles to the merchant in USDT as agreed. Original customer payments, merchant settlement receivables and final wallet receipts are three record layers that must be reconciled separately.

If customers transfer directly to the merchant's own USDT address, 稳付pay only identifies transactions, verifies confirmation conditions and sends order callbacks. Funds do not pass through the platform, which neither collects nor holds them. This process does not require asking the platform to transfer receipts already in your wallet. Tron (TRC20) and Ethereum (ERC20) are currently supported; other networks require separate development and integration confirmation.

Step 2: prepare an onboarding confirmation sheet both parties can review

Document the website, products, fulfillment method, reconciliation contact and callback URL, then confirm available channels. Separately list the settlement network, USDT asset, receiving address, receiving tool and address-change review process. Receiving funds never requires providing wallet private keys or seed phrases to onboarding staff.

Then confirm settlement triggers, per-order or other settlement methods, minimum amounts, quote validity, fee responsibilities and refund rules. Leave unagreed items pending instead of assuming zero fees or no threshold. The merchant dashboard is still in development; currently you can use Contact 稳付pay to confirm submission, settlement query and manual verification procedures rather than assuming a self-service withdrawal button already exists.

Step 3: verify payment success before settlement eligibility

When the order system receives a trusted payment notification, verify the signature under the actual protocol, check the order number, merchant identity, amount, currency and payment state, and save the result. Customer screenshots, browser return pages and a simple request-success message do not replace server-side payment records.

After payment succeeds, check whether the funds meet the agreed settlement conditions. Clearly identify the reasons for items under refund processing, amount disputes or pending verification. Being able to deliver a product does not mean settlement has reached the wallet. Likewise, pending settlement confirmation must not turn an already successful customer payment into a failed one.

  1. Confirm customer paymentCheck the trusted payment result and business order
  2. Determine the settlement-eligible amountList orders, fees and pending items
  3. Confirm the settlement statementCheck conversion, network, address and quantity
  4. Track the USDT transferRetain the transaction identifier and verify execution and confirmations
  5. Complete dual-currency reconciliationAssociate original-currency receivables with actual USDT receipts
Each step needs a record and responsible person. Specific triggers and query methods follow the onboarding agreement.

Step 4: confirm the statement and retain fields needed to recalculate it

Even when using a mutually agreed spreadsheet temporarily, every number should have a source. Keep details when one settlement covers multiple orders, and track the current settlement and remainder when a receivable is settled in installments. These are suggested accounting fields, not published 稳付pay API parameters.

Field groupSuggested recordsVerification purpose
AssociationsSettlement reference, order list and payment referencesTrace a total back to each business transaction
Original-currency amountsValid receipts, refunds, fees and explicit adjustmentsRecalculate the amount eligible for this settlement
Conversion rulesQuote direction, validity time, precision and rounding methodExplain the source of the USDT quantity
Receiving informationNetwork, asset, complete address and confirmed versionPrevent transfers to an old address or wrong network
Transfer resultsPayable quantity, actual received quantity, transaction identifier and confirmation timeReconcile transferred and received amounts
Exception recordsReason, responsible person and next review timeKeep unfinished items continuously traceable

Step 5: use a hypothetical statement to demonstrate fees and conversion

Example 1: the following figures illustrate calculation only and are not a 稳付pay quote. A batch has 1,000 yuan of valid receipts and 100 yuan of confirmed refunds. Suppose the agreed channel service fee is 1% of the remaining 900 yuan: the fee is 9 yuan and the amount available for conversion is 891 yuan.

Suppose the confirmed quote is 7.20 yuan per USDT: 891 ÷ 7.20 = 123.75 USDT. If a separately agreed 1 USDT transfer fee is deducted from that amount, the merchant receives 122.75 USDT. If the sender pays that fee separately, the merchant still receives 123.75 USDT. Establish where fees are deducted before calculating to avoid duplicate deductions.

Actual fee bases, conversion timing, quote direction and refund fees may differ; recalculate each according to the settlement statement. Maintain separate currency ledgers: do not subtract 122.75 USDT directly from 891 yuan or treat USDT as a fixed equivalent of yuan or another currency. Free monitoring for webmasters does not make all collection and settlement steps free.

Step 6: check transfer evidence and distinguish broadcast from receipt

After obtaining the transaction identifier, verify the asset, receiving address, actual transferred quantity and execution result on the correct network, then confirm receipt under the agreed confirmation rules. USDT transfers are token transfers; an entry on a transaction page or the native-coin transfer amount alone is insufficient.

Official TRON documentation distinguishes the broadcast response, transaction, execution receipt and solidification state. A successful broadcast response is not final receipt. Ethereum transaction documentation also distinguishes submission from subsequent processing. Congestion, nodes and receiving tools' crediting rules affect observation time; real-time settlement does not mean final on-chain confirmation always involves zero waiting.

Step 7: maintain separate order, settlement and transfer states

Record the order payment result, settlement progress and on-chain transfer result separately. Repeated payment notifications update the same payment. After a settlement query timeout, retain the original reference and continue verifying rather than creating another payable amount.

Internal states could be awaiting assessment, awaiting confirmation, processing, awaiting on-chain confirmation, completed and manual review required. These are management suggestions in this article, not existing 稳付pay status codes. Record the evidence, timestamp and operator behind each change. Seconds-scale callbacks describe notifications after configured transaction confirmation conditions are met; they do not combine settlement requests, broadcast and final receipt into one state.

Step 8: handle refunds and timeouts through original records to avoid duplicate payments

Scenario two: Settlement S-001 has been initiated, its query has not returned yet and a refund request arrives for an original order. First preserve S-001's associated orders, amount and address and ask onboarding staff to check the original result. If a transaction identifier is known, continue verifying it. An unknown result is not a failure and does not justify requesting another transfer of the same USDT amount.

If the original settlement completed, a refund requires separately agreed funding, currency, conversion and fees while retaining links to the original order and settlement. An on-chain transfer is not automatically reversed when the merchant marks an order as refunding. If settlement has not been sent, confirm whether its amount can be changed; never silently overwrite a statement already confirmed by both parties.

For a wrong address, amount mismatch, failed transaction or delayed crediting by a receiving tool, submit the same evidence set: settlement reference, network, address, quantity, transaction identifier and time. Hide unrelated customer data in public screenshots. These details do not enable someone to recover a wallet private key.

Step 9: reconcile two ledgers daily and retain a list of differences

The original-currency ledger reconciles opening unsettled receivables, valid income, refunds, fees, settlement deductions and closing unsettled receivables. The USDT ledger reconciles payable quantities, separately paid or deducted fees, transfer results and actual receipts. Conversion details and settlement references connect the ledgers; use consistent time zones and date attribution rules.

To prevent settling the same receivable portion twice, record the amount allocated to each settlement reference and track processing amounts separately. Partial settlements may allocate only the remainder that is neither settled nor already reserved. Release a reservation only after confirming settlement was not sent and can be released. Releasing processing amounts to the next batch merely because a query times out risks duplicate settlement.

When one transfer covers multiple orders, retain more than the transfer total. Stripe's payout reconciliation documentation illustrates connecting payouts to underlying transactions. This article adopts only that traceability principle, not Stripe's product APIs. List amounts awaiting on-chain confirmation, refunds or manual review separately rather than deleting records or inventing entries to force the ledgers to balance.

Pre-launch acceptance: explain every amount and recover from an exception

  • Both parties confirm current channels, the settlement network, receiving address and address-change process.
  • A normal order links to its payment record, settlement statement and USDT transfer record.
  • Quotes, fees, precision and rounding rules are clear enough for the merchant to recalculate independently.
  • Duplicate notifications and query timeouts do not cause duplicate accounting, fulfillment or settlement.
  • Refunds, partial settlements and unknown results have responsible contacts and follow-up checks.
  • On-chain execution and confirmation conditions are clear, and actual wallet receipts match the settlement statement.

After completing small-value integration tests, gradually introduce real business within the agreed scope. Preparing confirmation sheets, reconciliation fields and exception contacts gives real-time settlement verifiable completion criteria rather than only a promise of receipt.

References and technical documentation

Official references help verify general technical principles. Validate examples against the actual API documentation and runtime environment.

  1. Stripe: reconciling payouts with underlying transactions
  2. TRON: distinguishing broadcast, execution and solidified confirmation
  3. Ethereum: transaction submission and subsequent processing

Confirm integration for your business scenario

Describe your products, order volume, payment methods and settlement needs to confirm the APIs, movement of funds and exception handling item by item.

Contact 稳付pay ↗