Which six billing rules must a paid membership or subscription specify?

A subscription specification must settle six groups of rules before build approval: the entitlement being sold; price and billing timing; the customer's renewal choice; upgrade and downgrade treatment; cancellation and refunds; and failed-payment recovery. A payment provider can execute configured transactions but cannot define the company's commercial promise. Without one reviewed state table, a technically successful integration can still produce contradictory outcomes across billing, access, customer service and finance.

Scope and market context

This guide is for executives, product leaders, finance, service and operations teams designing paid membership, digital services, recurring delivery or other subscription products for mainland China. One-time purchases can reuse its order and refund disciplines without renewal states.

Payment channels, app stores and regulated sectors have their own eligibility and product rules. Alipay's “Individual Subscription” documentation, updated 31 August 2026, describes a subscription solution for the AI sector. It is evidence of that specific capability, not proof that every merchant and product has identical access. Verify the intended entity, channel and product in its own account.

Rule 1: Product and entitlement

Define what the customer buys beyond a label such as “Monthly Pro”:

• included features, allowances, service events, content or seats;
• whether access starts at payment, manual approval or a nominated date;
• whether ownership is per account, person, organisation or seat group;
• allowance carry-over and the order in which free and paid value is consumed;
• treatment of existing subscribers when a product is retired;
• access removed immediately or at period end after refund, non-payment, risk action or termination.

Acceptance should trace every subscription to the product version and entitlement snapshot sold at purchase. Editing a current catalogue must not silently rewrite historical promises.

Rule 2: Price, period and first charge

Specify currency, tax treatment, daily/monthly/annual interval, billing anchor, first-period proration, free trial, promotional period, return to standard price, caps, minimums and how a change applies to existing customers.

Define dates that do not exist in every month. Alipay's current solution describes a month-end adjustment for a subscription that began on the 31st and a return to the relevant date in later months. It also has provider-side timing for notification and collection. The merchant system should store the actual period boundaries returned by the provider instead of approximating every month as 30 days.

Finance should approve at least twelve months of examples, including month end, leap year, conversion from trial, promotion expiry and a price change. Revenue, tax, refund and service periods should reconcile.

Rule 3: Renewal choice, authorisation and notice

Automatic renewal must be an arrangement the customer can understand and choose. Document:

• where price, interval, renewal and cancellation are displayed;
• the action that records agreement and the evidence version retained;
• the prominent explanation before service begins;
• who sends pre-renewal notice and how delivery failure is recorded;
• when the merchant stops attempts or service after channel authorisation is withdrawn;
• how customer service retrieves agreement, notice and transaction evidence.

Article 18 of China's Measures for the Supervision and Administration of Online Transactions requires online operators using automatic extension or renewal to draw consumers' attention prominently before service and before the renewal date, while preserving consumer choice. A provider notification does not remove the merchant's responsibility for coherent product screens, orders and service evidence.

Rule 4: Upgrade, downgrade and plan changes

“Supports plan changes” must state whether a change is immediate or next-period; how remaining value is treated; whether an extra payment or refund occurs; how seats, data and allowances migrate; whether the action can be reversed; and how repeated changes are sequenced.

Alipay's current subscription capability supports upgrades and downgrades with related payment or subscription changes. The merchant must still decide the commercial policy. A provider cannot know whether reducing seats should archive data, whether annual-to-monthly migration is allowed, or whether a promotional subscriber qualifies for a new plan.

Write every path as current state, action, amount, effective time, new entitlement, accounting evidence and customer message. Test repeated clicks, concurrent actions, processing states and rollback after failure.

Rule 5: Cancellation, expiry and refund

Distinguish immediate cancellation with access ending, cancellation that becomes effective at period end, and merely disabling the next renewal. Define full, residual-value, usage-based, reviewed and non-refundable outcomes, ensuring the interface and contract agree.

Alipay documents period-end and immediate cancellation as separate choices, with immediate cancellation able to trigger a refund or configured refund amount. One “Cancel subscription” button can therefore represent materially different money and access outcomes. The service console should preview the consequence before an irreversible action.

