Subscription and Membership Platform Development

View this page

How a custom subscription or membership platform bills in India: UPI Autopay, card mandates, failed payments, member access, and a planning range.

Organisation
WavX Solutions
Telephone
+919310079927

Description

Service Subscription and membership platform development

A subscription or membership platform signs customers up to a plan, collects payment on a schedule, and gives or withdraws access according to whether they have paid. WavX builds these as custom web applications with recurring billing through an Indian payment gateway. If a hosted membership tool or a store subscription app already does what you need, use that instead.

Tell us what you need built Last updated 2 October 2026

What this covers, and when not to build it

"Subscription" and "membership" describe four different businesses. The software they need overlaps, but the hard part is different in each.

Business

Example

The hard part

Ready-made option to check first

Content membership

Courses, research, a paid community

Access control and what a lapsed member can still see

A hosted membership or course tool

Product subscription

Monthly boxes, milk, refills

Delivery schedules, skips, stock and address changes

A subscription app on your online store

Place-based membership

Gym, club, co-working, society

Check-in, freezes, family and corporate plans

Sector software, such as gym management software

Service subscription

Maintenance contracts, retainers, software

Usage, entitlements and invoices a finance team will accept

Billing features of your accounting or gateway product

Build custom when the plans or the member experience are the business itself: pricing that mixes a fixed fee with usage, benefits that depend on tier and tenure, families or companies sharing one plan, or a member area that has to work with systems you already run. If a hosted tool covers your plans today and you are still testing whether people will pay, stay on the tool. The guides on building a subscription business and building a membership website cover that earlier stage.

Modules

Module

What it does

Decide before the build

Plans and pricing

Plans, billing intervals, trials, add-ons, coupons, taxes

Whether a price change applies to existing members or only new ones

Sign-up and mandate

Account creation, plan choice, first payment, approval of the recurring mandate

Which payment methods you offer for recurring billing

Billing engine

Raises each charge on schedule, records the result, issues an invoice

Calendar billing or anniversary billing; how upgrades are pro-rated

Failed-payment handling

Grace period, retries, reminders, an alternative way to pay

How long access continues after a failed debit

Access control

Grants and withdraws content, features or entry according to plan and payment state

What a paused or lapsed member can still do

Member self-service

Upgrade, downgrade, pause, cancel, change payment method, download invoices

Whether cancelling takes effect now or at period end

Notifications

Renewal reminders, payment receipts, failure notices by email, SMS or WhatsApp

Wording and timing of each message

Admin panel

Members, plans, refunds, manual adjustments, an audit log

Who may refund or extend a membership

Reporting

Active members, recurring revenue, churn, failed-payment recovery

The numbers you will review each week

Tiers and rewards

Points, tiers and referral credit linked to membership

Whether this is needed at launch; see loyalty systems

Recurring billing in India: the rules that shape the design

Recurring payments on cards, prepaid instruments and UPI are governed by the Reserve Bank of India's Digital Payments – E-mandate Framework, 2026, issued on 21 April 2026, which consolidated the earlier circulars. The points below are from that document and from Razorpay's documentation, read on 2 October 2026. Your gateway applies them; the platform has to be designed around them.

Rule

Source

What it means for the platform

A mandate is registered only after the customer completes an additional factor of authentication, and the first transaction also needs it

RBI

Sign-up includes one approval step in the customer's bank or UPI app. The platform must handle a customer who abandons it.

Recurring transactions up to ₹15,000 may be processed without additional authentication; above that, each one needs it. The limit is ₹1,00,000 for insurance premiums, mutual fund subscriptions and credit card bill payments

Plans above ₹15,000 per charge do not renew silently. Offer a lower-value interval, or treat the renewal as a normal payment with a reminder.

The issuer sends the customer a notification at least 24 hours before the debit, and the customer can opt out of that transaction or of the mandate

A recurring debit is not instant. Allow for the notice period when choosing the day a charge is raised, and treat an opt-out as a cancelled charge the platform handles politely.

A mandate is for a fixed amount, or a variable amount up to a maximum the customer sets. Changing a mandate needs authentication again

Choose the mandate maximum with upgrades and price rises in mind.

The customer can withdraw a mandate at any time through the issuer

A cancellation can start outside your platform. Listen for it and update the membership.

Razorpay Subscriptions supports cards, UPI Autopay and eMandate (netbanking, debit card or Aadhaar based). Its documentation gives ₹15,000 as the default maximum for a UPI Autopay mandate, rising to ₹1,00,000 for certain merchant categories

Razorpay

Which methods you can offer depends on your gateway account and business category.

When an automatic charge fails, a Razorpay subscription moves to a pending state while retries continue, and to a halted state when retries are exhausted

Your access rules map onto these states: what a member keeps while pending, and what happens at halted.

The gateway reports each of these events to your platform through webhooks . A subscription platform that does not verify them, or that processes the same event twice, ends up with members who paid and were locked out, or who did not pay and were not. The mandate flow itself is described on the UPI Autopay integration page, and gateway setup on the Razorpay integration page linked below.

Members who cannot or will not use a mandate

Some customers will not approve a mandate, and some plans exceed the limits above. The platform needs a second path: a renewal reminder with a payment link, and a membership that extends when the payment arrives. It depends on the customer acting each time, but it works for any amount and any payment method.

