Alipay callbacks cached by a CDN: origin evidence, response isolation and old-order review
When a callback receives a successful response but the application has no receipt, inspect CDN or reverse-proxy reuse as well as routing. Using Alipay collection notifications, this guide examines an edge response without origin delivery. HTTP status alone proves neither payment nor customer credit.
Continue by topic
Define onboarding, charges and funds flow
稳付pay publicly lists WeChat Pay, Alipay and UnionPay; enabled channels and notification behavior follow formal configuration. Complete account setup for an eligible business and confirm protocol, domain and receiver requirements. Keep parameters and keys on the server. Confirm rates, payment limits, CDN subscription costs and log-retention costs separately. An expensive cache plan cannot guarantee payment success.
Merchant USDT settlement of CNY collections currently uses TRON/TRC20 only. Confirm net amounts, triggers and timing with the team. Payment success, customer credit or delivery, and merchant settlement are separate outcomes. Fixing a cache does not automatically deliver entitlements or complete settlement, and does not open an automated payout service.
Prove origin arrival with one request chain
In an isolated merchant environment, send a simulated request with a unique correlation identifier. Compare edge, proxy, application receipt and business processing records. Retain only necessary summaries and times, without disclosing signatures or customer data. Response content and cache indicators need corroborating origin evidence; one header does not establish the sole cause.
Example: notification A reaches the application; B receives the same response without its own origin record. A cache key omitting distinguishing parameters could reuse A, but verify configuration and logs. Browser return pages, customer order queries and notification acknowledgments are separate resources and need separate policies.
Limit caching while preserving authentication and one-time credit
Explicitly exclude the real callback route from caching and synthetic edge success responses. Use an appropriate origin Cache-Control: no-store response and verify actual proxy/CDN behavior. no-cache requires validation before reuse and differs from no storage. Updating future responses does not establish removal of old copies; handle existing objects through the cache system.
Still verify the formal signature and original merchant, order, amount and currency before persistence. Protect event processing and business credit against duplicates. Return the contracted acknowledgment only after its processing requirements are met, rather than a fixed 200. Private order queries also need authorization: disabling caching does not authorize cross-account access. Public guides and images can retain their own cache policies.
Reconcile affected orders and test isolation
List orders with an edge response but no application receipt, receipt without credit, or payment without delivery during the affected window. Query original references through authorized procedures or arrange team review, using the same idempotent processor. Do not mark every access-log entry paid or ask customers to pay again.
Simulate different orders A and B, duplicate A, forged notices, application downtime and unauthorized customer queries. Compare origin records and single delivery. Verify no callback-response reuse or private-result mixing while static resources remain available. RFC9111 explains HTTP semantics; public signature and callback guides explain the workflow, while formal materials govern actual fields and acknowledgments.
Frequently asked questions
Does adding no-store remove an already cached acknowledgment?
Not necessarily. Handle existing objects through the actual CDN or proxy and verify that new requests reach the origin.
Does callback HTTP 200 mean customer credit is available?
No. Verify trusted payment, durable receipt and one business credit. An edge response cannot replace that evidence.