Connect Stripe to Salesforce

Sales and CS work in Salesforce. Billing lives in Stripe. Without a link, an AE does not know a renewal already paid, CS finds out about a failed card from an angry email, and the "MRR" field on the account is whatever someone last typed in.

• The account carries a live subscription status, plan, and MRR from Stripe, so the AE opens a renewal already knowing where it stands
• A failed payment opens a case routed to the CS queue with the dunning stage and the invoice link, days before a cancellation
• A closed-won opportunity can create the Stripe customer and subscription, so there is no rekeying and the IDs match from day one
• Every update is an ordered run log, so a wrong MRR number can be traced to the exact Stripe event that set it

The retention flow most teams turn on first.

A failed Stripe invoice opens a Salesforce case and updates the account

Triggered on the Stripe event, idempotent on the invoice ID plus attempt count.

1. 1Trigger: Stripe Event received for invoice.payment_failed, carrying customer, subscription, amount_due, attempt_count, and next_payment_attempt.
2. 2Resolve: find the Salesforce Account by Stripe_Customer_Id__c equal to the Stripe customer. If none, match on billing email and set the ID.
3. 3Idempotency: look for an open Case with Stripe_Invoice_Id__c equal to this invoice. If one exists, add a comment with the new attempt count instead of a second case.
4. 4Case: Salesforce Create Case, record type "Billing", subject "Payment failed for {plan}", priority by amount_due, linked to the Account and the Contact who is the billing owner.
5. 5Account update: set Payment_Status__c to "Past due" and Dunning_Stage__c to the attempt count.
6. 6Recovery: a later invoice.paid for the same invoice closes the Case as "Resolved" and sets Payment_Status__c back to "Current".

The starting map for the Stripe subscription to Salesforce Account step.

• Subscription and MRR. Status, plan, quantity, renewal date, and MRR on the account, updated on every subscription change. (Stripe to Salesforce)
• Payments and dunning. Paid invoices update payment status. Failed invoices open or update a CS case with the dunning stage. (Stripe to Salesforce)
• New customer from closed-won. A closed-won opportunity creates the Stripe customer and subscription from the quote lines, with an approval step first. (Salesforce to Stripe)
• Contact and billing details. Billing email, company name, and address stay aligned, with Salesforce as source of truth for the company record. (Either direction)

The same controls apply to this sync as to every other Neblex workload.

• Ordered run log. Every update is an event log with the Stripe event, the record it resolved to, and the fields it changed. Replay a run without re-sending downstream side effects.
• Approval steps. Creating a Stripe customer or subscription from Salesforce pauses for a named approver, so a mis-scoped deal never bills a customer.
• Scoped access. Stripe uses a restricted key with read on customers, subscriptions, and invoices, and write only where the create-from-CRM flow needs it. Salesforce uses a connected app limited to the objects in the map.
• Environments. Build against Stripe test mode and a Salesforce sandbox, then promote the same flow to production.