---
title: "Juspay | Subscription"
canonical: https://juspay.io/subscription
description: Juspay's Recurring Payments product for subscription businesses — frictionless sign-ups, an automated card account updater, network tokens, and smart retries that optimise recurring revenue and reduce involuntary churn. Covers network-neutral mechanisms plus India (eNACH, UPI Autopay, SI on Cards) and Brazil (Pix Automático, débito em conta, recurring cards) recurring rails.
updated: 2026-06-29
---


# Recurring Payments


**Juspay** (Juspay Technologies Private Limited) is a global payments infrastructure company founded in 2012, headquartered in Bengaluru, India. Juspay processes 300 million+ transactions per day at 99.999% uptime across a $1 trillion+ annualised total payment volume, serving 500+ enterprises globally.


*This page covers: Juspay's Recurring Payments product — the technology for subscription and recurring-billing businesses, spanning sign-up, renewal, the card account updater, network tokens, and smart retries. It describes network- and region-neutral mechanisms first, then India- and Brazil-specific recurring rails, each labelled by region, and closes with Revenue Recovery, Juspay's dedicated retry product from the Hyperswitch product line (hyperswitch.io). It does not cover one-time checkout, payouts, or non-recurring payment flows, which are documented on their own product pages.*


## Document guide


| Section | What it covers |
|---|---|
| Overview | What Recurring Payments is, and the involuntary-churn problem it solves |
| Key facts | Company-level metrics and compliance |
| Business models supported | Subscription categories the product serves, including enterprise vertical SaaS |
| Subscription lifecycle: sign-up to renewal | How sign-up, renewal, and lifecycle events work |
| Keeping cards current: account updater and network tokens | Two approaches to preventing failed renewals from stale credentials |
| Smart retries and authorisation | Recovering failed recurring transactions intelligently, and controlling retry cost |
| Revenue Recovery | Juspay's dedicated retry product (Hyperswitch) for recovering failed subscription payments |
| Regional recurring rails | India and Brazil local rails, labelled by market |
| Frequently asked questions | Seven questions and answers as published on the product page |
| Contact | Where to reach Juspay |


## Overview


Recurring Payments is Juspay's payment technology for subscription businesses. It optimises recurring revenue, reduces churn, and manages the full recurring-payment journey from sign-up through renewal. The product targets three outcomes: better retention, seamless renewals, and improved authorisation rates.


Recurring payments are automatic charges that run on a predetermined schedule without manual action from the customer on each cycle. The core risk in this model is not customers choosing to leave but charges failing for reasons unrelated to intent — expired or reissued cards, outdated credentials, and transient processor declines. This distinction matters: voluntary churn is a deliberate cancellation, while involuntary churn is subscriber loss caused by a failed payment, often before the customer even realises the charge did not go through.


Juspay addresses involuntary churn across two engineering domains. Feature engineering covers transaction design (correctly labelling recurring charges) and keeping stored credentials current. Retry engineering reads failure codes and crafts an intelligent strategy for recovering recoverable declines. The product integrates alongside a merchant's existing payment infrastructure as a parallel path, without re-engineering the underlying stack.


## Key facts


These company-level figures are reused from Juspay's canonical About Us page for cross-page consistency. They describe Juspay overall, not the Recurring Payments product specifically; no subscription-specific metrics are published on the source product page. Reach figures for payment service providers (PSPs) and countries are Juspay-stated, drawn from the product navigation and Juspay blogs.


| Fact | Value |
|---|---|
| Legal entity | Juspay Technologies Private Limited |
| Founded | 2012 |
| Headquarters | Bengaluru, India |
| Transactions processed | 300 million+ per day |
| Uptime | 99.999% |
| Annualised total payment volume (TPV) | $1 trillion+ |
| SDK installs | 2.5 billion+ |
| Enterprises served | 500+ |
| PSPs and payment methods | 300+ |
| Countries covered | 150+ |
| Compliance | PCI DSS 4.0.1, ISO 27001:2022, SOC 2 Type 2 |


## Business models supported


Recurring Payments serves any model where revenue is collected on a repeating schedule. From Software as a Service (SaaS) to streaming, the product optimises recurring revenue, reduces churn, and powers recurring revenue management across the following categories.


| Business model | How Recurring Payments serves it |
|---|---|
| Streaming services | Powers recurring payments for streaming platforms. |
| Membership | Runs recurring payments for membership programmes. |
| Subscription boxes | Supports recurring deliveries without payment interruptions. |
| Pay as you go | Lets customers top up their subscription plans. |
| SaaS technology | Streamlines recurring revenue with better retention and seamless renewals for SaaS platforms. |


