Recharge + Stripe

Did subscription revenue change, or did more payments fail?

Connect Recharge and Stripe to Hendrik. Compare Recharge subscription charges with Stripe payment, refund, and dispute data before interpreting a subscription revenue movement.

Start with this stackBook a founder demo

See Hendrik at work

Recharge + Stripe review

Previous: 1–28 January. Current: 29 January–25 February. Both periods contain 28 days. Monetary values use USD and all timestamps use UTC.

MetricPreviousCurrent
Rechargesuccessful renewals (count, 28 days)1,080980
Stripesuccessful payment amount (USD, 28 days)102,000 USD94,000 USD

What Hendrik checks

  1. Subscription and charge timing

    Check Recharge subscription state, successful charges, plan changes, and order overlap with Shopify before comparing totals.

  2. Payment and refund scope

    Check Stripe payment, refund, dispute, and balance-transaction dates. Establish an order-to-payment reference before reconciliation.

  3. Explain the divergence

    Recharge: successful renewals (count, 28 days) changed from 1,080 to 980. Stripe: successful payment amount (USD, 28 days) changed from 102,000 USD to 94,000 USD. Compare the timing and definitions before attributing one change to the other.

About this example Synthetic data · Illustrative analysis · Changes require your approval.

How Hendrik handles your data

Want Hendrik to answer this with your data?

Start with this stackBook a founder demo

One analysis, different integrations

What each integration adds

Connect your stack

Set up each integration in one workspace.

  1. Create your Hendrik account. Choose a workspace for your business.
  2. Connect your data. Use each integration’s setup instructions above. Availability and permissions are shown in your workspace.
  3. Ask your first question. Hendrik uses the available data and tells you when a comparison needs more history or more data.
Requirements and data limits

What you need

  • Use one explicit 28-day comparison window, time zone, market, and legal-entity scope before comparing values.
  • Connected Recharge account with comparable subscription, renewal, and cancellation definitions.
  • Connected Stripe account with payment, refund, and dispute data for the same legal entity.
  • Keep provider-specific definitions visible and use an identity or product mapping only where it is established for this workspace.

Keep these differences in mind

  • Subscription outcomes can overlap commerce and payment records; no campaign cohort or customer match is assumed.
  • Payments must not be added to storefront or marketplace revenue; transaction reconciliation needs a proven payment relationship.
  • Recharge charges and Stripe payments must not be added or matched without a proven reference.

Works better together

Find more combinations
  • Shopify
  • Google Ads
  • Recharge
  • Stripe

Are renewals and successful payments keeping up with Google Ads?

Connect Shopify, Google Ads, Recharge and Stripe to Hendrik. Separate acquisition delivery, store revenue, subscription renewals, and payment collection.

See Shopify + Google Ads + Recharge + Stripe
  • Shopify
  • Meta Ads
  • Recharge
  • Stripe

Are renewals and successful payments keeping up with Meta?

Connect Shopify, Meta Ads, Recharge and Stripe to Hendrik. Separate acquisition delivery, store revenue, subscription renewals, and payment collection.

See Shopify + Meta Ads + Recharge + Stripe
  • Shopify
  • TikTok Ads
  • Recharge
  • Stripe

Are renewals and successful payments keeping up with TikTok Ads?

Connect Shopify, TikTok Ads, Recharge and Stripe to Hendrik. Separate acquisition delivery, store revenue, subscription renewals, and payment collection.

See Shopify + TikTok Ads + Recharge + Stripe

Your data. Your next step.

Put Hendrik to work on your stack.

Create your account, choose your workspace and connect your data.

Start with this stackBook a founder demo
See plans and pricing