How to Connect Stripe to Salesforce: Options and Costs for NZ Businesses

Money lives in Stripe, relationships live in Salesforce, and the gap between them is where awkward customer conversations come from. There are four realistic ways to close it: Stripe's official Salesforce Platform app, a Zapier or Make automation, an AppExchange payment app, or a custom build. Here is the full option set with verified mid-2026 numbers.

Why Bother Connecting Them

When did that customer last pay you? Is the subscription they are calling about active, past due, or cancelled? If answering means opening the Stripe dashboard in another tab, then every salesperson and every service agent is working half-blind. The predictable costs: renewal conversations that open with an apology, failed payments nobody chases until the customer churns, and revenue reporting assembled by hand at month end.

A connected org flips those into workflow. A failed payment becomes a task on the account owner's list the same morning. A new subscription shows on the account before the welcome email lands. That is the practical prize, and for most NZ small businesses it costs less than one lost customer a year.

The Four Realistic Options

Option	Verified cost (as at July 2026)	Best for
Stripe for Salesforce Platform (official app)	Stripe processing fees apply; the app is configured, not bought per feature	Subscription and billing businesses that want Stripe data living in Salesforce
Zapier	Free (100 tasks/mo, 2-step) · Professional from US$19.99/mo billed annually	Simple event-driven flows, fast start
Make	Free (1,000 credits/mo) · Core from US$9/mo	The same flows, cheaper, more technical
AppExchange payment apps (Blackthorn, Chargent)	Quote-based; Blackthorn does not publish pricing	Taking and managing payments inside the Salesforce UI
Custom build (Stripe API)	Your development time	Requirements the tools above cannot meet

Pricing sources: Stripe NZ pricing, Zapier pricing, Make pricing, Blackthorn pricing page, all checked July 2026.

Stripe's Official App: Powerful, Not Turnkey

Stripe for Salesforce Platform is Stripe's own product, published on the AppExchange. It mirrors Stripe billing objects (customers, subscriptions, invoices) as custom objects in Salesforce, with sync running in real time or on a schedule. On top of that data layer it exposes Stripe API actions to Salesforce Flow Builder and Apex, which is how you process and reconcile payments, run the subscription lifecycle from Salesforce, and convert negotiated quotes into active Stripe subscriptions.

The honest framing: this is an integration builder, not a plug-and-play app. Stripe describes it as working best on core clouds (Sales, Service, Revenue, Commerce, Experience), and getting value from it means someone configures flows around your billing model. For a subscription business that lives in both systems, it is the deepest option and our usual recommendation; just budget configuration effort, not only licence dollars.

Zapier and Make: The Event-Driven Route

Zapier's Stripe connector covers the moments that matter: new payment, new customer, failed payment, checkout session completed, invoice payment failed. Each can create or update Salesforce records or start a flow. Make's Stripe modules go further on the action side (41 actions, including creating customers and payment intents) at a lower price point.

The patterns we set up most for NZ SMBs:

• Failed payment creates a Task for the account owner, due today, with the invoice details attached.
• New payment updates the Opportunity or Account, so "did they pay?" is answered on the record.
• Checkout completed creates or matches a Contact, so online buyers do not live outside the CRM.

Limits are structural: one event at a time, no historical backfill, no payments UI inside Salesforce. For that, look at the next option.

AppExchange Payment Apps

Apps like Blackthorn and Chargent put the payment experience itself inside Salesforce: payment fields on records, payment links from an Opportunity, virtual terminal entry, with Stripe as one of the supported gateways (Blackthorn describes support for more than 120). They suit teams that take payments over the phone or invoice from Salesforce and want staff never to leave it. On cost, expect a sales conversation: as at July 2026, Blackthorn's pricing page lists no figures and directs you to its sales team, so get quotes in writing and compare against the official app plus configuration.

Custom Builds: For the Genuinely Unusual

Stripe's API and webhooks can drive any shape of integration, and sometimes that is warranted: marketplace models, complex revenue recognition, or multi-entity setups. It is also the most expensive option to build and to keep. We treat it as the route of last resort after the packaged options have genuinely been exhausted, which is less often than development quotes imply.

What Stripe Itself Costs in NZ