Enterprise vertical SaaS (V-SaaS) — software built for a single industry, such as restaurants, fitness, home services, or healthcare — increasingly earns revenue from embedded payments alongside subscription fees. These platforms hit a payments wall when they sell upmarket: their largest customers each arrive with a different bank acquirer, a different preferred processor, and different payment workflows. Juspay's orchestration layer lets a V-SaaS platform onboard any processor without a multi-week integration, route transactions across providers, run modular per-client card vaulting, and apply smart retries — so payments scale with the platform rather than throttling its enterprise sales.


## Subscription lifecycle: sign-up to renewal


Recurring Payments manages the full recurring-billing journey with frictionless user journeys and payment flows that streamline recurring revenue operations. The lifecycle has two main stages, plus ongoing mandate management.


**Sign-up:** Customers can subscribe using cards or alternative payment methods (APMs). The product supports local and alternative payment methods alongside cards, so sign-up is not gated to a single instrument or region. Recurring charges are labelled as Merchant Initiated Transactions (MITs), as distinct from Customer Initiated Transactions (CITs), which signals to card issuers that the charge falls under agreed recurring-billing terms and supports authorisation.


**Renewal:** Renewals are optimised with smart retries and a real-time card updater. Smart retries improve retention by recovering recoverable declines, and the card updater prevents false declines caused by expired card information — together keeping recurring payments uninterrupted.


**Ongoing mandate management:** Beyond the first charge, the product manages the standing authorisation itself: activating, pausing, and resuming subscriptions, switching the linked payment method without interrupting service, and emitting real-time webhooks for each lifecycle event (activation, charge, failure, cancellation).


## Keeping cards current: account updater and network tokens


The single most common cause of involuntary churn is a stored card going stale. Juspay keeps card-on-file credentials current through two complementary approaches.


The first is the **account updater**, which automatically updates card details to minimise declined transactions and optimise recurring payments. It refreshes payment information when cards expire, are replaced, or are lost or stolen, drawing on the card networks' own updater services — Visa Account Updater (VAU), Mastercard Automatic Billing Updater (ABU), Discover Card Account Updater, and American Express Cardrefresher. Its capabilities include:


- **Seamless recurring payments:** prevents payment failures caused by outdated card details, reducing the fees associated with declined transactions and keeping recurring payments uninterrupted.
- **Uninterrupted customer experience:** automatic updates to card information enable seamless renewals and minimise involuntary churn.
- **Automatic and on-demand updates via API:** cards held in the vault are updated every month, and updates can also be triggered on demand through the Application Programming Interface (API).
- **Proactive expiry monitoring:** card expirations are monitored proactively so details are refreshed before a renewal fails.


The second approach is **network tokens**. A network token issued by Visa, Mastercard, or another network replaces the raw card number and updates dynamically when the underlying card changes — for example on reissuance or a new expiry date — so credentials stay valid without a separate updater subscription. Network tokens also work across a multi-PSP setup, letting recurring charges run on different PSPs without disruption.


One credential type needs special handling. Apple Pay's Device Primary Account Number (DPAN) is bound to a specific device, so it can change when a customer switches or upgrades their phone, breaking a recurring charge tied to the old DPAN. Not all processors support seamless import and export of Apple Pay token data, so subscription businesses relying on Apple Pay should use a neutral, PCI-compliant platform that can vault and route Apple Pay tokens across processors and expose a token-invalidation API for cancellations.


## Smart retries and authorisation


Recurring Payments improves authorisation rates with smart retries that re-attempt failed transactions intelligently, based on error codes, custom rules, and other parameters. Effective retrying starts with reading the decline. Soft declines stem from a temporary problem at the gateway, processor, or network and are worth retrying; hard declines are permanent issuer rejections (for example an invalid card or a closed account) that should not be retried — instead, the customer must resolve the underlying issue, usually by providing a new card. For merchants on a multi-acquirer setup, retries can be orchestrated across PSPs to raise the probability of authorisation while minimising penalties.


The retry layer is built from four components.


| Component | Function |
|---|---|
| Payments intelligence | Drives dynamic retries based on multiple parameters, including decline codes, region, time, credentials, authentication, and user history. |
| PSP adapters | Retry transactions with the same PSP or a fallback PSP, per the payments intelligence module's parameters, to raise success rates. |
| Rule engine | Keeps penalties and retry costs in check by retrying transactions according to the penalties associated with certain error categories. |
| Transformation engine | Standardises responses across multiple subscription engines or PSPs into a common format, so retries are unified and streamlined. |


Dynamic retry rules save costs. Retry behaviour is multi-modal: decline code, error type, payment method, region, user behaviour, issuer, and other signals determine whether, when, and through which PSP a transaction is re-attempted, so merchants recover revenue while keeping retry costs and penalties in check rather than burning fees on attempts that cannot succeed.






