Payment fundamentals

How do transaction processing, payment collection and disbursement differ? Orders, funds flow and reconciliation

A customer's payment, the merchant receiving settlement and a beneficiary receiving a disbursement are three different outcomes. Map orders, funds flows and accounting records individually to explain why each amount was collected, where it went and who should investigate a discrepancy.

A quick introduction to collection and payouts

Collection means users pay the site. Payout means the site sends money to users or partners. These opposite directions require different order states, callbacks and failure handling.

Collection checks whether the user paid successfully

Resource, video and novel sites collect payment when selling memberships or individual content. The system creates a collection order; users pay through Alipay or WeChat, and your endpoint fulfills it after a success notification. Verify the merchant order ID, amount and payment status. Repeated notifications must trigger fulfillment only once.

Closing a payment page proves neither failure nor success. Actively query expired orders rather than relying on redirects.

Payout checks whether funds were sent

Payout handles outgoing payments, such as occasional settlements or payments other than balance refunds. It is not another membership collection. Each payout order needs a unique ID, recipient account and amount. Use the payout receipt to determine success, processing or failure. Investigate failures; do not blindly resend with the same ID and risk paying twice.

Why keep them in separate orders?

  • Collection success permits fulfillment; payout success confirms funds were sent. These two success states mean different things.
  • Callback fields differ. Using collection callbacks to update payout status breaks reconciliation.
  • For low volumes, keep payouts separate from the main collection channel to avoid interference during peaks.
  • Export reconciliation records separately by merchant order ID, rather than looking only at daily totals.

When does a site need payouts?

A content-only site that grants access after payment should first stabilize collection through native Alipay, native WeChat or personal QR. When outgoing payment orders appear, assess payout channels, limits and arrival times separately. Fees, available accounts and activation depend on the actual configuration confirmed in consultation.

Test one small real collection and one payout. Verify order IDs, amounts and receipts in your records before using them in production.
Contents

1. “Transaction processing” is informal: ask what the business actually does

The informal Chinese term often translated as “transaction processing” is not a standardized payment product. It may refer to collection, settlement, paying a partner or simply booking a transaction. During integration discussions, break it into actions tied to real goods or service orders: who pays whom, the underlying business, who ultimately receives funds and which records the system retains.

For example, a customer buys a website service, the site fulfills after receiving payment confirmation, the channel settles with the site, and the site pays its supplier. Collection, settlement and supplier payment are three business relationships. “Process it for me” cannot replace order evidence and each party's responsibilities.

The BIS CPMI glossary separately explains payment instructions, clearing and settlement. This article describes common business workflows for site owners; informal labels are not formal rules shared by every channel.

2. Collection, settlement and disbursement: direction and business purpose

ActionDirection of funds or instructionResult to verify
Payment collectionA customer pays through an agreed payment channelWhich order was paid and how much was received
SettlementAmounts due are transferred to the merchant as agreedSettlement currency, amount and receipt evidence
DisbursementThe merchant instructs a payment to a specified beneficiaryWhether the separate payout order completed
RefundThe corresponding amount is returned under the original transaction termsThe refund's relationship to the original payment
Accounting recordsThe system records these business changesWhether the ledger agrees with external funds evidence

Treating disbursement as collection's automatic second half causes mistakes. Customer payment only proves collection completed. Paying a supplier or another beneficiary needs separate authorization, funding and execution results. Likewise, an administration screen's balance does not mean funds are already in the merchant's wallet.

3. Keep the funds paths of the two USDT models distinct

稳付pay provides payment channels and can arrange real-time USDT settlement for collection under the integration agreement. Customers first pay through the channel, then the agreed amount due is settled to the merchant in USDT. Check collection records, settlement amounts, receiving network and address, and final evidence. This is not a model in which customer funds bypass both channel and platform entirely.

The other model is 稳付pay on-chain collection monitoring. Customers send USDT directly to the merchant's own wallet; 稳付pay identifies transactions, waits for agreed confirmation conditions and sends callbacks without receiving or holding funds. There is no platform collection followed by merchant settlement in this model.

Both models may involve USDT. The difference is who first receives customer funds and whether a later settlement obligation exists. Use consistent model names across integration pages, agreements, checkout and reconciliation. Identical final assets do not create identical responsibilities.

4. Link five separately numbered document types for clear investigation

The business order ID identifies the purchase; a payment ID identifies an attempt; a settlement ID covers one or several amounts due; a disbursement ID identifies an independently instructed payout; a refund ID links to the original payment. An order may have another payment attempt or multiple refunds, and a settlement may aggregate multiple payments. Do not force all of them into one identifier.

Use a relationship table to preserve allocated amounts between payments and settlements, plus the business basis, beneficiary and approval for disbursements. Record request identifiers and external references for calls, connect logs through internal IDs and restrict sensitive account details by role. Support, finance and engineering can then investigate the same underlying event.