Whichever integration route you choose, Stripe's own fees sit underneath it. As at July 2026, Stripe's published NZ pricing is 2.65% + NZ$0.30 per successful domestic card charge, 3.5% + NZ$0.30 for international cards, an additional 2% where currency conversion applies, and 0.7% of volume for Stripe Billing on the pay-as-you-go plan. Disputes cost NZ$25. If your integration business case involves moving more payments through Stripe, put these numbers in it.

The Edition Trap: Check This Before You Buy Anything

Every route above depends on Salesforce API access. Starter Suite has none, which rules out most integration tools entirely; on Pro Suite, API access is a paid add-on; from Enterprise Edition it is included. Our edition guide and NZ pricing guide cover the upgrade maths. Whatever you choose, confirm edition compatibility with the vendor in writing first.

What We Have Learned Building Stripe Integrations

Having recently delivered Stripe integrations for our own clients, three lessons repeat:

1. Model the billing lifecycle before touching tools. List the events that matter (trial started, payment failed, plan changed, cancelled) and what Salesforce should do about each. The tool choice usually becomes obvious from that list.
2. Pick one owner for the customer record. Decide up front whether Salesforce or Stripe creates customers, and make the other side match, not create. Most sync pain we see is two systems both believing they are in charge.
3. Treat failed payments as workflow, not data. A synced "past due" status nobody acts on changes nothing. The integrations that pay for themselves route failures to a human with a deadline.

When Not to Integrate (Yet)

• Payment volume is small and simple. A dozen invoices a month, no subscriptions? Checking the Stripe dashboard weekly may honestly be fine for now.
• Your billing model is about to change. Integrations encode the model; wiring one to a model you are replacing doubles the work.
• Your CRM data is dirty. Payment data attached to duplicate accounts makes reconciliation worse, not better. Clean up first.

How We'd Choose

• Simple needs, want value this week: Zapier or Make, starting with the failed-payment task flow. Under NZ$40 a month.
• Subscription business, both systems central: the official Stripe app, configured around your lifecycle.
• Team takes payments inside Salesforce: an AppExchange payment app; get written quotes.
• Also juggling accounting sync: read our Xero integration guide; payments and accounting decisions are better made together.

Frequently Asked Questions

How do I connect Stripe to Salesforce? Four realistic routes: Stripe's official app for Salesforce Platform (an integration builder using Flow and Apex), an automation platform like Zapier or Make for event-driven flows, an AppExchange payment app such as Blackthorn or Chargent, or a custom build on Stripe's API. The right one depends on your billing model, volume and Salesforce edition.

Is there an official Stripe Salesforce integration? Yes. Stripe publishes "Stripe for Salesforce Platform" on the AppExchange. It brings Stripe billing objects into Salesforce as custom objects, supports processing and reconciling payments, managing the full subscription lifecycle, converting quotes into subscriptions, and syncing Stripe data in real time or on a schedule, driven through Salesforce Flow Builder and Apex.

How much does a Stripe Salesforce integration cost? Stripe's processing fees apply regardless of route: as at July 2026, NZ pricing is 2.65% + NZ$0.30 per domestic card transaction and 3.5% + NZ$0.30 for international cards, plus 2% for currency conversion. On top of that, budget for your chosen tool: Zapier from free to about US$20 a month, AppExchange payment apps by quote, or build time for the official app.

Can Zapier connect Stripe and Salesforce? Yes. Zapier's Stripe triggers include new payment, new customer, failed payment, checkout session completed and invoice payment failed, which can create or update Salesforce records or start flows. As at July 2026, Zapier's free plan covers 100 tasks a month with two-step Zaps, and paid plans start at US$19.99 a month billed annually.

Which Salesforce editions can integrate with Stripe? Every serious route depends on Salesforce API access. Starter Suite has no API access, on Pro Suite it is a paid add-on, and from Enterprise Edition it is included. Stripe notes its official app works best with core clouds such as Sales, Service, Revenue, Commerce and Experience Cloud. Confirm compatibility before you commit.

---

SaaSKool designs and builds Salesforce integrations for NZ and AU businesses: payments, accounting, websites and the systems in between. Want a second pair of eyes on your billing stack? Start with the free health check.