Every Shopify merchant hits this decision eventually, usually while staring at the Settings > Payments screen for the first time or while reconciling a statement that doesn't quite match expectations. The pitch for Shopify Payments is straightforward: it's built in, it avoids an extra fee, and it's the path of least resistance. The pitch for a third-party gateway is usually about something Shopify Payments can't do for a specific merchant — a country it doesn't serve, a payment method it doesn't support, or a negotiated rate from an existing processor relationship that's hard to walk away from. Both pitches are true simultaneously, which is why this decision doesn't have a universal right answer. It has a right answer for your region, your volume, and your existing relationships, and the only way to get there is to actually look at the numbers instead of defaulting to whichever option showed up first in onboarding.
What Shopify Payments actually is
Shopify Payments is Shopify's own integrated payment processor, built on top of Stripe's infrastructure, which means it lives inside your Shopify admin with no separate login, no separate dashboard, and no app to install. Turn it on, connect a bank account, and you can accept cards immediately. Because Shopify owns the whole stack from checkout to settlement, it also unlocks features that third-party gateways can't fully replicate inside Shopify: fraud analysis built into the order timeline, chargebacks handled through the same admin panel you already use, and simpler accounting since payouts, fees, and refunds all show up in one ledger.
The rates scale with your subscription plan, and they're worth stating plainly rather than vaguely. For online credit card transactions in the US, the commonly cited current rates are 2.9% plus $0.30 on the Basic plan, 2.7% plus $0.30 on the Grow plan, and 2.5% plus $0.30 on both the Advanced and Plus plans. Cards issued outside your store's home country typically add another 1% on top of the base rate. These numbers move occasionally and vary by region and card type, so treat them as the current published ballpark rather than something to quote to a client without checking Shopify's own rate page first. The pattern that matters more than the exact digits is that higher-volume plans get meaningfully better rates, which is one of the first things worth checking before assuming a third-party gateway is cheaper.
The third-party fee, and the real math on when it matters
Here's the part that catches merchants off guard. If you use any payment gateway other than Shopify Payments, Shopify charges an additional transaction fee on top of whatever your processor charges you. This isn't a rumor or a legacy policy — it's a real, current line item, and it stacks. The commonly cited rates are 2.0% on the Basic plan, 1.0% on the Shopify/Grow plan, 0.5% on the Advanced plan, and a noticeably smaller figure — commonly cited around 0.15% to 0.2% — on Shopify Plus. That fee shows up on your Shopify invoice separately from your gateway's own processing fees, and it applies regardless of whether the third-party gateway itself is cheaper than Shopify Payments.
Do the math on a concrete example. A Basic-plan store processing a $100 order through Shopify Payments pays roughly $3.20 in Shopify's own processing fee and nothing else. The same store routing that order through a third-party gateway charging a competitive 2.5% plus $0.30 pays that $2.80 to the gateway, plus another 2.0% ($2.00) to Shopify as the platform fee — landing at $4.80, a full $1.60 worse than just using Shopify Payments. That gap narrows a lot on higher-tier plans, where the platform fee drops to 0.5% or less, and it can flip entirely if the third-party processor's negotiated rate is well below Shopify Payments' own rate, which does happen at serious volume.
Run the same comparison on an Advanced-plan store and the picture changes. Shopify Payments there sits at 2.5% plus $0.30, and the platform fee for a third-party gateway drops to a commonly cited 0.5%. If that merchant has negotiated a rate of, say, 2.2% plus $0.25 with an existing processor because of high monthly volume, the total cost with the platform fee added back in comes out close to parity with Shopify Payments, sometimes slightly ahead. That's the threshold worth watching for: below it, the platform fee usually eats any savings a third-party gateway claims to offer; above it, a genuinely negotiated enterprise rate can start to win. The honest takeaway is that the third-party fee makes Shopify Payments the default winner on price for most Basic and Grow-plan stores, and the calculus only gets genuinely competitive once you're on Advanced or Plus with real negotiating leverage on the gateway side.
Where Shopify Payments simply isn't available
Price isn't always the deciding factor, because for a meaningful share of merchants Shopify Payments isn't a choice at all — it's not offered in their country. Shopify Payments' coverage is commonly cited at around 39 countries and regions, concentrated in North America, Western and Northern Europe, and a handful of Asia-Pacific markets like Japan, Singapore, and Hong Kong. That leaves large, active ecommerce markets outside the fence. India is the clearest and most frequently cited example: Shopify Payments has never launched there, and every Shopify store selling to Indian customers in rupees has to route payments through a third-party gateway by default, not by preference. Other markets commonly flagged as lacking Shopify Payments support include Brazil, Argentina, Indonesia, Vietnam, Nigeria, South Africa, Pakistan, and Saudi Arabia, though the exact list shifts as Shopify expands coverage, so it's worth checking Shopify's current supported-countries page for any specific market before making a call.
For merchants incorporated or trading in one of these regions, the third-party discussion isn't really "should we pay the extra fee" — it's "which local gateway do we integrate," because there's no built-in alternative sitting right next to it in the admin. This is also where local payment method coverage matters as much as the processing rate. A merchant selling into India needs UPI, netbanking, and popular wallets supported natively, which a US-based generic gateway usually can't offer as well as a local specialist can.
The gateways merchants actually use, and what each is good for
Shopify integrates with more than 100 third-party gateways, but in practice the list that comes up in real merchant conversations is much shorter and fairly regional. In India, Razorpay and Cashfree are the two names that dominate, both available as dedicated apps in the Shopify App Store with local KYC-based onboarding, UPI and netbanking support, and rupee settlement — Cashfree is also an official Shopify partner, and both are built specifically for the gap Shopify Payments leaves open there. PayPal remains the closest thing to a universal fallback, useful less for its rates and more for the trust signal it carries with certain buyer segments and for reaching customers who prefer a PayPal balance over entering card details.
Stripe shows up in a more complicated role. In countries where Shopify Payments is available, Stripe generally isn't offered as a separate third-party option because Stripe is actually the banking infrastructure behind Shopify Payments itself. In markets outside Shopify Payments' coverage, Stripe can sometimes be connected as a direct third-party gateway, but availability varies by region and should be verified against Shopify's current gateway directory rather than assumed. Authorize.net and 2Checkout (rebranded as Verifone) round out the list for merchants who came to Shopify with an existing merchant account and negotiated rate from one of these older-guard processors and don't want to give that relationship up just to consolidate onto Shopify Payments. None of these are theoretical — they're live, supported integrations, and the right one depends entirely on the merchant's region and existing infrastructure rather than any universal "best" option.
Fraud liability and who actually handles a chargeback
This is the difference merchants notice the least until the first serious dispute lands, and then it matters a lot. With Shopify Payments, chargebacks and inquiries appear directly inside your Shopify admin. Shopify acts as the intermediary between you and the customer's issuing bank: you typically get somewhere between 7 and 21 days to submit evidence, Shopify forwards that evidence to the card network, and the bank makes the final call, with no appeal available once it does. Shopify charges a chargeback fee — commonly cited around $15 — that gets refunded if the merchant wins the dispute. Crucially, everything happens in one place, using the same order data, customer records, and fulfillment history already sitting in your store.
Route payments through a third-party gateway and that entire process moves outside Shopify. A Stripe dispute is managed in the Stripe dashboard, using Stripe's own evidence templates and timelines, and Stripe's chargeback fee — also commonly cited around $15 — is not refunded even if the merchant wins, which is a meaningfully worse position than Shopify Payments' refundable fee. PayPal disputes run through PayPal's Resolution Center with their own fee structure, commonly cited around $20, sometimes waived under PayPal's own seller protection program. Neither alternative is poorly built — Stripe in particular offers more configurable fraud rules and a more sophisticated risk dashboard than Shopify Payments exposes — but the operational cost is context-switching. Your team ends up managing disputes, fraud signals, and evidence submission in a second system that doesn't share your order timeline, which is a real overhead cost that rarely gets counted alongside the processing rate when merchants compare options on price alone.
PCI compliance: what changes when you leave Shopify Payments
Shopify's hosted checkout is PCI DSS Level 1 compliant as a platform, which covers the infrastructure Shopify controls directly. That baseline compliance exists regardless of which gateway a merchant uses, because Shopify's checkout page itself is what actually collects card data in most configurations. But compliance is a shared responsibility, not something a merchant can fully outsource. Merchants remain accountable for their own apps, admin access controls, and completing an annual Self-Assessment Questionnaire, and current PCI DSS 4.0.1 requirements around checkout page scripts put real obligations on merchants to know what's running on their storefront regardless of processor.
Where this gets more involved with a third-party gateway is scope. Depending on how the integration is configured and whether any card data ever touches a merchant's own servers versus staying entirely within the gateway's hosted fields, the gateway or the merchant's acquiring bank may ask for additional PCI documentation that simply doesn't come up under Shopify Payments' more contained setup. This isn't usually a dealbreaker — most reputable gateways, including Razorpay, Cashfree, and Stripe, offer hosted or tokenized checkout fields specifically designed to keep merchants out of higher PCI scope — but it's an added piece of due diligence that Shopify Payments merchants skip entirely by staying inside Shopify's own compliance boundary.
A realistic decision framework
Strip away the marketing on both sides and the decision really comes down to three questions, roughly in this order of importance. First, is Shopify Payments even available in your business's registered country? If not, this entire debate is moot and the real decision is which regional gateway — Razorpay or Cashfree for India, or the equivalent local specialist elsewhere — fits your payment method mix best. Second, what's your plan tier and transaction volume? On Basic or Grow with unremarkable volume, the math from earlier in this piece holds: Shopify Payments wins on pure cost in the overwhelming majority of cases, and the platform fee alone makes a "cheaper" third-party gateway a net loss once you add it back in. On Advanced or Plus, particularly with negotiated enterprise rates from an existing processor, the platform fee shrinks enough that a genuinely better underlying rate can outweigh it.
Third, do you have an existing relationship or multi-platform requirement that makes consolidation valuable on its own? A brand running the same catalog across Shopify, a separate marketplace presence, and a POS system outside Shopify's own hardware sometimes gets more value from one processor handling reconciliation everywhere than from Shopify Payments' lower per-transaction rate. That's a legitimate reason to accept the platform fee even when the pure math says otherwise, because the operational simplicity of one settlement account, one fraud team, and one set of reports across every sales channel has a real dollar value that doesn't show up in a rate comparison.
It's also worth being honest about the scenarios that don't justify a third-party gateway, because they come up often. Wanting a slightly nicer-looking checkout dashboard, disliking Shopify's payout schedule, or assuming a name-brand processor is inherently more trustworthy than Shopify Payments are not, on their own, good reasons to take on the platform fee and the extra integration overhead. If none of the three questions above produce a clear constraint pointing away from Shopify Payments, the default is still the default for a reason. None of these questions has a universally correct answer, which is exactly why "just use Shopify Payments" and "third-party gateways are always cheaper" are both bad advice when stated as absolutes.
Setup and technical complexity: native versus integrated
The complexity gap between the two options is real and worth planning for honestly. Enabling Shopify Payments is close to a formality: verify business details, connect a bank account, and it's live, with fraud filters, payout schedules, and chargeback handling already wired into the same admin interface as everything else in the store. There's no separate app, no separate credential set, and no separate support relationship to manage.
A third-party gateway adds a real integration step, even when the gateway ships an official Shopify app. Razorpay and Cashfree both require a live merchant account with completed KYC before the Shopify app will process a single transaction, which for an Indian merchant can mean days of document turnaround with the bank or gateway before checkout even goes live. Beyond initial setup, ongoing maintenance differs too: gateway API versions get deprecated and need updating, as happened when Shopify moved off legacy Stripe integrations in 2024 and required merchants on outdated versions to migrate or lose checkout functionality. Multi-gateway setups, where a merchant runs Shopify Payments for domestic orders and a regional gateway for a specific country, add configuration work around routing rules, currency handling, and keeping two sets of payout and reconciliation records aligned with the accounting system. None of this is prohibitive, but it's real engineering and operations time that a "just flip it on" comparison of processing rates tends to ignore entirely.
Where this gets built right
Most merchants land on Shopify Payments by default and only revisit the decision when a specific constraint forces the question — expanding into a country Shopify Payments doesn't cover, negotiating a better rate at higher volume, or needing to unify payments across Shopify and a second sales channel. Each of those situations is solvable, but they're rarely solved well by installing a gateway app and hoping the defaults work for a specific market's payment method mix, tax handling, and currency settlement requirements.
That's the kind of work Carryup's Shopify Deep Engineering service handles for D2C brands: wiring up regional gateways like Razorpay or Cashfree correctly from the KYC stage through go-live, building multi-gateway routing when a brand needs Shopify Payments for one region and a local processor for another, and making sure checkout stays fast and compliant while the payment layer underneath gets more complicated. If you're weighing this decision for a store expanding into a new market or trying to reconcile payments across more than one platform, that's a conversation worth having before the integration gets built rather than after something breaks in production.
If any of this sounds like your situation, talk to us. We'll tell you exactly where your revenue is leaking and what it would take to fix it. Explore Strategy & Consulting →

