--- title: Understand the subscription lifecycle slug: subscriptions/how-it-works excerpt: >- Learn how Pine Labs Online subscriptions transition through plan creation, mandate registration, pre-debit notifications, auto-debit execution, and terminal states. sidebar_order: 2 hidden: false sidebar_label: Subscription lifecycle metadata: title: Subscription Lifecycle — States & Status Flow | Pine Labs description: >- Understand subscription and plan lifecycle states including created, active, halted, paused, completed, expired, and cancelled. Learn state transitions for UPI AutoPay mandates and recurring debits. keywords: >- subscription lifecycle, plan lifecycle, subscription states, mandate states, UPI AutoPay flow, Pine Labs subscriptions robots: index --- ## Plan Life Cycle The figure below shows the life cycle of the Plan. The table below list the various statuses that our Plans can have during its life cycle. | Status | Description | | :------- | :------------------------------------------------------------------------------------ | | CREATED | When the Create Plan request is successfully created with a future start date. | | ACTIVE | When the plan is activated, i.e., when the scheduled start date and time are reached. | | INACTIVE | When the plan has expired. | *** ## Subscription \[Mandate Registration] Life Cycle The figure below shows the life cycle of the Subscription. The table below list the various statuses that our Subscription can have during its Mandate registration life cycle. [block:parameters] { "data": { "h-0": "Status", "h-1": "Description", "0-0": "CREATED", "0-1": "When the Create Subscription request is successfully received by Pine Labs Online.", "1-0": "EXPIRED", "1-1": "This state occurs when no response is received from the partner bank for the create subscription request within `4` hours.", "2-0": "INACTIVE", "2-1": "The mandate creation fails due to a failure response from the acquirer.", "3-0": "TRIAL", "3-1": "This state occurs when the mandate is successfully created by your customer. **Note**: Subscription billing will begin once the trial period ends. After the trial period, the mandate will transition to the `ACTIVE` state.", "4-0": "ACTIVE", "4-1": "Subscription is in an active state and can be presented to the customer.", "5-0": "PAUSED", "5-1": "This state occurs when the subscription is temporarily paused, and billing is currently on hold.", "6-0": "RESUMED", "6-1": "The subscription transitions to this state when either the merchant or the customer resumes it from a `PAUSED` or `HALTED` status.", "7-0": "UPDATING", "7-1": "This status occurs when the subscription details are requested for modification. **Note**: Once the customer provides consent, the subscription modification request will be processed, and the subscription will return to the `ACTIVE` state.", "8-0": "DEBIT FAILED", "8-1": "The subscription enters this state if the first debit execution request fails and the customer cannot be charged on the initial attempt for a billing cycle.", "9-0": "HALTED", "9-1": "After exhausting all retry attempts by both the merchant and Pine Labs Online, the subscription enters the `HALTED` state. No further actions can be performed while subscription remains in this state.", "10-0": "CANCELLED", "10-1": "The subscription is successfully cancelled after receiving a callback confirmation from the bank.", "11-0": "COMPLETED", "11-1": "Upon reaching the subscription's end period, the mandate transitions to this final state." }, "cols": 2, "rows": 12, "align": [ "left", "left" ] } [/block] *** ## Presentation Life Cycle The Presentation Life Cycle consists of two distinct flow types: 1. [Pre Debit Notification Flow](#pre-debit-notification) 2. [Customer Debit Flow](#customer-debit-notification)

Pre Debit Notification Flow

The figure below shows the life cycle of the Pre Debit Notification flow of Presentation. The table below list the various states of a Presentation. | Status | Description | | :--------- | :---------------------------------------------------------------------------------------------------------------------------- | | CREATED | When we have received the Subscription Notification request successfully. | | PENDING | When we successfully initiate a Pre-debit Notification. | | PAUSED | When the subscription is Paused. | | CANCELLED | When the subscription is Cancelled. | | NOTIFIED | When the notification is delivered successfully. | | FAILED | Pre-Debit Notification is unsuccessful, the system automatically retries delivery up to 10 times before marking it as Failed. | | PDN FAILED | Pre-Debit Notification has failed after all internal retries for a subscription. | ***

Customer Debit Flow

The figure below shows the life cycle of the Customer Debit flow of Presentation. The table below list the various states of a Presentation. [block:parameters] { "data": { "h-0": "Status", "h-1": "Description", "0-0": "CREATED", "0-1": "When the create presentation request is successfully received by Pine Labs Online. **Note**: You need to use our Presentation API only if notification is handled by Pine Labs Online.", "1-0": "PENDING", "1-1": "When we successfully initiate a Pre-debit Notification.", "2-0": "PAUSED", "2-1": "When the subscription is Paused.", "3-0": "CANCELLED", "3-1": "When the subscription is Cancelled.", "4-0": "FAILED", "4-1": "Pre-Debit Notification or customer debit fails, the system will attempt up to three retries—initiated either by the merchant or Pine Labs. After three unsuccessful attempts, the subscription status changes to `HALTED`. The merchant can then send a new notification and debit request. Once the debit is successful, the subscription returns to the `ACTIVE` state.", "5-0": "COMPLETED", "5-1": "When the debit is successful." }, "cols": 2, "rows": 6, "align": [ "left", "left" ] } [/block]