> For the complete documentation index, see [llms.txt](https://learn.fueled.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.fueled.io/integrations/sources/recharge-payments.md). # ReCharge Payments Our ReCharge Payments integration is primarily designed to track the following server-side events: * Subscription Started * Subscription Paused * Subscription Canceled Our Shopify and BigCommerce Apps also track re-billing events triggered by ReCharge Payments out-of-the-box. The value of our ReCharge Payments integration is that it allows you to track the creation and updates to ReCharge subscriptions. *(Detailed event schema documentation coming soon.)* ### Use Cases * Analyze customer journies that lead to subscription sign-ups in Google Analytics, MixPanel or Amplitude. * Measure one-time purchases from shoppers with active subscriptions * Trigger email and SMS campaigns when customers pause or cancel their subscriptions. --- # 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://learn.fueled.io/integrations/sources/recharge-payments.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.