Skip to main content
Remark’s Recharge integration lets agents look up subscription details and perform supported subscription actions during shopper conversations.

​
What the integration does

Once connected, Remark can use Recharge to:
  • Find a shopper’s subscriptions
  • Find upcoming queued charges
  • Skip an upcoming charge
  • Cancel a subscription
  • Reschedule the next charge date
  • Change a subscription shipping address
  • Change a subscription delivery frequency
Remark uses Recharge as the system of record. Subscription changes are made in Recharge, and Recharge’s rules still determine whether a subscription, charge, address, or schedule change is valid.

​
Before you start

You need:
  • Access to Settings > Integrations in the Remark dashboard
  • Your Recharge admin domain
  • A Recharge Admin API token with the scopes required for your actions below, not a Storefront API token
Your Recharge admin domain should look like:
Only the Recharge store owner has API token access by default. The owner can grant access to staff and must accept the API Terms of Service before the first token can be created. To create the token in the Recharge merchant portal:
  1. Open Tools & apps > API tokens.
  2. Select Create new in the Admin tokens section.
  3. Enter a token name and contact email.
  4. Select Read access or Read and Write access for the permissions your actions need, using the scopes below. Leave unused permissions at No access.
  5. Select the checkbox in Terms of service.
  6. Select Save.
See Recharge’s Admin API token instructions for account access and current token settings.

​
Required token scopes

Recharge groups address access under customers and charge access under orders. Use these API scopes, rather than looking for separate address or charge permissions: Grant only the scopes needed for your enabled actions and verification method. Read-only actions do not need write scopes. These actions do not require payment-method, checkout, or External Tokens access.

​
Connect Recharge

  1. Open Settings > Integrations in the Remark dashboard.
  2. Find Recharge.
  3. Select Connect.
  4. Enter your Recharge Domain.
  5. Enter your Recharge API token.
  6. Select Connect.
Remark tests the credentials before saving the integration. If the test fails, the integration is not installed. The connection test checks customer read access. A successful connection does not confirm the permissions needed to change subscriptions or charges.

​
Add Recharge actions to an intent

Connecting Recharge makes Recharge actions available to your workspace. To let agents use those actions in conversations, add them to the relevant intent, such as a subscription management or recurring order playbook. In that intent:
  1. Add the Recharge actions the agent should be allowed to use.
  2. Write matching criteria for shoppers asking about subscriptions, upcoming charges, skips, cancellations, address changes, or delivery cadence.
  3. Tell the agent which shopper details to collect before using Recharge.
  4. Test the intent in the Playground before enabling it for live conversations.

​
Customer verification

Recharge actions require the shopper’s email address plus either:
  • Last name
  • Shipping ZIP or postal code
Remark verifies the shopper against Recharge before returning subscription data or making changes. If last name is provided, it must match the Recharge customer record. If ZIP or postal code is provided, it must match a shipping address attached to one of the shopper’s Recharge subscriptions. For actions that modify a subscription or charge, Remark also verifies that the subscription ID or charge ID belongs to the verified customer.

​
Supported actions

Use Get Recharge subscription information before actions that need a subscription ID. Use Get upcoming Recharge charges before skipping a specific charge. Confirm the items on the charge before skipping it. The cancellation action does not issue a refund. These actions do not update payment methods.

​
Playground behavior

Read-only actions can return Recharge data in the Playground. Actions that change Recharge data are no-ops in the Playground. The Playground shows what would have happened without cancelling, skipping, rescheduling, or updating a live subscription. A successful Playground run does not verify write permissions in Recharge.

​
Troubleshooting

​
Domain validation fails

Confirm that the domain ends in .admin.rechargeapps.com. Use the Recharge admin domain, not your public storefront domain.

​
API token is rejected

Confirm that the token came from Tools & apps > API tokens in Recharge and has not been revoked or rotated. If your team created a new token, open More options on the Recharge integration, select Manage connection, and enter the new token.

​
Customer cannot be verified

Confirm that the shopper email exists in Recharge and that the provided last name or shipping ZIP matches Recharge. For ZIP verification, the shopper must have at least one subscription address in Recharge.

​
Subscription action fails

Use Get Recharge subscription information to confirm the subscription ID belongs to the verified customer. For charge skips, use Get upcoming Recharge charges to confirm the charge is queued and belongs to the shopper. If reads work but changes fail, review the token’s write scopes against the table above. Do not grant unrelated permissions to resolve an error.

​
Recharge rejects the change

Recharge can reject changes because of subscription status, charge timing, address requirements, product rules, or store configuration. Review the subscription directly in Recharge, then retry once the Recharge-side issue is resolved.
Need help connecting Recharge or testing subscription actions? Contact support@remark.ai.