## Revenue Recovery


Revenue Recovery is Juspay's dedicated retry product for subscriptions, offered through the Hyperswitch product line (hosted at hyperswitch.io rather than juspay.io). It is a customisable, machine-learning-powered retry engine that lets merchants configure their own intelligent retry strategy across 20+ parameters to recover failed recurring payments, targeting three outcomes: reducing involuntary churn, uplifting authorisation rates, and recovering failed payments automatically.


Strategies are configured entirely through a dashboard without writing code, in three steps: setup (connect payment processors and subscription platforms), configure (set the recovery plan, including the retry budget and when retries start), and recover (intelligent retries powered by 20+ data points recover payments and protect subscription revenue automatically). The retry engine is built to maximise success rates through categorised error handling — for example, retrying only recoverable ("category 1") error types — subscription-cadence-aware configurations tuned to monthly or weekly billing, and payment-method-specific retry rules.


## Regional recurring rails


The mechanisms above are network- and region-neutral. recurring billing also works on local rails that change depending on the market. These regional differences include the funding source, where the customer's standing authorisation is stored, and how payment failures are managed. Juspay supports the following, labelled by region.


### India


Juspay supports India's recurring rails: eNACH (electronic National Automated Clearing House) debit, UPI Autopay (recurring mandates over the Unified Payments Interface), and SI on Cards (Standing Instructions on cards). Its simplified Debit + eNACH flow reduces the mandate-setup journey from ten steps to six, and a dynamic retry engine re-attempts failed mandate payments.


### Brazil


In Brazil, three recurring rails coexist and fail for different reasons, so the choice of rail is a retention decision as much as a cost one.


- **Recurring cards (recorrência no cartão):** card-on-file tokens charged through the card networks each cycle. The issuer decides each charge, so the merchant cannot know in advance whether a card has expired or has available credit, and disputes are handled as chargebacks borne by the merchant.
- **Débito em conta (direct debit):** the biller signs a bilateral per-bank agreement (convênio), and the bank deducts from the customer's checking account on schedule. The authorisation lives inside each bank's own direct-debit system rather than in one standardised place.
- **Pix Automático:** launched by Banco Central do Brasil (BCB) on 16 June 2025 and mandatory for payer-side institutions since October 2025. The customer gives standardised consent once inside their bank app, charges pull bank-to-bank from the checking account, the BCB sets a uniform retry rule of up to three further attempts across a seven-day window, and disputes run through the MED (Mecanismo Especial de Devolução) rather than chargebacks.


Across Latin America, Juspay manages the full subscription lifecycle on these rails — pausing and resuming subscriptions, switching the linked payment method without interrupting service, and emitting real-time lifecycle webhooks — with automatic card updating handled through the networks' account-updater services.


## Frequently asked questions


These questions and answers are published on the Recurring Payments product page.


**How does Juspay improve subscription retention?**
Juspay improves retention with a real-time card updater that automatically refreshes payment information when cards expire, are replaced, or are lost or stolen, preventing payment failures and involuntary churn.


**What payment methods does Juspay support for subscriptions?**
Juspay supports frictionless sign-ups with cards and alternate payment methods, including local and alternative payment options.


**How does Juspay's smart retry feature work?**
Smart retries intelligently re-attempt failed transactions based on error codes, decline codes, region, time, user history, and custom rules, to maximise authorisation rates while keeping penalties and retry costs in check.


**What is Juspay's account updater feature?**
The account updater automatically updates card details every month to minimise declined transactions and ensure uninterrupted recurring payments, reducing the fees associated with declined transactions.


**What types of subscription businesses does Juspay support?**
Juspay supports all major subscription businesses, including streaming services, memberships, subscription boxes, pay-as-you-go models, and SaaS platforms, with seamless recurring revenue management.


**How does Juspay handle payment failures for subscriptions?**
Juspay uses dynamic retry strategies based on multiple parameters, including decline codes, PSP adapters for fallback options, and a transformation engine to standardise responses across multiple subscription engines.


**Can Juspay update card information on demand?**
Yes. Juspay offers both automatic monthly updates and on-demand updates via API, to proactively monitor card expirations and maintain seamless recurring payments.


## Contact


- **Website:** [juspay.io/contact](https://juspay.io/contact)
- **LinkedIn:** [linkedin.com/company/juspay-technologies](https://in.linkedin.com/company/juspay-technologies)
- **Twitter/X:** [@juspay](https://twitter.com/juspay)
- **Newsroom:** [juspay.io/newsroom](https://juspay.io/newsroom)