Recalling a faulty card-key batch: affected items, replacement eligibility and settlement evidence

A quality incident in one batch of license keys does not justify redistributing every historical purchase or assuming that delisting the product solves the issue. For owned or authorized goods, establish the affected batch and review notification, replacement and after-sales responsibility per item. 稳付pay provides the agreed payment service; this guide does not claim a key-revocation or automatic-recall API.

Continue by topic

Confirm product responsibility and payment terms

Public payment methods include WeChat Pay, Alipay and UnionPay, subject to actual business approval and configuration. Explain authorization, delivery and after-sales rules before onboarding. Confirm rates, amount limits, extra after-sales costs and timing rather than promising acceptance of every key product. Keep formal merchant parameters and keys private. The product owner confirms the defect, revocability, alternatives and customer notice; payment success does not establish product validity.

Merchant USDT settlement after CNY collection currently uses TRON/TRC20 only, with agreed conditions, charges and timing. Payment, key delivery and merchant settlement need separate evidence. A recall does not automatically reverse payments or recover settled USDT. Confirm refunds and settlement adjustments separately; an automatic payout API is not available.

Isolate saleable stock and version the impact list

Create an internal recall reference with supplier, batch, product version, evidence and reviewer. Pause new allocations from that batch. Separate unsold stock, reserved but undelivered items, exposed keys and redeemed keys. Unknown batch mapping remains under review rather than being declared unaffected. A batch identifier is not the full secret; never include complete keys in routine logs or notices.

Illustration: batch B contains100 items, with70 unsold,20 delivered and10 unresolved. Isolate the70 and investigate the other30; do not compensate all100. Version and timestamp the impact list. Append differences when delayed delivery records appear, retaining earlier versions so previously contacted customers are not forgotten. These counts illustrate stock, not a service offer.

Decide per item rather than assuming mass revocation

Link each item to its purchase, verified payment, delivery evidence and redemption outcome. When payment needs investigation, use the formal signature and query protocol; repeated notifications still produce one original delivery. A recall must not fabricate another payment or replay callbacks to distribute extra keys.

For a confirmed replacement, assign unique responsibility using the recall reference and stable item identity. Reuse the existing replacement chain and verify whether the old key can actually be revoked. A remote timeout is unknown, not successful revocation; without that capability, do not promise invalidation. Check prior compensation and after-sales cases before a batch job acts. Stock isolation, issuer-confirmed invalidation and customer receipt of a replacement remain separate evidence.

Close only when each affected item is explained

Use authorized customer channels to explain the item, current status, minimal evidence and follow-up. Do not request passwords or seed phrases or publish customer lists. This publishing task sends no such messages. Failed notification remains pending contact, not customer acceptance. Record consent, replacement delivery, refund requests and actual refund outcomes separately.

Simulate incorrect batch mapping, delayed delivery records, redemption, unknown revocation, repeated recall jobs and failed notices. Explain every exclusion, unresolved case, replacement and completed after-sales action; investigate newly found items. Preserve original income and separately approved adjustments, and reconcile settlement under actual terms. Unresolved items retain owners and review dates. A completed background job alone does not prove a completed recall.

Frequently asked questions

Can every order be refunded after a supplier flags a batch?

Review actual scope, payment and prior cases first. Approve under product policies and channel terms; a batch alert is neither a refund receipt nor a blanket liability decision.

Can a rerun compensate already handled customers again?

Not by default. Check the recall and stable item record. Additional compensation requires separate approval and evidence.

References