Editing notes must not change original document facts. Adjust completed business through linked adjustment records with reasons and operators, rather than overwriting historical amounts.

5. Separate collection callbacks, settlement execution and disbursement callbacks

  1. Create a real business orderFix product, amount, currency and order ID
  2. Obtain the payment resultVerify signatures, check the payment record and persist
  3. Review settlement detailsLink amounts due, fees and settlement records
  4. Track separate payoutsCreate a disbursement document from the merchant instruction
  5. Complete reconciliationVerify collection, settlement and payout evidence separately
This shows common business relationships. Disbursements can occur independently; not every collection must trigger one.

“Request accepted” and “beneficiary received funds” are separate states. Refer to Stripe's Payout object documentation for pending, processing, completed and failed states. This is a general design reference, not the 稳付pay specification. Display payment, settlement and disbursement states separately so one green success label does not conceal unfinished stages.

6. Store amounts, currencies and conversion snapshots together

Store money in integer smallest units configured by currency, not floating-point accumulations. Cross-currency settlement also needs original amount and currency, settlement currency, conversion direction, precision, rounding, fee items and the applied conversion snapshot. A CNY cent is not a USDT smallest unit, and balances in different currencies cannot simply be added.

As a calculation example only, CNY 100 converted at CNY 7.20 per USDT gives approximately 13.888888 USDT before fees. The real settlement amount depends on agreed fees and rounding. These illustrative figures are neither a quote nor a 稳付pay rate commitment.

Record each actual business change separately: collection, fees, settlement, refunds and adjustments. A balance summarizes the ledger; repeatedly editing it does not reconcile discrepancies. Keep event and posting times, reporting-period time zone, source documents and actor identity to explain differences across days.

7. Duplicate requests and blockchain broadcasts are not final results

After a payout timeout, query the original result by business ID, then retry with the same agreed idempotent identity. Do not use a new identifier to pay again. Stripe's idempotent request documentation illustrates identifying retries of one operation. Use the actual protocol for keys, expiry and responses. Verify callback signatures and amounts, deduplicate and persist before acknowledging.

A USDT settlement transaction hash is a trackable reference, not final receipt. Check actual execution, network, token contract, receiving address, amount and agreed confirmation conditions. TRON's official transaction documentation distinguishes broadcast, inclusion and solidification; Ethereum's official API documentation provides receipt and block-state queries. Real-time initiation is not final blockchain confirmation, so do not label a successful broadcast as final receipt.

8. Two discrepancy scenarios: follow the document relationships

Scenario one: the customer paid, but the supplier has not received the disbursement

First verify collection through its payment record. Then check whether a disbursement was created, approved, accepted and completed externally. If the original request timed out, query that payout instead of paying again because collection succeeded. Support should explain collection facts and payout progress separately; a collection callback is not a disbursement receipt.

Scenario two: a month-end collection was settled, then a next-month refund breaks reconciliation

Link the refund to the original payment and inspect its date and settlement batch. Distinguish original amount, prior settlement, subsequent adjustments and fees. For CNY collection settled in USDT, preserve the historical conversion snapshot rather than replacing it with the next month's rate. Follow the agreement for cross-currency refunds and explain differences through separate adjustments, not by deleting and recreating last month's settlement.

9. Daily reconciliation: keep differences in an actionable queue

  • Compare actual order payments with channel details, marking missing, duplicate or mismatched amounts.
  • Check each settlement's source payments, currency, conversion snapshot, fees and receipt evidence.
  • Verify payout authorization, beneficiary, unique business identifier and final execution state.
  • Link cross-period refunds, failed-payment reversals and manual adjustments to original records, retaining timestamps and actors.
  • Assign owners for incomplete, unsupported or conflicting records rather than automatically eliminating differences.

The 稳付pay merchant backend remains under development. Contact us to confirm channels, real-time USDT settlement and integration arrangements rather than treating future backend features as live. Free on-chain monitoring for small and medium site owners is separate from collection, USDT settlement and enterprise pricing. Confirm fees, settlement conditions and available payout capabilities during onboarding.

References and technical documentation

The official sources below support protocol and implementation checks. Code and scenarios illustrate technical concepts; validate your environment and production integration protocol separately.

  1. BIS / CPMI: payment, clearing and settlement glossary
  2. Stripe official: Payout objects and processing states
  3. Stripe official: idempotent requests and safe retries
  4. Stripe official: Webhook signatures and duplicate events
  5. TRON official: transaction lifecycle and solidification
  6. Ethereum official: transaction receipts and block states

Keep improving your site

Check each step of networking, orders and funds notifications against your business scenario. Discuss payment integration and USDT monitoring through the contact page.

Contact 稳付pay ↗