WeChat and Alipay collection limits: amount checks, payment attempts and old-order reconciliation
A top-up that worked yesterday may be rejected today for amount conditions; that alone does not prove a lost payment. Distinguish pre-creation rejection, an initiated request with an unknown outcome, and an actual paid order. WenFuPay aggregates WeChat, Alipay and UnionPay collection, but limits depend on the channels opened for the merchant. This guide promises neither a universal maximum nor a CNY10 minimum for every case.
Continue by topic
Confirm channel conditions before creation
Confirm method, merchant scope, currency, amount units, upper and lower boundaries and effective time. Check product amounts against those conditions. Display and server validation should use the same confirmed rule set; changing only the browser leaves the backend submitting old amounts.
A customer payment minimum, merchant prefunding and minimum settlement requirements are different concepts. Published ranges need scope and update time; fees cannot be inferred from limits. Ask the technical team when conditions change rather than guessing a complete range from one error.
Resolve unknown earlier attempts first
Separate a definite rejection without a valid payment from a timed-out attempt whose outcome is unknown. Query or escalate the latter using its original reference and the agreed procedure. A retry prompt is not a reason to create another payment immediately.
Example: the first request for TOP-A times out, then a limit message appears. Check whether the first attempt was accepted. Retain channel, order references and results per attempt. Never alter the original amount while retaining its old signature or payment reference.
Obtain clear consent for a changed purchase
If the product is outside current channel scope, the merchant and integration team can assess another applicable, approved option or explain that purchase is unavailable. Changes to amount, quantity or entitlements need a clear new purchase snapshot; do not silently replace it with lesser benefits.
Do not automatically split payments to bypass confirmed limits. If the business genuinely permits separate purchases, each needs its own real order, delivery and after-sales basis. Their sum cannot simply declare the original order paid. Preserve and handle any already verified receipt separately.
Accept the integration with boundary cases
Within authorized testing, cover inside-boundary amounts, boundary values, out-of-range values, wrong units, changed rules and request timeouts. Verify rejection, unknown outcomes and one-time delivery after success separately. Testing need not attempt to bypass real channel limits.
Tell WenFuPay the product, common amount ranges, payment environment and callback needs. Confirm available channels and test formal documentation. The platform assists channel and notice integration; the merchant manages products and balances. Merchant USDT settlement of CNY collections currently uses TRC20 only; direct-wallet monitoring is a separate service.
Frequently asked questions
Should an over-limit payment be split automatically?
Do not split to bypass channel restrictions. Confirm an applicable legitimate option. Independent genuine purchases still need separate payment, delivery and after-sales records.
Does one limit error prove an earlier payment did not charge?
No. Separate the current rejection from any earlier unknown attempt and reconcile each original reference to avoid duplicate payment or an omitted receipt.