Shopify Payment Options: Shopify Payments Versus Third-Party Gateways

Shopify Payment Options: Shopify Payments Versus Third-Party Gateways

Choosing how to collect money on Shopify has never been a question of which rate is lower. It is a question of what is available in your target market. This article covers collection only: the boundaries of the three paths, where Shopify Payments fits and where it does not, the extra cost mechanics on third-party gateways, multi-currency and settlement, subscriptions and preorders, chargebacks and account risk, and what to watch when switching. For the full flow from signup to first order, see the Shopify store setup tutorial; themes, products, and page configuration are out of scope here. If you are still comparing platforms, see the ecommerce platform comparison, and for the plugin side of a self-hosted store see the WooCommerce payment gateway setup guide. No rates, volume thresholds, or settlement days appear here; wherever a number is involved, the platform's and channel's current official policy governs.

1. The Three Collection Paths on Shopify

There are only three ways to get paid on Shopify: the platform's own Shopify Payments, external third-party payment providers, and manual payment methods. What separates them is not the interface but who moves the money, who carries chargeback liability, and what the platform charges. Get that structure clear and every later trade-off becomes easier.

1.1 Defining the Three Paths

Shopify Payments is integrated directly by the platform: once enabled and approved, settlement and chargeback handling stay inside one back office. A third-party payment provider is an external acquirer the merchant contracts with, configured through the platform's payment provider settings, where the platform still hosts the checkout page but the money flow bypasses the platform. Manual payment methods such as cash on delivery, bank transfer, or offline remittance involve no real-time online capture, so orders must be marked paid by hand, which suits wholesale, made-to-order, and high-ticket B2B flows.

1.2 What a Platform-Hosted Checkout Implies

Whichever path you use, the checkout page is hosted by the platform and merchants cannot rewrite its underlying logic. That constraint has two consequences. First, card data never touches the merchant's servers, so compliance scope stays small. Second, switching payment providers happens at the configuration layer rather than in front-end code, which makes switching look cheap. The real cost is elsewhere, and section 8 covers it.

2. Where Shopify Payments Fits and Where It Does Not

2.1 Not Every Market Can Enable It

Shopify Payments opens market by market, and the platform does not offer the service everywhere; the available markets and eligibility conditions follow the platform's current official policy. That means one thing: if your main customer base sits in a market outside the open list, the cost model has to be built on third-party gateways plus the extra transaction fee from day one, not on the assumption that you will start on platform rails and optimize later. Teams that miss this during pricing discover a completely different margin structure after launch.

Even in an open market, the merchant must pass an eligibility review, and entity details, business category, and settlement account must agree. A failed review usually has no fallback option, so you return to third-party gateways anyway. Budget buffer time for the review in the project plan.

2.2 What You Actually Buy With Shopify Payments

There are three layers of benefit. The first is a closed loop: settlement, refunds, and chargebacks handled in one back office rather than reconciled across systems. The second is consistent checkout: methods appear directly in the hosted checkout without extra redirects or plugin injection. The third is one fewer liability boundary: when a dispute appears, there is only one responsible party instead of an argument between platform and acquirer.

The price is control. Settlement timing, available methods, and refund windows are set by the platform, and the parameters a merchant can tune are limited. If the business needs unusual settlement arrangements or a specific local method, a third-party gateway is often the only route.

3. When Third-Party Gateways Make Sense and What They Cost

3.1 Four Cases That Force a Third-Party Gateway

Four situations effectively leave only third-party options: the target market does not support Shopify Payments; you need a local method the platform does not cover; you already hold an acquiring contract whose pricing beats migrating; or your entity and settlement account do not satisfy platform requirements. None of these are technical problems; they are commercial and compliance problems, so finance and legal should make the call rather than engineering.

3.2 The Extra Transaction Fee Is Structural

When you use a third-party payment provider, the platform charges an additional transaction fee. This is the platform's price for money bypassing its own rails, and it is a separate charge from the acquirer's own pricing. Cost comparison therefore has to add both layers: the acquirer's pricing plus the platform's extra fee is the true cost of collection. Comparing acquirer quotes alone systematically understates cost.

The fee also shifts where optimization happens. Under a third-party setup, the main cost lever is acquirer negotiation and the mix of payment methods, not changing the platform plan. To compare pricing structures across channels, see the payment gateway rate comparison, keeping in mind that the figures there illustrate structure only and the official quote from each channel governs.

4. How Method Availability Differs by Market

4.1 Availability Is a Gradient, Not a Boolean

Method availability is not a yes-or-no answer but a gradient. In some markets the platform's own rails cover everything. In others only third-party gateways work. In others both work but local method coverage differs. In still others, stable operation requires a local entity or local acquiring. The most reliable way to locate yourself on that gradient is a small live payment test in the target market, not a dashboard drop-down.

4.2 Combined Configurations Are the Norm

