> ## Documentation Index
> Fetch the complete documentation index at: https://docs.abconvert.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Recharge Integration

> Connect Recharge to validate your store, register subscription webhooks, and attribute eligible subscription lifecycle and renewal outcomes to ABConvert tests.

<Warning>
  **Pre-release.** This guide applies when the Integrations hub is enabled for your ABConvert account. Connect only a Recharge store that belongs to the Shopify store in ABConvert.
</Warning>

Use Recharge when a checkout test affects a subscription offer or when you need subscription lifecycle and renewal outcomes alongside ABConvert test results. ABConvert validates the Recharge store, registers required webhooks, and queues a limited backfill.

## Configure Recharge and ABConvert

<Steps>
  <Step title="Prepare Recharge credentials">
    Create the Recharge API token and client secret required by your Recharge account. Store them securely until you paste them into ABConvert. Do not share them in a test name, note, or support ticket.
  </Step>

  <Step title="Connect the matching store">
    In **Integrations**, open **Recharge** and paste the API token and client secret. ABConvert checks that the Recharge store matches your connected Shopify store before saving encrypted credentials.
  </Step>

  <Step title="Allow webhook registration and backfill">
    After connection, ABConvert registers or repairs its required Recharge webhook topics and queues a best-effort backfill. A successful connection confirms credential and registration health; it does not prove a subscription lifecycle event was delivered.
  </Step>

  <Step title="Verify a real lifecycle event">
    Use a safe subscription test flow. Confirm a signed Recharge lifecycle or charge event reaches ABConvert and is attributed to an eligible test before relying on renewal or churn reporting.
  </Step>
</Steps>

## What Recharge integration covers

ABConvert processes subscription creation, activation, updates, pauses, cancellations, skips, paid charges, failed charges, and refunds when Recharge delivers a valid webhook. It can attribute subscription outcomes back to eligible checkout-test assignments.

ABConvert reads Recharge plans already owned by your store for subscription offers. It does not create plans or change recurring prices for you.

## Use cases

* **Measure subscription conversion:** compare which test group creates or activates more subscriptions after a checkout-test exposure.
* **Measure renewal quality:** compare paid renewals, failed charges, cancellations, and refunds by the originating test group.
* **Test an existing offer:** offer a plan your store already owns, then use lifecycle outcomes to evaluate the checkout change.

## Things to know

* A connection health check is not lifecycle delivery proof. Verify a real signed vendor delivery in a safe test environment.
* Backfill is limited to relevant subscription history after the earliest active checkout test. It is not a full import of every historical subscription or charge.
* **Test and repair** can register missing webhook endpoints. Use it only when you intend to repair the current Recharge connection.
* Disconnecting revokes stored credentials and attempts to remove ABConvert-managed Recharge webhooks. A provider-side deletion can fail, leaving an inactive endpoint that no longer accepts ABConvert ingestion.