Stripe integration
Connect Stripe to Hendrik.
Hendrik reads Stripe balance transactions, charges, payment intents, refunds, subscriptions, invoices, and disputes so you can separate payment collection from storefront orders.
Questions Hendrik can help answer
- Do payment and refund facts explain a storefront gap?
- Did disputes or failed payments change the commercial result?
- Is a payment to order match confirmed or only an aggregate comparison?
Stripe + Shopify example
Compare payment and storefront refund movement
Same 30-day USD windows
| Metric | Previous | Current |
|---|---|---|
| ShopifyStore refund value | US$8,000 | US$13,500 |
| StripeProcessor refund amount | US$7,600 | US$9,100 |
| StripeDisputes opened | 8 | 23 |
What Hendrik checks
Check source scope
Confirm whether Shopify payments in scope are processed by this Stripe account.
Compare dates
Keep refund creation and payment dates visible.
Qualify matching
Do not assert transaction reconciliation without a proven payment reference.
About this example Synthetic data · Illustrative analysis · Changes require your approval.
How Hendrik handles your dataWant Hendrik to answer this with your data?
Your connected data
What Hendrik reads from Stripe
Use Stripe with WooCommerce or Shopify and ad data to see whether demand weakened or more payments failed, refunded, or became disputed.
- Charges and payment intents
- Processor payment state.
- Refunds
- Processor refund records.
- Disputes
- Dispute data.
- Balance transactions
- Processor balance movement records.
- Invoices and subscriptions
- Subscription billing data.
Setup and access
Setup and access for Stripe
- Setup
- When enabled, sign in with Stripe and confirm the account and live or test mode.
- Permissions
- Stripe Apps OAuth permission (`stripe_apps`). Hendrik uses the connected account to read payment data.
- Supported accounts
- One Stripe account and mode.
- Available history
- The current product configuration defaults to 90 days. Hendrik shows the actual coverage after the first sync.
- Data refresh
- Configured data streams run from hourly to every 6 hours. Hendrik shows the published freshness for each source after sync.
- Setup time
- Stripe starts its initial sync after authorization, account selection, and data checks. The duration depends on the selected account and history.
- Can Hendrik make changes?
- Connecting reads Stripe data. It does not create charges, refunds, subscriptions, or payment changes.
- Integration availability
- Your workspace shows Connect or Request access for your account.
Requirements and data limits
What you need
- Confirm the customer’s Stripe account and currency scope.
- State the payment, refund, dispute, or balance date being used.
- Establish an order-to-payment relationship before transaction reconciliation.
Keep these differences in mind
- Stripe means customer payment data, not Hendrik billing data.
- Stripe amounts must not be added to commerce revenue as extra revenue.
- Payment settlement and storefront order dates can differ.
- This is an aggregate comparison, not a transaction-level reconciliation.
Your data. Your next step.
Put Hendrik to work on your stack.
Create your account, choose your workspace and connect your data.
See plans and pricing