Novel-site credits and chapter purchases: preventing duplicate debits and unlocks
A successful novel-site top-up does not mean a chapter has been purchased. If a reader opens the same chapter on a phone and computer and both requests debit credits, the balance and reading rights diverge. For owned or authorized novels, this guide focuses on the chapter-purchase ledger, unique grants and recovery after top-up. These are merchant-side recommendations; confirm acceptance and payment conditions with 稳付pay. No novel-system plugin or content-brand partnership is implied.
Contents
1. Fix credit and chapter-purchase rules
Before purchase, disclose credit uses, conversion, paid and bonus portions, expiry, spending order and after-sales terms. Membership, chapter purchase and credit top-up are different products; membership access is not a permanent purchase record. This example uses credits only for chapters, grants rights under purchase-time terms and spends bonuses first. Merchants must define their rules; this is not 稳付pay pricing or a refund promise.
2. Confirm payment and credit the top-up once
Bind the reader account on the backend and preserve a unique top-up order, payment amount and currency, conversion version and paid/bonus credits. Verify payment under the actual integration documents, then credit against a durable unique top-up source; a return page or screenshot is insufficient. Commit payment confirmation, credit entry and balance together locally. Repeated callbacks reuse the result. A top-up order is not the debit reference for every chapter purchase.
Further reading: Payment callbacks
3. Check an existing grant before charging
For a purchase, validate account, work and stable chapter identity on the backend, reading trusted pricing and rule versions rather than browser prices. Check existing purchase rights or membership coverage and show what is being bought. When a purchase is needed, create its own record with account, chapter, credit price and rule version; retries retain the same reference. Renaming a chapter must not silently create a new charge.
4. Commit the debit, spending entry and grant together
Within one database, recheck rights and available balance, then commit source-level debits, purchase result and unique grant together. Use suitable uniqueness for a reader’s chapter purchase plus locking or version conditions for balance; a check followed by an insert alone cannot stop concurrent devices. Return existing rights without charging, and do not grant or debit on insufficient funds. After conflict or rollback, reconcile instead of displaying success.
5. Worked example: two devices buy one chapter
In an isolated exercise, a verified top-up grants 1,000 paid and 200 bonus credits; a chapter costs 30. These numbers are illustrative. Two devices buy the same chapter. With bonus-first rules, the final state is one grant, one 30-bonus-credit debit and balances of 1,000 paid plus 170 bonus. The other request returns the existing grant; rereading adds no debit. If devices buy different chapters but the balance covers only one, only one eligible purchase commits and the other reports insufficient funds.
6. Recover timeouts using the original purchase
After a timeout, query the merchant’s original purchase reference. If the debit and grant committed, refresh access without charging; after rollback, verify no successful grant before retrying. If a separate service grants reading access, persist a delivery task and reconcile or retry with the same business reference; a local transaction cannot cover that service. Show pending verification for unknown results. Do not both refund credits and keep granting unconditionally. Manual repair adds a reasoned compensation record, retaining original debit and grant sources rather than overwriting a balance.
7. Reconcile credits, chapters and merchant settlement
With owned test accounts, simulate duplicate callbacks and clicks, two devices buying one chapter, concurrent different chapters, insufficient funds and a lost response after commit. Reconcile opening credits plus top-ups and adjustments minus spending to closing credits, and trace each chapter to a purchase or membership period. Do not initiate real payments or use reader passwords. Support needs only necessary order, chapter and redacted evidence.
Reconcile credit spending separately from merchant USDT settlement. Agreed T0 real-time USDT settlement after WeChat or Alipay collection does not turn reading credits into withdrawable money. For direct payments to a merchant-owned USDT address, only TRC20/ERC20 monitoring is currently available; funds bypass 稳付pay and callbacks follow configured confirmation conditions. Apply the original order’s conversion rules. Confirm network, rates, fees and conditions with @tonyyyds.
Further reading: USDT settlement
8. Frequently asked questions
Should a successful top-up callback unlock the currently open chapter?
Not by default. A top-up adds agreed credits; a chapter purchase confirms chapter, price and rights separately. For direct chapter sales, preserve an explicit chapter order, not the current browser page.
Are unique request IDs enough if repeated clicks create two IDs?
No. Also check the account’s existing grant for that rereadable chapter and keep debit and grant within a consistent transaction boundary. Two references alone do not justify two charges.
Should a reader buy again if a purchased chapter will not open?
First check the original debit, valid grant and reading-service status. If the purchase is valid, repair access or its delivery task without charging again. Resolve disputed rights or content availability under purchase terms; continued access to all removed content is not guaranteed.
References
Official references cover only database uniqueness and local transaction principles. Novel-credit rules, purchase flows and sample numbers are original merchant-side designs, not 稳付pay API fields, plugin capabilities or fixed product promises.
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 ↗