Merchant top-ups and subscription operations

VPN renewal billing periods: early renewal, expiry boundaries and timezones

A VPN renewal that appears one day short may reflect unclear billing units, start times or display timezones rather than a wrong payment. This guide covers lawful subscription invoices, service periods, payment confirmation and support reconciliation only. Merchants must choose and disclose their rules in advance; these examples do not imply automatic debits or guaranteed 稳付pay acceptance of VPN businesses.

Contents

1. Treat 30 days and a calendar month as different units

Disclose whether the product sells a fixed duration or calendar months. If 30 days means 720 consecutive hours, apply that agreement. Calendar-month products need a rule for a missing corresponding month-end date. Do not show only “monthly” and choose the calculation during a dispute. Store the agreed unit and rule version; later wording or prices must not reinterpret past purchases.

2. Define explicit start and end instants

A merchant may define periods that include the start instant and exclude the end, then disclose that convention. An end of 2026-11-01 00:00+07:00 must not also be described as valid throughout November 1. Store offset-aware timestamps or a common time basis and display the timezone. RFC 3339 supports explicit offsets; it does not choose subscription billing rules for merchants.

3. Preserve remaining time on early renewal

For an extending product, renewal starts at the current period’s end rather than replacing it from payment time. For example, a period ending November 10 at 00:00+07:00 with a fixed 30-day renewal paid November 5 extends to December 10 at the same offset. This illustrates that rule only. Immediate replacement products must disclose treatment of remaining time before payment; replacement and extension are different operations.

4. Apply the agreed start rule after expiry

After expiry, disclose whether a new purchase starts at payment confirmation, activation or a fixed cycle. Do not silently count delivery queues as consumed service or backdate every purchase to the old expiry. Preserve payment confirmation and entitlement activation separately. For late callbacks, inspect the original order and existing periods before applying actual product rules; unclear cases require review.

5. Separate retries from two real renewals

Repeated notifications for one order cannot extend twice. Two independently verified purchases create two renewals under product rules. Concurrent processing must append consistently from the current end rather than having both workers read an old date and overwrite each other. Use transactions and appropriate concurrency controls for merchant records, while reconciling remote delivery references separately; a local transaction does not cover an external service.

6. Preserve before and after values when correcting dates

For “one day missing,” compare unit, previous expiry, payment confirmation and display timezone before deciding renewal is missing. A display difference does not automatically justify a day’s credit, and a real missing renewal needs more than new wording. Corrections record old time, calculation, new time, order and reviewer, then verify delivered results. Agreed outage compensation has a separate record rather than rewriting purchased duration.

7. Reconcile added periods, not only final expiry

For every renewal, retain previous end, added interval, resulting end and delivery evidence. This explains repeated purchases. Daily, match each verified payment to one valid renewal or an explicit support state; investigate extensions without payment through approval records. Reconcile merchant settlement separately. USDT receipt proves neither correct subscription duration nor VPN performance or availability.

Related verification guide: Support records and redaction

8. Billing-period checks and FAQ

With owned test records, check month-end purchases, the exact expiry instant, timezone displays, early renewal, concurrent orders and replayed callbacks. Test fixed durations and calendar months against their actual product rules without real payments. Support needs order, unit, before/after times and necessary redacted evidence, never VPN passwords. Use https://t.me/tonyyyds first for collection onboarding and exceptions.

Does early renewal lose remaining days?

An extension follows the current end. Immediate replacement must disclose treatment of old rights; check original purchase terms.

Do two callbacks for one payment add time twice?

No. Confirm one renewal for the verified order; two genuine purchases are handled separately under the rules.

Does a different displayed date prove a missing day?

Not necessarily. Normalize timezones and compare exact instants, purchased units and boundary rules before correcting.

References

The references support general database and time-recording principles only. These are merchant-side designs, not 稳付pay dashboard features or API parameters. Current fiat collection channels are WeChat personal-code collection, WeChat native collection and Alipay native collection. T0 real-time USDT settlement follows the merchant’s agreed configuration and terms; it is not a success-rate guarantee. TRC20/ERC20 monitoring concerns payments directly to the merchant’s own wallet, without platform custody; callbacks follow configured confirmation conditions. The automated payout API is not open.

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 ↗