Verifying a native WeChat payment: screenshots, merchant references and query results

When a customer supplies a successful-payment screenshot but no website credit appears, support needs traceable order evidence. A screenshot is not a trusted callback. Website purchases, payment attempts and identifiers on a WeChat receipt may belong to different systems.

Continue by topic

Recover the original purchase in your own application

Ask the authenticated customer to select their order and reconcile product, amount snapshot, creation time and current processing state. Enforce order-viewing rights across devices or changed contact details. Do not attach an arbitrary screenshot to an order with a matching amount.

Collect only relevant time, amount and traceable references, redacting unrelated transactions, names and wallet balances. Website payment verification does not require the customer’s password or SMS verification code.

Map three layers of identifiers deliberately

The internal purchase identifies what was bought; the merchant attempt identifies the submitted collection request; the channel or receipt reference traces the corresponding payment. Confirm the real field mapping during integration instead of guessing from reference length or suffix.

For example, receipt R should map through authorized stored evidence to attempt A and then purchase P. If the relationship is missing, keep it under review and escalate rather than placing R into an arbitrary order field.

Use trusted notifications and authorized queries

Verify notifications under the actual 稳付pay collection protocol and check merchant, original order, currency, amount and confirmed state. Use the agreed query process when a notification is absent or inconclusive. Official WeChat guidance provides general notification/query principles, not interchangeable aggregator fields or acknowledgements.

A successful screenshot alongside an unknown query is a discrepancy for technical review. Show reconciliation progress; do not credit first and seek evidence later, or repeatedly ask the customer to pay again while the outcome is unknown.

Continue from payment verification to fulfillment

If payment is confirmed but credit is missing, inspect the unique credit entry, customer mapping and entitlement task instead of creating another collection order. Repeat notifications read existing processing; multiple real payments retain separate evidence.

A handover record should connect purchase, attempt, evidence source, query time, confirmation decision and delivery result. Test mismatched screenshots, several equal-value orders, delayed notifications, query-first results and confirmed payments with failed fulfillment.

Frequently asked questions

Can support credit a balance from a success screenshot?

Not from the image alone. Map it to the original order and obtain a trusted notification, authorized query result or technical confirmation.

Does a different receipt reference mean the customer paid the wrong order?

Not necessarily. The references may identify different layers; reconcile their stored relationship instead of comparing their appearance.

References