Most cross-border merchants end up combined: platform rails or one primary acquirer in the main market, one or two local acquirers filling methods in secondary markets, and separate handling for specific high-risk regions. The platform allows these to coexist, but operations get heavier, because each channel has its own chargeback process, settlement cycle, and reconciliation definitions. Combined setups therefore only work once reconciliation is unified, otherwise more channels simply mean more unreconciled differences.

On specific brands, globally oriented merchants often evaluate Stripe and Adyen side by side, the first fast to integrate and the second deep in regional coverage. Checkout.com, known for checkout experience, and Mollie, broad in European local methods, are also commonly shortlisted. Where the audience leans on installments and buy now pay later, coverage in the target market for Klarna, Afterpay, and Affirm is what matters. All of these run as third-party payment providers inside Shopify and therefore trigger the platform's extra transaction fee.

5. Multi-Currency, Exchange Rates, and Settlement

5.1 Markets Currency Is a Display Currency, Not a Settlement Currency

Shopify's multi-currency capability is configured through Markets, letting merchants set display currencies and pricing per market. The distinction that matters is this: display currency decides what the buyer sees, settlement currency decides what actually lands in your account. The two can differ, with a conversion step in between whose timing and rate source are set by the platform or the acquirer, which feeds straight into margin. Reading multi-currency checkout as a multi-currency collection account is the most common pricing-stage misunderstanding.

5.2 Matching Settlement Currency to Account Structure

If revenue comes mostly from one market, matching settlement currency to a local account reduces conversion loss. If revenue is spread, you must decide whether to accept a single settlement currency and convert yourself, or configure local settlement paths per market. That decision ties into entity structure, tax registration, and how the funds will be used, so it comes well before technical configuration. For the account design itself, see the multi-currency collection account guide, and define display price, settlement price, and book price as three distinct definitions up front.

6. Collecting for Subscriptions and Preorders

6.1 Subscriptions Depend on Both an App Layer and a Gateway Layer

Subscription businesses on Shopify usually run through subscription apps, and whether an app can charge depends on whether the underlying payment method supports tokenization and merchant-initiated charges. Shopify Payments handles this layer most smoothly. Third-party gateways must be checked for token storage and recurring charge support, with actual capability per the channel's official documentation. Renewals work only when both layers are satisfied; an app-only setup fails on the second charge.

6.2 Preorders and Installments Are Different Mechanics

Preorders usually run through preorder apps or a workaround in the ordering flow, and are essentially collect now, ship later, so the risk sits in fulfilment rather than payment. Installments split one order into several charges and require the payment method itself to support installment products. Both share one trait: order status no longer maps one-to-one onto funds status, so operators must see both that an order is paid and how many installments exist and which one is current. For interface design, see the subscription billing API integration guide.

7. Chargebacks, Risk Control, and Account Risk

7.1 The Chargeback Flow Works Inside the Platform, but Evidence Is Still Yours

Shopify provides a chargeback workflow where merchants submit evidence to respond to a dispute, but collecting that evidence and its quality remain your job: tracking numbers, delivery confirmation, communication logs, and records of accepted terms. With a third-party gateway, the chargeback process and liability sit with the acquirer, and the platform only relays or displays. Any switch in collection setup therefore requires updating the chargeback playbook at the same time. For reason codes and evidence templates, see the chargeback reason codes and evidence playbook.

7.2 Account Risk Comes From Three Places

Account risk comes from three sources: sudden shifts in transaction patterns, such as a long history of small orders followed by a very large one; a rising chargeback ratio crossing an acquirer's risk threshold; and a mismatch between entity details and the actual business, which invites compliance review. The answer is not to raise block rates, but to design blocking, review, and manual verification as one traceable chain. For concrete tactics, see the payment fraud prevention strategies guide, and treat any threshold as subject to the channel's official policy.

8. What to Watch When Switching Providers

8.1 The Real Migration Cost Sits in Subscriptions and Stored Methods

The technical part of a switch is light: reconfigure the back office, complete contracting on the channel side, and since the platform hosts checkout, the front end barely moves. The real cost sits in two places. First, stored payment methods for subscription businesses usually cannot be charged under the new setup, so customers must be guided to reauthorize. Second, liability for historical chargebacks and refunds must be written down before the switch, or old transactions end up orphaned. Get these wrong and you get a chain reaction where the new channel is live but existing customers fail to renew.

8.2 Risks, Symptoms, and Responses

A sensible sequence is to pilot in a secondary market or on a new storefront, validating chargeback, refund, and subscription paths; then migrate subscriptions in the main market; and only then retire the old channel. For the overall migration method and rollback design, see the payment gateway migration guide. If you are considering outsourcing collection and compliance responsibility entirely, compare the models in the merchant of record platforms guide. The limits SaaS platforms place on payment options get their own treatment in the independent store payment architecture piece, and automated and agentic checkout trends on Shopify are covered in the Shopify agentic commerce article. More collection topics are collected under the Payment category.

Source: 16IDC original. Product capabilities, pricing and eligibility requirements follow the relevant providers’ official documentation and contract terms.