> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/chord-oms/chord-oms-overview/subscriptions/recurring-prepaid-subscriptions.md). # Recurring Prepaid Subscriptions ### Introduction Chord allows your customers to purchase and subscribe to a prepaid recurring subscription . ### What is a Recurring Prepaid Subscription? A recurring prepaid subscription is where the purchaser (customer) subscribes to a product /s by making upfront payments for the subscription on a recurring cyclical billing period basis. The customer will make a payment at checkout for the subscription for the first billing period. Then once all subscription installments for that billing period have been fulfilled, the subscription will automatically renew and the customer will be charged again for the next period. For example, a customer susbcribes to a 3 month prepaid subscription. This means the customer will prepay for the 3 months upfront. Their product will be fulfilled once every month, and once all products for the first 3 months have been fulfilled. The subscription will renew and the customer will prepay for the next 3 months. Not to be confused for [prepaid gift subscriptions](https://docs.chord.co/prepaid-gift-subscription) where the subscription completes after the first billing period. ### Visual Flow ![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-ddb867c36eb01a8f009dcd7854897df8359c636f%2Frecurring-prepaid-subscriptions-1.png?alt=media) The purchaser chooses a recurring prepaid subscription and specifies the installment count( the number of subscription installments to be fulfilled) and interval of fulfillment (how frequent and installment should be fufilled). For example an installment count of 3 and an interval of 3 months, means a subscription installment will be fulfilled once every month. The purchaser is then directed to Checkout, as the recurring subscription skips the Cart, using the "Buy Now" flow, and is prepaid in full in a single transaction. As such, no other items other than prepaid subscription items can be added to the order. When the order is complete, the purchaser receives an email to confirm their subscription. Then every month for the next 3 months the purchaser will recieve their subscription installments. Then once all prepaid installments have been fulfilled and the customer is due for their next installment, they will be charged for the next 3 months and the cycle will repeat until the customer cancels their susbcription. ### What is a Billing Period and How does it work? A Billing Period is a recurring fixed length of time where the customer will be charged for subscribing to a recurring prepaid subscription. ![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-7ef50978456f7f3e99c3b941ab0731d455945303%2Frecurring-prepaid-subscriptions-2.png?alt=media) *The diagram further illustrates the above as the following example:* As a customer I have subscribed to a $90 subscription where I will get billed every 3 months. Within that 3 month billing period, I will receive 1 subscription installment every month. After that 3 month period is up, I will be charged $90 again to cover the next 3 months, where I will receive 1 subscription installment per month within that 3 month period and so on. The billing period is configured on the backend, and this billing period is what will set the schedulder to issue a renewal payment to a customer. So an installment count of 3 and an interval of 1 month will then mean a subscription will have a 3 month billing period. So following the example above, the recurring subscription will have a 3 month billing period where the customer will be charged $90 upfront and they will recieve an installment once a month. ### Recurring Prepaid Subscription Order ![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-5854ec38f546bd33c77e72e412213a63128a3f4e%2Frecurring-prepaid-subscriptions-3.png?alt=media) On the Stripe checkout page under the product description, we clearly communicate to the customer what they are signing up for, for how long, and the renewal amount which they can confirm before checking out. This description is customizable in the OMS using the environment variable: **STRIPE\_PREPAID\_SUBSCRIPTION\_CONSENT\_MESSAGE.** ### OMS View Prepaid subscriptions can be viewed in the OMS under the Subscriptions/Prepaid subscriptions tab. ![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-bdfb4ba3beb84e126b203a41cdc9ae87dfa0e2a5%2Frecurring-prepaid-subscriptions-4.png?alt=media) When a prepaid subscription record has been clicked into, this will open a more detailed description of the subscription. The fulfilled installments, total installments, fuflfilled total and purchased total all reset every billing period. ![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-01d3262725f1d27ddd6248e231dbd148b8895a74%2Frecurring-prepaid-subscriptions-5.png?alt=media) ![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-dc3863c897a36b41d5858f162d7a4bba7e1e9439%2Frecurring-prepaid-subscriptions-6.png?alt=media) ### Recurring Prepaid Subscription Modifications **Updating a subscription** Once a prepaid subscription has been purchased, the only modifications or updates that can be made to the subscription is the shipping address. As of now the customer will have to contact customer support to do this as this can only be done in the OMS. **Canceling a subscription** A recurring prepaid subscription can be cancelled at an time within a billing period. The system will issue a refund in the form of a store credit to refund unfilfilled subscription installments. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.chord.co/chord-oms/chord-oms-overview/subscriptions/recurring-prepaid-subscriptions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.