If you also have a mobile app

App-store rules decide how a member can pay inside an app, and they differ by what is being sold.

Apple. Guideline 3.1.1 of the App Review Guidelines says that unlocking features or content within an app, including subscriptions and access to premium content, must use in-app purchase. Section 3.1.3 lists exceptions, including goods and services consumed outside the app, and access to content a user acquired on another platform.

Google Play. The Payments policy requires Google Play's billing system for digital content and in-app features, and says it must not be used for physical goods or for physical services. Gym memberships are one of the examples it gives. Developers in eligible countries may offer an alternative billing system under a separate programme.

In practice a club, gym or delivery subscription can take payment through an ordinary gateway in its app. A content membership sold inside the app falls under the stores' own billing unless an exception applies. Both policies are revised often, so WavX checks the current text against your plan before the app is designed. Starting on the web avoids the question until the plans are proven.

Planning range

These figures come from the WavX cost model, the same one behind the software cost estimator . The range is the subtotal less 15% to the subtotal plus 25%. It is a planning range, not a quote.

Scenario

Cost model inputs

Subtotal

Timeline band

Web platform with recurring billing

Custom web application base ₹4,50,000; accounts and roles ₹60,000; payments and billing ₹90,000; admin panel ₹90,000; notifications ₹70,000

₹7,60,000

₹6,46,000 to ₹9,50,000

10–16 weeks

The same, with reporting and a member mobile app

Adds analytics dashboard ₹80,000 and companion mobile app ₹2,00,000

₹10,40,000

₹8,84,000 to ₹13,00,000

Assumptions: small scale (multiplier 1.0), standard interface design, one payment gateway. Not included: the gateway's own transaction fees, SMS and WhatsApp message charges, and content production. Yearly maintenance is 15–25% of the build cost, as set out in the maintenance cost guide .

How the build runs

Plans and rules on paper. Every plan, interval, trial, upgrade path, refund rule and failed-payment rule is written down. A billing bug is often a rule nobody decided.

Gateway account and methods. Your gateway confirms which recurring methods and limits apply to your business category.

Billing engine in test mode. Sign-up, renewal, failure, retry, pause and cancellation are run end to end against the gateway's test environment before any member area is built.

Member area and admin panel. Built on top of a billing engine that already works.

Migration. Existing members are imported. Mandates do not move with a member list. Ask both gateways what can be migrated, and expect that members will have to approve a new mandate.

Launch with a small group. Run one full billing cycle with real payments before opening to everyone.

At handover the source code, the database and the gateway account belong to your company.

What to ask any developer of a subscription platform

What does a member see and keep on the day a renewal fails?

How are gateway events verified, and what happens if one arrives twice or not at all?

How does a plan above ₹15,000 renew?

What happens to billing when a member upgrades mid-cycle?

Can a member cancel without contacting support?

If we change gateway later, what has to be redone?

Subscription and membership platforms are one part of custom software and business systems at WavX.

Frequently asked questions

Can customers pay a subscription automatically by UPI?

Yes, through UPI Autopay. The customer approves a mandate once in their UPI app and later charges are collected on schedule. Under the RBI's e-mandate framework, a recurring charge of up to ₹15,000 can go through without fresh authentication; above that the customer has to authenticate each time, so high-value plans need a different design.

What happens when a renewal payment fails?

The platform should not cut access at once. The usual design is a grace period, retries by the gateway, reminders to the customer with a way to pay by another method, and only then a pause. These rules are written down before the build, because they decide how many members you lose to a failed debit.

Do we need custom software, or will a ready-made tool do?

A ready-made tool is right for a simple paid newsletter, a course site with one or two plans, or product subscriptions on a Shopify store. Custom is worth it when the plans, the billing rules or the member experience are the business itself and the tool cannot express them.

Can members pay inside our mobile app?

It depends on what they are paying for. Apple and Google require their own in-app billing for digital content and features sold inside an app, with exceptions. Physical goods and services consumed outside the app, such as a gym membership, are paid through an ordinary payment gateway. We check the current store rules against your plan before designing the app.

How much does a subscription platform cost to build?

The WavX cost model gives a planning range of about ₹6.5 lakh to ₹9.5 lakh for a web platform with accounts, recurring billing, an admin panel and notifications. This is a planning range, not a quote. Gateway fees are charged separately by the gateway.

Sources

Reserve Bank of India: Digital Payments – E-mandate Framework, 2026 (21 April 2026) · read 2 October 2026

Razorpay Docs: Subscriptions · read 2 October 2026

Razorpay Docs: Subscriptions, supported banks and apps · read 2 October 2026

Razorpay Docs: Subscription states · read 2 October 2026

Apple: App Review Guidelines, section 3.1 (payments) · read 2 October 2026

Google Play Console Help: Payments policy · read 2 October 2026

Related

UPI Autopay integration

Loyalty, rewards and affiliate systems

Razorpay integration

How to build a subscription business in India

Shopify subscriptions

Custom software and business systems

Build your own software — your way, your pricing.

WavX Solutions is here to create your own software in a fully custom way, built exactly how you work — with a pricing model that fits your business. Connect now and let's build it.

Contact Now helpwavx@gmail.com