# Recharge + Stripe integration and analysis

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

## The question this stack can answer

Did subscription revenue change, or did more payments fail?

## What Hendrik reads from each source

- **Recharge:** Subscriptions, renewals, cancellations, and charges show the health of subscriber retention.
- **Stripe:** Payments, refunds, and disputes show whether money was collected after an order was placed.

## What you need to connect

- 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.

## Important limits

- 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.

## Illustrative example

### 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.

*About this example: Synthetic data · illustrative analysis · Hendrik only acts with the permissions you give it.*

- successful renewals (count, 28 days) (Recharge): 1,080 → 980
- successful payment amount (USD, 28 days) (Stripe): 102,000 USD → 94,000 USD

### What Hendrik checks

- **Subscription and charge timing:** Check Recharge subscription state, successful charges, plan changes, and order overlap with Shopify before comparing totals.
- **Payment and refund scope:** Check Stripe payment, refund, dispute, and balance-transaction dates. Establish an order-to-payment reference before reconciliation.
- **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.

### What Hendrik sees

Recharge successful renewals fell. Stripe successful payment amount fell.

### What to do next

Confirm processor coverage and payment relationships before acting on an apparent charge gap; reassess after those boundaries are established.

**Limit:** Recharge charges and Stripe payments must not be added or matched without a proven reference.

## Provider documentation

- [Recharge documentation](https://support.getrecharge.com/hc/en-us/articles/360044363954-Understanding-Recharge-Analytics)
- [Stripe documentation](https://docs.stripe.com/reports)

## Start with this stack

[Create a workspace and connect Recharge + Stripe](https://app.withhendrik.com/auth?mode=sign-up&acquisition_channel=marketing&return_to=%2Fonboarding%2Factivation&cta_location=integration_markdown&landing_page_id=combination-recharge-stripe&combination=recharge-stripe)