Skip to main content

Recharge Integration

Recharge Integration Why: Streamline your member management by connecting Recharge to automatically create member accounts and manage access based...

Written by Ken Truesdale

Platform 2 Guide — This article applies to the new platform. Looking for classic platform docs? Browse the Platform 1 collection.

Why: Streamline your member management by connecting Recharge to automatically create member accounts and manage access based on subscription events. This integration saves you time and ensures your members have seamless access to your content.

Navigate: App Station > Settings > Integrations > Recharge

Quick Start

  1. In Recharge, go to Tools and apps > API tokens and create an Admin API token.

  2. Enable the following permissions: Store information, Products, Plans, and Subscriptions. Leave all write scopes unchecked.

  3. Copy both the API Access Token and API Client Secret from the Admin API token details.

  4. In Member Kitchens, go to App Station > Integrations > Recharge, paste both credentials, and enable the integration.

  5. Configure webhooks in Recharge using the provided webhook URL for the following topics: subscription/created, subscription/cancelled, subscription/paused, subscription/activated, charge/paid, charge/failed, and charge/refunded.


Detailed Setup Instructions

1. Create the Admin API Token in Recharge

To start, you need to create an Admin API token in Recharge.

  • Navigate to Tools and apps > API tokens.

  • Click on Create Token and ensure you select Admin API token. Do not use a Storefront API token.

2. Set Minimum Permissions

Once you have created the token, set the necessary permissions:

  • Enable the following scopes:

    • Store information (store_info)

    • Products (read_products)

    • Plans (read_plans)

    • Subscriptions (read_subscriptions)

Leave all write scopes and other permissions unchecked to ensure proper functionality.

3. Copy Both Credentials

Open the Admin API token details and copy the following:

  • API Access Token: This is used by Member Kitchens to validate the connection and fetch products.

  • API Client Secret: This is used for verifying webhook signatures. Note that these are different values on the same token details page.

4. Enable the Integration in Member Kitchens

Now, head over to Member Kitchens:

  • Go to App Station > Integrations > Recharge.

  • Paste both the API Access Token and API Client Secret into the respective fields.

  • Click Enable Integration. Member Kitchens will validate the access token before saving.

5. Configure Webhooks in Recharge

Next, you need to set up webhooks in Recharge:

  • Use the Admin API access token as the X-Recharge-Access-Token when registering the webhook URL provided by Member Kitchens.

  • Register webhooks for the following events:

    • subscription/created

    • subscription/cancelled

    • subscription/paused

    • subscription/activated

    • charge/paid

    • charge/failed

    • charge/refunded

6. Add Product Mappings

To ensure that your products are correctly mapped:

  • Click Fetch Products on the Recharge integration page in Member Kitchens. This will load the Recharge product catalog into the mapping UI.

  • You can also send a test subscription webhook for automatic discovery or manually enter the subscription.external_product_id if needed. Note that legacy payloads may use recharge_product_id.

7. Understanding the Subscription Lifecycle

The integration handles the full subscription lifecycle, including:

  • Subscription Created: Creates a user if needed and grants access.

  • Charge Paid: Confirms active status or converts a trial to permanent access.

  • Subscription Cancelled: Revokes access.

  • Subscription Paused: Pauses access.

  • Subscription Activated: Re-activates access.

  • Charge Refunded: Revokes access.

  • Charge Failed: Flags the subscription as past due.

8. Logging and Monitoring

Every event processed by the integration is recorded in an audit log, allowing you to track all incoming webhook events for troubleshooting and monitoring.

Did this answer your question?