Manual Payment Tracking Eliminated with Stripe–Salesforce Automation
for a US Nonprofit

We installed the Stripe for Salesforce Platform app into the client's Salesforce sandbox org, followed by the required Stripe API extension package. The Stripe sandbox account connection was authorized using the Stripe API keys, and the Salesforce org authorization was completed within the platform. This two-step authorization establishes the secure channel through which Salesforce Flows can invoke Stripe Apex actions at runtime.

Webhook configuration was handled next: we registered the Salesforce-provided Stripe webhook URL in the Stripe dashboard, configured the Stripe account details, and enabled the specific webhook events needed for payment processing — including invoice.payment_succeeded and invoice.payment_failed. The API version was set correctly to match the installed Stripe package, which is a common point of failure when teams configure this independently. With webhooks enabled, Stripe can now push real-time payment events into Salesforce as Stripe Event records.

tripe App Installation, Authorization

Stripe App Installation

Webhook Configuration

We built the Opportunity Create Flow — named "Opportunity after flow stripe payment url generate and update – V12" — as a Record-Triggered Flow that fires when an Opportunity record is created. The flow first retrieves the Stripe account configuration and the related Salesforce Account details. It then checks the Opportunity stage and amount conditions to determine whether invoice generation should proceed. This conditional gate prevents test or placeholder Opportunities from triggering live Stripe actions unnecessarily.

The core logic handles the Stripe customer ID check: if the related Account already has a Stripe Customer ID stored, the flow retrieves the existing Stripe customer rather than creating a duplicate. If no Stripe ID exists, it creates a new Stripe customer and stores the resulting Customer ID on the Salesforce Account. From there, the flow creates the Stripe invoice, adds invoice items, finalizes the invoice, and writes the resulting Stripe Invoice ID and hosted Invoice URL back to the Opportunity record. Every step is handled inside Salesforce Flow using Stripe's published Apex actions — no external API calls or middleware required.

Opportunity Create Flow

Opportunity Create Flow

Opportunity Create Flow

The Opportunity Update Flow — "Opportunity after Update flow stripe payment url generate and update – V11" — handles the same invoice generation logic but fires on record update rather than creation. Separating these two triggers is the most critical architectural decision in the entire implementation. A single flow handling both create and update would fire on every field change to an Opportunity, creating a new Stripe invoice each time — which breaks both the Stripe account and the Opportunity record's invoice tracking within hours of going live.

The update flow includes additional validation: it checks whether the Opportunity already has a Stripe Invoice ID before deciding whether to create a new invoice or update an existing one. Stage and amount validation runs first. The Stripe customer existence check mirrors the create flow logic. From there, it creates or retrieves the Stripe customer, creates the invoice and invoice items, finalizes the invoice, and updates the Opportunity's Stripe Invoice ID and Invoice URL fields. This flow handles cases like amount changes after the initial Opportunity creation without producing orphaned invoices in Stripe.

Opportunity Update Flow

Opportunity Update Flow

The Payment Pending Reminder Flow — "Payment Link Created and Pending for 30 Days Sending email alert – V7" — is a scheduled-path flow that fires on Opportunity create or update, then waits 30 days from the transaction creation date before checking payment status. If the Stripe Payment Status field still shows unpaid or open at the 30-day mark, the flow sends a reminder email alert to the relevant stakeholder. This replaces the manual follow-up process entirely with a zero-touch, time-based automation.

One design decision we implemented specifically for this client: the flow includes separate email alert logic for Profit record types and Nonprofit record types on the Opportunity object. Nonprofits often have different communication requirements for payment follow-up — different email templates, different sender identities, different escalation paths. Building this as two distinct alert branches inside the same flow means both record types are covered without needing separate flows to maintain. The flow also updates the Opportunity stage to Closed Won automatically when payment is confirmed as completed.

30-day reminder email flow

The Stripe Event Payment Status Update Flow — "Update Opportunity status When Stripe event changes – V4" — is triggered by the creation of a Stripe Event record in Salesforce, which occurs when Stripe sends a webhook event to the org. The flow identifies the Stripe Event type, finds the related Opportunity record, and updates the Opportunity's Stripe Payment Status field to reflect the incoming event: Paid for a successful payment, Failed for a payment failure. This closes the feedback loop between Stripe and Salesforce entirely — no polling, no manual checking.

Sandbox validation covered all critical scenarios: Stripe Invoice ID generation, Invoice URL population on Opportunity records, Stripe Payment Status updates via webhook events for both payment.success and payment.failed event types, and the 30-day reminder email configuration. Each scenario was tested end-to-end in the Stripe sandbox environment before signoff. The implementation is structured so that production deployment requires only one additional step: installing the paid Stripe app in the production org. All four flows, custom fields, and webhook configurations migrate directly.

Stripe Event Payment Status Update Flow