# Stripe + Salesforce integration and analysis

Connect Stripe and Salesforce to Hendrik. Compare Salesforce opportunity progression with Stripe payment and dispute data without assuming a deal-to-payment join.

## The question this stack can answer

Are won Salesforce deals turning into Stripe payments?

## What Hendrik reads from each source

- **Stripe:** Payments, refunds, and disputes show whether money was collected after an order was placed.
- **Salesforce:** Leads, opportunities, stages, and campaign membership show whether paid leads become qualified opportunities.

## What you need to connect

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

## Important limits

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

## Illustrative example

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

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

- successful payment amount (USD, 28 days) (Stripe): 102,000 USD → 94,000 USD
- Won deals · close date in period (count, 28 days) (Salesforce): 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.

### What Hendrik sees

Stripe successful payment amount fell. Salesforce won deals fell.

### What to do next

Use payment data to qualify the pipeline view before an acquisition action; reassess after relationship and date boundaries are documented.

**Limit:** Opportunity amount and Stripe payment amount are different measures, not additive revenue.

## Provider documentation

- [Stripe documentation](https://docs.stripe.com/reports)
- [Salesforce documentation](https://help.salesforce.com/s/articleView?id=sf.reports.htm)

## Start with this stack

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