Shopify and Stripe: Why You Probably Cannot Use Stripe as Your Gateway

The answer nobody wants

"Shopify Stripe integration" is a search with a disappointing answer, and I would rather give you the disappointing answer in the first paragraph than sell you around it.

In countries where Shopify Payments is available, Stripe is not offered as a separate third-party payment gateway. Shopify's own documentation gives the reason directly: Stripe is Shopify Payments' banking partner, and all payment reporting and management takes place in your Shopify admin.

You are already on Stripe. You just do not have a Stripe dashboard, because the merchant-facing layer is Shopify's.

There is a narrow exception — merchants in a Shopify Payments region who cannot activate Shopify Payments for eligibility reasons can contact Shopify support to ask about standalone Stripe access. That is a support conversation about your specific account, not an integration you can plan around.

So if you came here to swap gateways, the project is usually over. What follows is what people actually need when they ask this question, because in my experience they are asking one of four different things.

Question 1: "I want lower fees"

Adding a third-party gateway is almost never how you get them.

Shopify applies third-party transaction fees on all third-party and alternate payment gateways, even when Shopify Payments is activated. That fee is a percentage that varies by plan, and it stacks on top of whatever the gateway itself charges you. So the comparison is not "Shopify's rate versus Stripe's rate" — it is "Shopify's rate" versus "the other processor's rate plus Shopify's third-party fee."

One structural exception: on the Shopify Plus plan, third-party transaction fees may be waived when Shopify Payments is activated, depending on your location. If you are on Plus and running a second gateway for a specific market, that is worth confirming with Shopify for your region rather than assuming either way.

The genuinely useful version of "lower fees" on Shopify is usually not a gateway change at all. It is: getting off manual card entry, reducing international-card mix by localising properly with Markets, and killing the chargebacks you are eating because your fulfilment communication is bad. Those move the number. Gateway shopping mostly moves it sideways.

Question 2: "I need a payment method Shopify Payments does not offer"

This one is legitimate and it is the actual use case for a third-party gateway. Shopify supports over a hundred credit card payment providers, and running one alongside Shopify Payments is a supported configuration — you keep Shop Pay and the local payment methods that come with Shopify Payments, and add the specific method you need on top.

The trade is the third-party fee on those transactions, and a second reconciliation surface. Both are fine if the payment method is genuinely unlocking revenue. Neither is fine if you added a gateway "for flexibility."

If you need something deeper than an available provider — a bespoke payment method, custom authorisation and capture timing — that is a payments app extension, and there are two gates: only approved partners can build on Shopify's Payments Platform, and building a custom payments extension is limited to eligible Shopify Plus merchants. Check eligibility before scoping anything.

Question 3: "I need Stripe for something that is not the storefront checkout"

This is the request I get most often, and it is the one where the answer is yes.

Plenty of businesses running a Shopify storefront also need Stripe for money that does not flow through a cart:

• Subscriptions and recurring billing managed outside the storefront — memberships, service retainers, SaaS-style plans sold alongside physical goods.
• B2B invoicing on net terms, where the order is placed in Shopify but the invoice is issued and collected separately.
• Marketplace or multi-vendor payouts through Stripe Connect, where the storefront takes the order and a second system splits the money.
• Deposits, quotes and custom orders — high-ticket, made-to-measure or freight-quoted items where the final amount is not known at the time of order.

These are integrations, not gateway swaps, and they are perfectly buildable. The architecture is always the same shape: Shopify owns the order, Stripe owns that payment, and a small service keeps them consistent.

The rules I hold on those builds:

One system owns each payment. A payment that both Shopify and Stripe think they own is a double charge waiting for a race condition. Decide per payment type, write it down, and never let the two paths overlap.

Webhooks must be idempotent. Both platforms retry. A webhook handler that creates a record without checking whether it already exists will, on a bad day, create it four times. Key on the event id, store what you have processed, and make replays free.

Reconcile against the order, not the total. Which brings me to the fourth question.

Question 4: "The numbers do not match"

This is the least glamorous and most valuable work in this whole area, and it applies whether you are on Shopify Payments or a third-party gateway.

Your Shopify order totals will never equal your payout amounts, and the reasons are all boring:

• Payouts are batched on a schedule and cross day boundaries, so a payout contains orders from more than one reporting day.
• Processing fees are deducted from the payout, not from the order.
• Refunds land in a different payout than the original charge, often in a different month.
• Chargebacks, reversals and their fees appear as separate transactions with their own timing.
• Multi-currency orders settle at a conversion rate applied at settlement, not at checkout.
• Gift cards, store credit and third-party financing mean part of an order total never touches the processor at all.

Finance teams see the gap, assume something is wrong, and ask engineering to explain it. The deliverable that ends that conversation forever is a reconciliation table, not a dashboard: one row per payout, joined to its constituent transactions, joined to Shopify orders, with an explicit column for every deduction. Anything that does not reconcile gets a reason code.

My stack for this is deliberately dull — export the payout data and the order data, join them in Python or DuckDB, and produce a small table. It is the same approach I use for custom Shopify reporting, and for the same reason: the answer is a table and three sentences, not a BI tool nobody logs into.

Build it once, run it monthly, and you convert a recurring argument into a lookup.

The short version

• In Shopify Payments countries, Stripe is not available as a separate gateway, because it is Shopify Payments' banking partner. You are already on it.
• Third-party transaction fees apply to third-party gateways even with Shopify Payments active. Adding a gateway rarely reduces total cost.
• Custom payments extensions are approved-partner and Plus-gated. Confirm eligibility before scoping.
• The real Shopify-plus-Stripe builds are subscriptions, invoicing, marketplace payouts and deposits — money that does not go through the storefront cart.
• One system owns each payment. Webhooks are idempotent. Reconcile per payout, with a reason code for every gap.

Related services

Payment integrations, custom apps and Admin API work sit under Shopify expert development. Checkout-side customisation has its own constraints — see Shopify checkout extensibility. For B2B net terms and company-level payment configuration, see Shopify B2B: company accounts, catalogs and price lists.

I build the integrations around Shopify's payment layer and the reconciliation that keeps finance from having to guess. See [Shopify expert development](/shopify-expert) or [hire a Shopify developer](/hire-shopify-developer).

Direct: [WhatsApp +55 11 98851-2788](https://wa.me/5511988512788) · [contato.matheusabrahao@gmail.com](mailto:contato.matheusabrahao@gmail.com)