Stripe
Payments, refunds, and disputes show whether money was collected after an order was placed.
How to connect StripeStripe + Salesforce
Are won Salesforce deals turning into Stripe payments?
Connect Stripe and Salesforce to Hendrik. Compare Salesforce opportunity progression with Stripe payment and dispute data without assuming a deal-to-payment join.
See Hendrik at work
Stripe + Salesforce review
Previous: 1–28 January. Current: 29 January–25 February. Both periods contain 28 days. Monetary values use USD and all timestamps use UTC. Reported lead volume and CRM wins describe different cohorts. Stripe adds collected payment data. Compare those stages without treating them as a joined funnel.
| Metric | Previous | Current |
|---|---|---|
| Stripesuccessful payment amount (USD, 28 days) | 102,000 USD | 94,000 USD |
| SalesforceWon deals · close date in period (count, 28 days) | 34 | 29 |
What Hendrik checks
Payment and refund scope
Check Stripe payment, refund, dispute, and balance-transaction dates. Establish an order-to-payment reference before reconciliation.
Opportunity and campaign definition
Check Salesforce record type, stage history, campaign membership, and identity coverage before using opportunity movement.
Explain the divergence
Stripe: successful payment amount (USD, 28 days) changed from 102,000 USD to 94,000 USD. Salesforce: Won deals · close date in period (count, 28 days) changed from 34 to 29. 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 dataWant Hendrik to answer this with your data?
One analysis, different integrations
What each integration adds
Salesforce
Leads, opportunities, stages, and campaign membership show whether paid leads become qualified opportunities.
How to connect SalesforceConnect your stack
Set up each integration in one workspace.
- Create your Hendrik account. Choose a workspace for your business.
- Connect your data. Use each integration’s setup instructions above. Availability and permissions are shown in your workspace.
- 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 Stripe account with payment, refund, and dispute data for the same legal entity.
- Connected Salesforce org with agreed lead, opportunity, and stage definitions.
- 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
- Payments must not be added to storefront or marketplace revenue; transaction reconciliation needs a proven payment relationship.
- CRM campaign and opportunity records require an established identity relationship before attribution claims.
- Opportunity amount and Stripe payment amount are different measures, not additive revenue.
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