Card-platform refunds: checking code redemption, unknown results and revocation evidence
For a card platform, the difficult refund question is often whether a delivered code can still be used. Using merchant-owned software licenses, this guide addresses a code that was displayed but whose redemption query timed out. It does not repeat integration setup or imply unconditional acceptance by 稳付pay.
Contents
1. Establish what you can verify
Use this process for owned or authorized digital goods with clear after-sales terms. Establish whether the item can be revoked, who confirms redemption, how long evidence is retained and who approves refunds. States and records below are merchant-side design suggestions, not 稳付pay dashboard features. If third-party codes cannot be queried or revoked, do not infer that they are unused. This guide does not decide eligibility: assess disclosed terms and applicable requirements.
2. Separate viewing, redemption and revocation
Displayed means the customer could see the code. Redeemed requires confirmation from the licensing system; revoked requires explicit confirmation that it is invalid. A timeout, unavailable service or unexpected response means unknown, not unredeemed. Record the check time, source system and traceable internal evidence ID. Support screens should show masked identifiers. Keep full codes out of ordinary logs and never request customer passwords or wallet recovery phrases.
3. Example: one refund from a two-code order
Fictional DEMO-ORDER-A contains two licenses at an illustrative sale price of CNY 30 each, totaling CNY 60; these are not platform fees. One is redeemed. The other was displayed, but its query timed out. Link the case only to the second internal code ID. Derive its proposed refund ceiling from its sale snapshot and allocated discount: CNY 30 here. Do not mark the whole order unpaid. If later redeemed, escalate for review; if confirmed revoked, proceed to refund approval.
4. Six checkpoints before closing the case
First verify the trusted payment record and purchaser ownership. Second link the case to the individual delivery record and pause additional replacement delivery for that item. Third query redemption and retain evidence. Fourth, where revocation is supported, request it from the licensing system and await a definite result. Fifth approve the specific amount and perform the refund under the actual channel agreement. Sixth close only after verifying the real refund receipt. Redeemed, failed-revocation or unknown cases stay under manual review, never prematurely marked refunded.
5. When redemption races with a refund
An unredeemed query is not a lock: the customer may redeem a moment later. In a merchant-owned licensing system, design an atomic revoke-only-if-still-unredeemed transition and inspect its actual outcome. Keep the local order, per-item case reservation and audit record consistent in a transaction. Do not hold database locks while awaiting an external system. If an external revocation times out, query the original operation ID. Without result lookup, escalate rather than treating timeout as success or blindly resending.
6. Failed refunds, duplicate cases and resale
If revocation succeeds but the refund fails, retain revoked/refund pending; do not reactivate the code to make the screen look complete. Merge repeated requests into the same per-item case and keep successful cumulative refunds within the approved refundable amount. Local constraints cannot replace external refund-result checks. Pause a second refund while the first result is unknown. Keep displayed or revoked original codes in isolated history, not saleable stock. Add new inventory only for new credentials the issuer confirms can safely be issued.
7. Reconcile item, payment and refund evidence
Closure evidence should include the original order and payment reference, masked item ID, source and time of redemption or revocation confirmation, approved amount and reason, actual refund outcome and operator. Separate approved from refunded: a support note does not prove money was returned. Review unknown redemption, revoked-but-not-refunded cases, amount mismatches and duplicate requests daily, with an assigned owner. Customer updates should explain the current state and next follow-up, without invented refund deadlines or arrival guarantees.
Related verification guide: After-sales records and redaction
8. FAQ and rehearsal checklist
Rehearse with synthetic data: unredeemed, redeemed, query timeout, revocation that succeeds after a timeout, simultaneous approval by two agents, refund failure after revocation and repeated requests for one item. Each run must trace the order to one case and its final evidence; uncertain external outcomes remain on the review list. These are tests of the merchant’s own software workflow, not a request to create real payment orders or a universal automated refund interface.
Can a customer’s claim of non-use authorize a refund?
A claim alone does not establish redemption status. Use product terms, licensing evidence and approval. If verification is unavailable, record unknown and escalate; a screenshot alone is insufficient.
Does revocation prove a refund succeeded?
No. Revocation changes product access; a refund is a separate funds outcome. Retain evidence for each. Continue resolving a failed refund without automatically restoring or reselling the original code.
Does 稳付pay provide these redemption or automated refund APIs?
This article makes no such claim. The product licensing system owns redemption; confirm refund methods with the channel and technical team. The independent automated payout API is not open. A workflow is not callable API documentation.
References
These official references support general transaction, uniqueness and concurrent-state principles. They do not establish that 稳付pay uses a particular database or offers code-redemption or automated refund features. Actual integration and refund arrangements require the agreed protocol.
Confirm integration for your business scenario
Describe your products, order volume, payment methods and settlement needs to confirm the APIs, movement of funds and exception handling item by item.
Contact 稳付pay ↗