Airport add-on traffic not credited: reset cycles, balances and reconciliation
If added traffic is not visible, payment may be unconfirmed, the order may be bound incorrectly, the allowance ledger may be stale, or a cycle reset or client cache may be involved. Check payment, ledger credit and display separately; a screenshot alone cannot establish a duplicate purchase or charge.
Contents
1. Define the service and status terms
Define traffic units, plan validity, reset timezone and add-on expiry first. Keep recurring plan traffic, one-time add-ons and promotional allowances in separate ledger entries. If an add-on carries over or one allowance is consumed first, show the same rule at checkout and in the ledger.
2. Bind each order to the purchased entitlement
At order creation, snapshot the internal user ID, service account, plan-cycle ID, traffic amount and unit, price, currency and order time. Do not replace an old order snapshot with the current plan when a payment notice arrives. Handle cross-cycle payments using the order-time rule or a reviewed version so traffic is not credited to the wrong cycle.
3. Process status only after server-side confirmation
After final payment confirmation, add the allowance once through an idempotent ledger entry and record its source order, validity and balance change. Link order success and allowance detail transactionally. Node or panel caches may refresh asynchronously, but they are not the balance ledger. Repeated callbacks must not add traffic again.
4. Route exceptions and retain reconciliation evidence
When traffic is missing, compare order status, account, cycle ID, add-on ledger entry and remaining allowance. Separate incomplete payment, missing entitlement entry and stale display. For complaints near a reset, reconstruct the timeline in one timezone. Do not request another payment or reset the user's ledger before resolving the state.
5. Pre-launch acceptance checklist
Test cycle start, mid-cycle purchase, reset boundaries, carry-over, duplicate notices, late payment, account changes and display-cache delay. Record the order, cycle, payment state, before-and-after ledger and displayed value. Report payment confirmation, allowance crediting and visible-display rates separately.
6. Frequently asked questions
The return page says success. Can I activate the service immediately?
Do not rely only on a browser redirect, screenshot or client message. The merchant backend should verify the trusted payment result, merchant order ID, amount and currency before granting the entitlement once. Query or hold the order while its outcome is unknown.
Should a repeated callback grant the entitlement again?
No. After signature and order checks, use the merchant order ID or confirmed channel transaction ID for idempotency. A completed entitlement action should be recognized as already processed, without adding time, traffic, points or balance again.
Are rates, success rates and crediting times fixed?
Do not infer a fixed promise from an example or one order. Rates and processing terms follow the current quote and integration agreement. A success rate must state its period, order scope and success definition, with pending, failed and canceled orders reported separately.
Business scope
This guide covers billing for lawfully operated, authorized network subscriptions. It does not provide node setup or network-restriction evasion instructions, nor promise that 稳付pay will onboard a particular service.
Confirm integration for your use case
Describe your products, order volume, payment methods and settlement needs to confirm interfaces, fund flows and exception handling.
Contact 稳付pay ↗