Scheduled VPN downgrades: paid periods, versioned changes and refund conflicts

A request for a lower VPN plan next period does not reduce already purchased rights immediately or authorize another automatic charge. Schedule changes only when the merchant offers and discloses such rules. This guide concerns lawful, authorized services and entitlement accounting, not connection instructions or a downgrade engine supplied by 稳付pay.

Continue by topic

Decide whether this is intent or a purchase

Public methods include WeChat Pay, Alipay and UnionPay, subject to business approval and formal configuration. Explain the lawful service, domain, plans, payment and delivery flow before account setup. Confirm rates, limits, extra charges and settlement terms; keep formal parameters and keys private. The merchant must disclose future pricing, price differences, refund treatment and effective time. A scheduled downgrade is not proof of payment.

Merchant USDT settlement after CNY collection currently uses TRON/TRC20 only; confirm charges, triggers and timing. Payment success, actual VPN rights and merchant settlement require separate evidence. Scheduling does not invoke automatic payouts or refunds; the automatic payout API is not open. Nor does it authorize an unapproved charge next period.

Version the future change independently

Record a stable account, original purchase, current plan and period end, target plan, policy version, timezone, effective point, request and confirmation time, and cancellation conditions. These are merchant records, not new 稳付pay API fields. Keep scheduled state, payment for the next period and actual authorization state separate.

Illustration: account U has a higher plan until December1 at00:00+07:00 and requests a lower plan next period. If that period requires another purchase, scheduling alone adds no time. Without a valid purchase, the service expires under the disclosed policy rather than renewing free. If U later buys a different plan, explicitly cancel, replace or retain the schedule under the rules; do not let job timing decide.

Validate payments and scheduled execution consistently

Authenticate new-purchase callbacks under the formal contract and match merchant, order, amount, currency and success. Durable payment identity produces one purchased entitlement. Do not discard a trusted renewal because a downgrade is scheduled, or recreate a cancelled change after an old callback.

At execution, inspect the active schedule version, cancellation state, newer purchases and after-sales constraints. Confirm eligibility and create one fulfillment responsibility in a local transaction. A queued V1 must stop if the user has confirmed V2. If a remote authorization update times out, investigate the original operation. Local uniqueness cannot guarantee exactly one external effect; retries must not add periods repeatedly or overwrite a completed upgrade.

Check three times and retain separate after-sales evidence

Display when current rights end, when the change is scheduled and when actual authorization completes. They are not one success flag. If the target plan disappears, the account is disabled or a refund is unresolved, retain a pending case for policy-based review rather than silently selecting an arbitrary plan. A refund request does not erase payment; actual refund, entitlement adjustment and schedule cancellation need separate records.

Simulate repeated requests, cancellation with a stale queued job, renewal around the boundary, duplicate callbacks, remote timeout and refund conflict. Verify that U loses no current purchased period early, future purchases deliver once and old versions cannot overwrite newer decisions. Reconcile merchant settlement to actual money and confirmed adjustments, not downgrade intentions. Support needs redacted orders and a timeline, not connection passwords.

Frequently asked questions

Can scheduling reprice historical payments immediately?

No. Preserve the purchase snapshot and record any agreed price adjustment or actual refund separately.

Does a finished timer job prove completion?

No. Confirm the current valid version and actual authorization result. Timeout or conflict remains unresolved.

References