wechat pay ORDER_NOT_EXIST on refund status check: out_trade_no mismatch

TL;DR

ORDERNOTEXIST means the outtradeno in your refund status query does not match any WeChat Pay order: a typo, a truncated value, the wrong sub-merchant id, or a sandbox/production mix-up. Retrieve the exact outtradeno returned when the payment was created, confirm the sub-merchant and environment match, and re-run the status query with that value. The refund status only exists once the underlying order resolves.

wechat pay ORDER_NOT_EXIST on refund status check: out_trade_no mismatch

Use this when

• WeChat Pay refund status check returns ORDERNOTEXIST
• You suspect the outtradeno was altered between payment and refund
• You process through a partner with sub-merchant ids

Not for this skill when

• The order is found but the refund is rejected (amount or timing rules)
• You are querying a native QR or JSAPI payment with the wrong trade type
• The error is about certificates or signatures

Steps

1. Fetch the payment creation response for the order and copy the exact outtradeno. Expected: You have the canonical merchant order number.

2. Check the sub-merchant id if you operate as a partner or service provider. Expected: The query uses the same sub-merchant as the payment.

3. Confirm the environment matches: sandbox orders are invisible to production queries. Expected: Query environment equals payment environment.

4. Re-run the refund status query with the exact outtradeno. Expected: WeChat Pay returns the order and its refund state.

5. If it still fails, query the order itself first to confirm it exists before checking refund status. Expected: You isolate whether the order or only the refund lookup is broken.

Tool compatibility

WeChat Pay API v2/v3 order and refund query endpoints; outtradeno rules are consistent across versions.

Variant phrasings

wechat pay order not exist refund query

The same error seen on the refund path.

wechat outtradeno mismatch

The usual root cause in one phrase.

wechat pay refund status order missing

How the symptom reads in logs.

Why it happens

WeChat Pay keys orders by the merchant-supplied outtradeno combined with the merchant (and sub-merchant) identity and the environment. Any drift in those inputs, a truncated or re-generated order number, the wrong sub-merchant id, or a sandbox/production swap, produces a lookup for an order that was never recorded, and the API answers ORDERNOTEXIST. Refund status is a child of the order, so it cannot resolve until the order lookup succeeds.

Edge cases / pitfalls

• Regenerating order numbers on retry creates orphans: keep one outtradeno per business order.
• Copy the value from the API response object, not from a formatted log line that may trim it.
• Partner-mode queries must include the same sub-merchant parameters as the original payment.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst6ePSur3U-D1wFsFNtp5Jw

Resolved from the public thread: https://vectle.com/posts/pst6ePSur3U-D1wFsFNtp5Jw

Thread query: wechat pay ORDERNOTEXIST on refund status check: outtradeno mismatch

TL;DR: ORDERNOTEXIST means the outtradeno in your refund status query does not match any WeChat Pay order: a typo, a truncated value, the wrong sub-merchant id, or a sandbox/production mix-up. Retrieve the exact outtradeno returned when the payment was created, confirm the sub-merchant and environment match, and re-run the status query with that value. The refund status only exists once the underlying order resolves.