Both WeChat and Alipay succeeded after switching: attempts, duplicate payments and entitlements

A user opens a WeChat checkout, switches to Alipay, and both channels later report success. This differs from receiving the same callback twice: there may be two genuine receipts for one intended purchase. Preserve both payment facts before deciding which satisfies the purchase and how to handle the other. These are merchant-side design suggestions, not a promise of automatic merging or refund APIs from WenFuPay.

Continue by topic

Separate purchases, payment attempts and receipts

A purchase records the user, product and agreed amount. Each attempt records its channel, merchant order number and payment reference. A verified result proves an actual receipt. Link these records without overwriting them with one “last order number”.

Before enabling switching, confirm with the technical team whether the old order can still be paid, can be closed, and how its notifications are matched. Hiding its QR code or closing the browser does not prove expiry. Do not replace a WeChat reference with an Alipay reference to reuse one record.

Keep both successes; allocate only the intended delivery

Example: purchase SUB-A buys one membership, while WeChat attempt W and Alipay attempt A are independently confirmed. Validate signatures and match merchant, original order, amount and currency under the actual protocol, then retain receipt evidence for W and A separately. Equal amounts do not prove a repeated notification.

If the purchase covers one entitlement, allocate delivery once and place the other payment in an additional-payment review. Unique constraints can protect local allocations. They cannot undo a second payment or establish the correct refund amount.

Give the extra payment its own after-sales record

Confirm the customer’s intent and whether both receipts completed, whether either was fulfilled elsewhere, and whether an after-sales action is already in progress. A genuinely intended second purchase needs explicit confirmation and an association under the product rules; equal amounts alone must not extend a membership.

For refunds or adjustments, confirm available methods, costs and completion evidence with the channel and technical team. Distinguish requests, approvals, execution and completion. Query an unknown original operation before resubmitting. Merchant USDT settlement proceeds are not a substitute for the customer’s original payment amount when calculating after-sales handling.

Test the complete switching race before launch

Use your own simulated records for old-channel-first, new-channel-first, concurrent notices, query timeouts and a second payment confirmed after delivery. Explain both receipts, the one purchased entitlement and the extra payment’s handling status in every case.

For WenFuPay integration, describe the website or app, payment environment, switching entry and callback rules, then use the formal documentation after account setup. Channel access and order notifications assist integration; the merchant still owns its product and entitlement ledgers. USDT settlement of CNY collections currently uses TRC20 only; direct monitoring of a merchant-owned wallet is a separate service.

Frequently asked questions

Can the second success be ignored as a duplicate callback?

Not without checking the payment reference. A repeated notice for one payment differs from two genuine payments. The latter requires receipt and after-sales records.

Does disabling the button prevent two payments?

No. Old pages, existing checkouts and network delays can still produce results. Server-side attempt associations, delivery deduplication and additional-payment review remain necessary.

References