Gifting novel-site credits: reservations, claim expiry and refund attribution

Design gifting only when the novel site’s own terms allow it. Define eligible credits, claim deadlines and refund attribution before implementing reservations and single claims. This is merchant-side design, not a WenFuPay transfer, withdrawal or gifting API.

Continue by topic

Confirm collection and eligible credits first

WenFuPay offers WeChat, Alipay and UnionPay collection subject to licensed content, business configuration, rates, limits and extras. Describe recharge packages and gift rules before formal setup and callback testing. Purchased credits and collection fees are separate; gifted credits are not new payment revenue.

USDT settlement of CNY proceeds currently uses TRON/TRC20 only, with agreed costs, exchange and conditions. The merchant manages same-site, non-cash, non-withdrawable gifts allowed by its terms. Specify whether paid, bonus or particular batches are eligible; never assume the entire balance can be gifted.

Reserve eligible batches before creating a claim

Retain gift reference, sender, recipient conditions, credit batches, quantity, deadline and rule version. Atomically check availability and reserve credits. A link alone is not a completed transfer, and reserved credits must not remain spendable on chapters.

Example: from 100 available credits, reserving 30 leaves 70 available and 30 pending, traceable to the original purchase. Only an eligible successful claim creates recipient credit. Repeated clicks use the same gift identity and create no second 30. Use unguessable links, limit disclosure impact and expose no account details.

Choose one outcome: claim, cancellation or expiry

Concurrent claiming and expiry must not both succeed. Durable state and unique constraints coordinate one result. Freeze the affected scope for refunds or disputes, distinguishing unclaimed, claimed-unused and consumed credits; do not arbitrarily deduct from all recipients because the payer requested a refund.

Release unclaimed gifts to their original batches under current expiry rules. Expired bonus credits do not become new permanent paid credits. Review claimed credits using disclosed terms and consumption evidence. Keep origin records; deleting a gift does not resolve its balances. No cash redemption or cross-site exchange is described here.

Test and reconcile separately from payment callbacks

Authenticate and match the original recharge under the real contract and credit it once before merchant gift logic begins. Reopening checkout or a gift link must not create another payment credit. Simulate double clicks, competing claims, expiry races, refund holds and expired batches; do not transfer actual user balances for tests.

Reconcile purchase sources, reservations, recipient credits, releases and spending. Internal movement creates neither new revenue nor another merchant settlement. Retain redacted references and transitions, show clear claim statuses, and investigate unknown differences rather than asking customers to recharge to cover a system gap.

Frequently asked questions

Does gifting 30 credits need another payment callback?

No. The original callback confirms the original purchase; reservations and claims belong to the merchant’s internal credit ledger.

Do expired unclaimed gifts always return as permanent credit?

No. Follow the original batch type, expiry and disclosed rules; do not convert expired bonus credits into permanent paid credits.

References