Friday, July 10, 2026
Platforms & Tools

How to Choose and Configure a Payment Gateway Stack in 2026

Selecting the wrong payment gateway costs DTC brands 1–3% of GMV in unnecessary fees. Here's how to build a stack that converts, scales, and keeps compliance clean.

By · · 7 min read
How to Choose and Configure a Payment Gateway Stack in 2026

Payment infrastructure is one of the most consequential—and least glamorous—decisions a Shopify or DTC operator makes. Choose wrong and you’re leaking margin on every transaction, watching checkout abandonment spike because a preferred local method isn’t available, or scrambling when your single gateway flags your account during a Black Friday spike.

In 2026, the gateway landscape has matured considerably. Shopify Payments has expanded to 24 markets, Stripe continues to dominate developer-first stacks, and a new tier of regional challengers—Checkout.com, Adyen for SMB, and Airwallex—have made multi-gateway configurations not just viable but operationally straightforward. Here’s how to build a payment stack that actually fits your business.

Purple analytics chart on computer screen
📊 Platforms & Tools · By The Numbers
📈
41%
Growth
🎯
40%
Impact
💰
1.2%
Revenue
30%
Efficiency

What Does a Modern Payment Gateway Stack Actually Include?

Most merchants conflate the payment gateway (the technology that transmits transaction data) with the payment processor (the entity that moves money) and the merchant account (where funds land). In practice, platforms like Shopify Payments, Stripe, and Adyen bundle all three, which simplifies setup but obscures the tradeoffs.

A complete payment stack in 2026 typically includes:

Laptop analytics dashboard view

“Most of our clients come to us with a single-gateway setup and wonder why their international CVR is 40% lower than domestic,” says Michelle Tanaka, head of payments optimization at Skio partner agency Fuel Made. “The answer is almost always missing LPMs and no fallback routing logic.”

💡 Article Summary
Key Insights
1
What Does a Modern Payment Gateway Stack Actually Include?
2
How Do You Evaluate Gateway Fees Without Getting Buried in Fine Print?
3
What’s the Right Configuration for a Shopify Plus Store in 2026?
4
How Should You Handle Payment Gateway Risk and Account Holds?
5
Which Payment Gateways Work Best for Non-Shopify Platforms?
Source: Ecommerce Times

How Do You Evaluate Gateway Fees Without Getting Buried in Fine Print?

Gateway pricing is deliberately opaque. Here’s what to actually compare across vendors:

Step 1: Map your transaction mix. Pull 90 days of order data and segment by card type (debit vs. credit vs. corporate), geography, and average order value. Corporate Amex cards carry interchange rates 0.8–1.2% higher than consumer debit. If 30% of your B2B orders are on corporate cards, that’s a material cost difference between gateways that pass through interchange versus flat-rate processors.

Step 2: Model the true effective rate. The headline rate (e.g., Stripe’s 2.9% + $0.30) is almost never your actual rate. Add:

Step 3: Run a fee simulation. Take last month’s GMV and apply each gateway’s full cost structure. For merchants doing $500K+/month, the difference between Shopify Payments (2.4% + $0.30 on Advanced) and a negotiated Checkout.com rate can be $3,000–8,000/month.

“We moved a $2.1M/month Shopify Plus client from Stripe to a Checkout.com primary with Stripe as fallback last year. The effective rate dropped from 2.71% to 2.18%. That’s $110,000 annualized—real money.” — Alex Forrest, founder of CODA Commerce, a Shopify Plus agency

Step 4: Don’t ignore the Shopify transaction fee trap. Shopify’s 0.5–2% third-party gateway fee is levied on every transaction processed outside Shopify Payments. On a $1M/month store at the Basic plan, that’s $20,000/month in pure platform tax. Unless your non-Shopify gateway saves you more than that in interchange, the math rarely works below $3M GMV.

What’s the Right Configuration for a Shopify Plus Store in 2026?

Shopify Plus operators have access to Shopify Checkout Extensibility and the Payments Platform API, which changes what’s configurable. Here’s the recommended stack architecture for a Plus merchant doing $1M–$10M/month:

