Combining comic membership gifts and paid purchases: sources, refunds and redemption deduplication

A reader redeems a membership gift code and then buys membership through WeChat or Alipay. One expiry field cannot explain what should survive a refund. Keep each gift and genuine purchase as a separate entitlement contribution, then apply the disclosed stacking rules. This guide concerns owned or licensed comics. The merchant manages gift codes; WenFuPay is not being described as a code-issuance service.

Continue by topic

Separate promotional sources from paid orders

For a code campaign, retain its campaign ID, eligible account or conditions, validity, gift scope and redemption-rule version. Paid orders separately retain product, purchaser, amount, currency and payment evidence. Do not manufacture a cash top-up to represent a gift.

Before purchase, explain whether gift and paid periods follow one another, overlap or have a cap, including membership-level and content restrictions. Later campaign changes must not silently recompute past grants. Independent permanent chapter purchases must not be overwritten by membership stacking.

Fix ownership before blocking code and order replays

Associate redemption with a stable user ID and a specific campaign-code record; associate payment with the original purchasing account. Nicknames, current devices and payer names alone cannot assign membership. Shared codes or merged accounts require eligibility and redemption-history checks under the published rules.

A single-use code needs a durable claim record, and repeated notices for one paid order produce one contribution. Unique constraints can support local deduplication. “One claim per user” and “one redemption per code” are different rules that need separate definitions, not just a browser warning.

Preserve every contribution during concurrent stacking

Example: gift G and paid order P both add membership to READER-A. Preserve each source, scope and period, then calculate permissions under the published ordering or merging rule. Avoid two workers reading the same old expiry and overwriting one another.

If reading access is external, query the original operation after a timeout rather than redeeming another code as compensation. Show the current expiry while letting support inspect intervals attributable to gifts and purchases. This example specifies no standard gift length or comic membership price.

Adjust the related purchase and review gifts under their terms

Before a refund adjustment, verify the paid order, usage or reading history, actual refund outcome and campaign terms. Do not zero the membership or subtract arbitrary days from its current expiry. Adjust the affected source contribution and recalculate still-valid entitlements.

If a gift explicitly depends on a valid purchase, review the condition disclosed before payment and retain adjustment evidence. Integrate payment confirmation and callbacks with WenFuPay’s formal documentation; codes and reading access remain the merchant’s responsibility. Test concurrent code claims, repeated payment notices, gifts before and after purchases and unknown refund outcomes using simulated records. Unknown outcomes remain under review, not automatically refunded.

Frequently asked questions

Must a gift disappear when the paid order is refunded?

Not universally. Examine the paid contribution and gift conditions separately. Independent gifts follow their own terms; purchase-dependent promotions need review against the previously disclosed condition.

Does payment success prove that a membership code was redeemed?

No. Payment, code claims and reading authorization are different records. Each needs evidence and an association with the correct account.

References