Also specify post-expiry data retention, export, resubscription, repurchase and promotional eligibility. Loss of premium functionality should not cause unannounced deletion of customer data.

Rule 6: Payment failure, retry and recovery

Define outcomes for insufficient funds, channel rejection, expired authorisation, network timeout, duplicate or out-of-order notification and merchant downtime:

• who controls retry count and timing, and whether provider defaults fit the product;
• whether a grace period exists and which features remain available;
• when status becomes overdue, paused, cancelled or expired;
• whether successful recovery keeps the period or creates a new one;
• how late success and an initiated refund avoid duplicate fulfilment;
• whether service agents can restore access and what review is required;
• how finance finds service delivered without payment or payment received without access.

Alipay's current solution describes pre-expiry notice, advance collection, algorithmic retry and termination after final failure. Store the provider's actual subscription state, periods and notifications; do not reproduce remembered defaults as fixed business logic.

Minimum state table

Current state	Permitted action	Financial result	Entitlement result	Evidence retained
Trial	Convert or cancel	First charge or no charge	Trial expires or paid access begins	Trial terms and agreement
Active	Renew, upgrade, downgrade, cancel	Charge, adjustment, refund or scheduled change	Immediate or period-end change	Product version, period and authorisation
Payment processing	Query, wait, controlled retry	Never create an accidental duplicate charge	Existing access or grace policy	Request, provider state and notifications
Past due or grace	Recover, restore, cancel	Post on success or end in failure	Limit selected features or pause	Attempts, notices and service actions
Cancels at period end	Restore or await expiry	No next-period collection	Current access continues	Request and effective time
Cancelled or expired	Repurchase or export	New order or no movement	Apply retention policy	Reason, refund and retention deadline

Terminology may vary, but money, entitlement and evidence must correspond. Provider payment status, merchant subscription status and membership access status should not be collapsed into one field; delayed notifications would make the true state impossible to represent.

Delivery scope and acceptance

A first release should include versioned products and prices, subscription orders, agreement evidence, periods, payments and refunds, entitlement allocation, notifications, service lookup, reconciliation, exception queues and audit records. Recommendation widgets and sophisticated promotions can wait; cancellation, failure handling and accounting evidence cannot.

Acceptance should use pre-approved scenarios: first purchase, trial conversion, normal renewal, month end, promotion expiry, upgrade, downgrade, period-end cancellation, immediate cancellation and refund, payment failure, successful retry, final failure, duplicate and out-of-order notifications, service restoration, channel revocation and reconciliation difference. Check the customer interface, provider transaction, entitlement, service console and finance result together.

Frequent mistakes

Assuming provider support defines the product. The provider supplies capability and defaults; the merchant owns the product promise, entitlement, refund and service responsibility.

Treating cancellation as one Boolean. Request time, financial effect, access end, future collection and data retention are separate decisions.

Granting access on any success notification. Notifications may repeat or arrive out of order. Fulfilment must be idempotent by subscription, period and transaction, with query-based reconciliation.

Delegating every renewal notice to the channel. Verify the live channel experience and retain the merchant's own presentation, choice and order evidence.

Ongoing controls

Review collection success, final failures, refunds, complaints, notice delivery, entitlement mismatches and reconciliation differences each month. Re-run the full state suite after any price, interval, plan, notice, refund or provider change. Product, finance, service and engineering should jointly approve rule versions, with explicit migration treatment for existing subscriptions.

If digital subscriptions are sold through App Store or Google Play, use the in-app purchase fees and scope guide to assess channel rules, regional pricing, refunds and subscription-management responsibilities separately from web billing.

Sources

• Alipay Agent Payment Documentation: Individual Subscription (updated 31 August 2026; accessed 4 September 2026)
• State Administration for Market Regulation: Measures for the Supervision and Administration of Online Transactions (accessed 4 September 2026)

This is a product and delivery framework, not a substitute for live provider eligibility, consumer-protection review, tax advice or legal advice.