Step 1: Enable Shopify Payments as primary. The zero transaction-fee benefit alone justifies this for most merchants. Pair with Shop Pay to maximize one-click checkout adoption—Shop Pay shows 1.72x higher conversion than guest checkout in Shopify’s own 2025 benchmarks.

Step 2: Add Stripe as your fallback via the Payments Platform API. Shopify’s gateway failover logic will route to Stripe automatically if a Shopify Payments authorization fails. This is particularly important for high-AOV orders where a single declined transaction is expensive to lose.

Step 3: Integrate BNPL based on your AOV and category. For AOV above $150, Affirm and Klarna both show statistically significant conversion lifts (8–14% in split tests across furniture, apparel, and electronics). Klarna’s new Shopify app, updated in March 2026, now supports one-click checkout flows that don’t break the native Shop Pay experience.

Step 4: Enable local payment methods via a LPM aggregator. Rather than integrating iDEAL, Sofort, PIX, and Alipay individually, use an aggregator like Worldpay’s Global Payments suite or Airwallex’s LPM module. Airwallex’s Shopify app (launched Q4 2025) covers 60+ LPMs under a single integration and is the current best-in-class option for merchants with meaningful EU and APAC revenue.

Step 5: Configure 3D Secure 2.0 rules carefully. 3DS2 is now mandatory across EEA markets under PSD2 but adds checkout friction. Use risk-based authentication—route low-risk transactions (repeat customers, low AOV, matching billing/shipping) through frictionless flow and only challenge high-risk sessions. Kount and Signifyd both integrate directly with Shopify Plus checkout for real-time fraud scoring that feeds 3DS2 decisioning.

How Should You Handle Payment Gateway Risk and Account Holds?

This is the operational issue nobody talks about until it’s an emergency. Payment processors can hold funds or suspend accounts with limited notice, and it happens most often during high-volume periods—exactly when you can least afford it.

“I’ve seen seven-figure Shopify stores wake up on Cyber Monday with a 72-hour hold on their Stripe account because a fraud spike triggered an automated review. The damage wasn’t just the held funds—it was the checkout disruption while they scrambled for an alternative.” — Jamie Osei, director of risk at payments consultancy Paytrix Advisory

Operational steps to reduce hold risk:

Which Payment Gateways Work Best for Non-Shopify Platforms?

For WooCommerce, BigCommerce, and headless setups, the calculus is different. You don’t have the Shopify transaction fee to worry about, but you lose the native Shop Pay advantage.

WooCommerce: Stripe remains the default best-in-class option via the WooCommerce Stripe plugin (5M+ active installs). For higher-volume WooCommerce stores, Braintree (PayPal’s developer platform) offers competitive interchange-plus pricing and strong subscription support via its Vault API. WooPayments, Automattic’s native gateway, has improved substantially in 2025–26 but still lacks the international payment method coverage of Stripe.

BigCommerce: BigCommerce’s open payment architecture is genuinely best-in-class—no platform transaction fees and certified integrations with 65+ gateways. For BigCommerce operators, the recommended stack is Checkout.com (primary) + PayPal Commerce Platform (for digital wallet and Pay Later coverage) + an LPM aggregator for international. Checkout.com’s BigCommerce-certified app supports real-time FX and dynamic 3DS2, which is hard to match.

Headless/Custom: Stripe is the default for headless builds—its Elements and Payment Intents API are the most developer-documented in the industry. Adyen’s Token-as-a-Service API is worth evaluating above $5M GMV; the network token uplift (1.5–3% higher authorization rates) pays for the integration cost at volume.

What’s the Implementation Timeline and Who Owns This Project?

Payment gateway projects are underestimated in complexity. A realistic implementation timeline:

Ownership should sit with your Head of Ecommerce or VP of Growth, not your dev agency alone—payment decisions carry P&L consequences that require business context. Bring your CFO into gateway fee negotiations; processors respond differently when finance is in the room.

The payment stack isn’t a set-and-forget decision. Revisit it every 12 months: gateway fee structures change, new LPMs gain adoption in your key markets, and your own transaction mix evolves. Merchants who treat payments as a living infrastructure investment consistently outperform those who configure it once at launch and move on.

More in Platforms & Tools

View All →