> 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/prepaid-subscriptions/cancellation-of-prepaid-subs.md). # Cancellation of Prepaid Subs ## Cancellation of Prepaid Subs ## Introduction While previously the cancellation of an active Prepaid subscription required reaching out to Chord to handle, this functionality has now been surfaced within the admin and can be completed without any need to reach out to \***.** \*Cancelling a prepaid subscription via this flow will not only cancel the prepaid, but will also cancel the corresponding subscription as well as initiate a prorated refund (when directed). ## Cancellation Steps Each prepaid subscription will now have a `Cancel Prepaid Subscription` button surfaced within the prepaid details. Click this button to kick off the cancellation. ![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-a779a39c6c6363cc566c6073173046a64436de7b%2Fcancellation-of-prepaid-subs-1.png?alt=media) Once clicked, a modal will populate with **3 potential options:** * `No refund` - cancel the prepaid subscription without accounting for any refund or fulfilled installments ![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-f094260df0250ea5c346011a3797678a3378a05f%2Fcancellation-of-prepaid-subs-2.png?alt=media) * `Refund as store credit`- select this option if you would like to issue *store credit* for any of the remaining unfulfilled prepaid installment orders. (As a note, the store credit will be issued to the **purchaser**). * *As show, a drop-down will appear allowing for the selection of the number of installments to refund. This list will not exceed the maximum number of installments allowed for refund (i.e. unfulfilled installments).* ![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-21fcade5ed096dc92404dc64790dc32892eeef17%2Fcancellation-of-prepaid-subs-3.png?alt=media) * `Refund to original payment method`- select this option if you would like to issue a refund to the original payment method (i.e. credit card) that was used to complete the original subscription creation order. * *As show, a drop-down will appear allowing for the selection of the number of installments to refund. This list will not exceed the maximum number of installments allowed for refund (i.e. unfulfilled installments).* ![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-3dd62b2f49702417a6420b6ecc4f3b2444b196d1%2Fcancellation-of-prepaid-subs-4.png?alt=media) * Select `Cancel Subscription` * Once selected, the parent **Prepaid Sub,** connected child sub and the original order will be canceled/have a refund applied. ![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-d1cf1306ed5f43ab3b0bb95860c6a25dc6273232%2Fcancellation-of-prepaid-subs-5.png?alt=media) ![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-67eaa28c4b4a2924768998f1f511c51171b4d507%2Fcancellation-of-prepaid-subs-6.png?alt=media) ![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-25d3960f26961d9444cc4e6d409756cc01720e75%2Fcancellation-of-prepaid-subs-7.png?alt=media) * **NOTE:** When a refund to the original payment method is generated and the refund applied, make sure that a corresponding adjustment is made at the order level to ensure that the order is not in a `Balance Due` or `Credit Owed` state. --- # 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/prepaid-subscriptions/cancellation-of-prepaid-subs.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.