Truncated Alipay callback bodies: request limits, receipt evidence and failure isolation
Missing fields can mean edge rejection, a partial application read, or merely abbreviated logs. Identify which occurred before signature verification. Never invent missing parameters to credit a balance.
Continue by topic
Agree the channel and notification contract first
WenFuPay offers Alipay, WeChat and UnionPay collection under the merchant’s actual rates, limits and extra costs. Describe the site and backend before formal onboarding. Confirm the notification format, encoding, accepted sizes, acknowledgments and recovery process; this guide supplies no universal maximum.
USDT settlement of CNY proceeds currently uses TRON/TRC20 only, with agreed costs and conditions. 24/7 service does not reconstruct damaged notices automatically. Keep payment, notification receipt, business credits and settlement separate. Read public collection and callback guides; obtain actual parameters from the team.
Distinguish rejection, short reads and shortened logs
Trace edge, reverse proxy, application server and parser using redacted request references, times and error categories. Nginx client_max_body_size limits the request body; client_body_buffer_size controls its read buffer. They are not interchangeable, and globally disabling limits is not a diagnosis.
A shortened log display does not prove a shortened request. Compare byte counts at the same processing stage; transfer coding, decompression and character decoding can change representations. Keep full notifications, private data and keys out of routine logs. Reproduce with controlled synthetic payloads.
Complete receipt is only the beginning
After a complete read, follow the actual signing contract for raw bytes or normalized fields; do not assume every protocol signs raw bodies. Isolate missing fields, read failures, parse errors and invalid signatures. Do not splice earlier parameters into a convincing successful notification.
Do not fabricate a business-success acknowledgment for damaged, unprocessed data. Follow the real failure contract with technical support and query the original order. Verify merchant, order, amount, currency and trusted success before idempotent credit. An HTTP code alone proves neither payment nor a ledger update.
Apply a bounded repair and reconcile affected orders
Test each proxy, parser and read path in a controlled environment, sizing bounded limits for verified legitimate payloads. Never upload real notices to unknown testing services. Cover inside, at and above the boundary, partial reads, encoding errors and repeated delivery; rejected input must never create credit.
After rollout, inspect receipt evidence and reconcile a bounded incident list. Redelivery, queries and late notices may race, so one payment must produce one delivery. Record the change, reviewer and recovery results. Do not ask customers to pay again as a diagnostic step.
Frequently asked questions
Does a short log prove a truncated callback?
No. Logging may abbreviate output. Compare actual read evidence at the same stage, rather than relying on a screenshot.
Should I remove request-size limits?
No. Locate the failure and use bounded limits based on the actual contract and legitimate payloads, retaining verification and duplicate-credit protection.