Every few weeks, a store owner sends me a screenshot of their ecommerce payment gateway dashboard with one question: “Is this normal?” Usually it isn’t. Sometimes the fees are quietly eating a third of the margin on small orders. Sometimes a good chunk of legitimate cards are being declined, and nobody noticed because the store was busy chasing traffic. And sometimes the merchant picked a gateway three years ago because a plugin made it easy, and has never looked at it since.

I’ve spent years helping online retailers set up, audit, and switch payment providers, and the pattern is always the same. People treat the ecommerce payment gateway as a utility, like electricity. You plug it in and forget it. But your gateway sits at the exact moment a browser becomes a buyer. If it fails, looks untrustworthy, or charges too much, you lose money in ways that rarely show up as a single obvious line item.

This guide is the conversation I have with clients before they sign anything. It isn’t a ranking of “the top 10 gateways.” Rankings go stale fast, and the best provider for a fashion brand shipping across Southeast Asia is not the best one for a US supplement store. Instead, I’ll walk you through how to think about the decision so you can judge any provider yourself.

What an Ecommerce Payment Gateway Actually Does

Let’s clear up the vocabulary first, because sales reps blur it on purpose.

A payment gateway is the piece that captures card or wallet details at checkout and passes them safely onward. Stripe draws the line clearly: the gateway handles sending payment data securely, while the processor approves the transaction and moves funds between banks. Then there’s the merchant account, which is where the money lands before it reaches your bank.

Why the Terms Get Blurred

In the old days, you bought these three things separately and stitched them together. Today, most merchants never see the seams. A payment service provider, or PSP, bundles the gateway and processor into one service, so businesses have less to set up and manage. Stripe, PayPal, Adyen, Square, and many regional players work this way.

Why does this matter for your choice? Because “gateway” on a pricing page might mean three different things:

• A standalone gateway (like Authorize.net) that still needs a separate processor and merchant account.
• An all in one PSP that bundles everything under one contract.
• A platform’s built in option, like Shopify Payments, which is a PSP wrapped inside your store software.

Before comparing anything, ask each provider plainly: “Who is my processor, who holds my funds, and who do I call when a payout goes missing?” If the answer takes more than a minute, write that down as a warning sign.

Start With Your Customers When Choosing an Ecommerce Payment Gateway

Most merchants open a comparison spreadsheet and sort by transaction fee. I understand the instinct, but it’s backwards. The cheapest gateway that doesn’t support how your buyers want to pay is the most expensive one you can pick.

How Shoppers Pay Today

Look at the shift in how people actually pay online. Worldpay’s 2025 Global Payments Report found that digital wallets made up 53% of ecommerce spending in 2024, and that smartphones’ share of global ecommerce spend climbed from 19% in 2014 to 57% in 2024. That shift is central to mobile commerce and to the ecommerce trends shaping 2026. If your checkout makes a phone shopper type a sixteen digit card number with their thumb, you’re asking them to do more work than your competitor is.

Questions to Ask Your Own Data

So the first exercise I give clients is simple. Pull your analytics and answer these questions:

• What share of your traffic and orders comes from mobile?
• Which countries do your buyers live in?
• What’s your average order value, and how much does it vary?
• Do you sell one off purchases, subscriptions, preorders, or a mix?

The answers tell you which payment methods your ecommerce payment gateway must support. A store with a $40 average order and mostly mobile traffic needs Apple Pay, Google Pay, and PayPal front and center. A furniture store with a $1,500 average order should seriously consider buy now, pay later options. A store selling into the Netherlands needs iDEAL; one selling into Brazil needs Pix; one selling in the Philippines will want GCash and Maya.

Missing methods cost real sales. Baymard Institute’s checkout research, as reported by Multichannel Merchant, found that 8% of shoppers abandoned because there weren’t enough payment options and 5% because their card was declined. Those percentages sound small until you multiply them by a year of traffic. They are also among the easiest wins in ecommerce checkout optimization.

Read Ecommerce Payment Gateway Pricing Like a Finance Person

Once you know what you need, then you look at cost. And here’s where most people get misled, because the advertised rate is only the beginning.

Flat Rate Pricing

Flat rate is the familiar one: a single blended charge on every sale, commonly something like 2.9% plus 30 cents, no matter which card the buyer used. It’s simple, predictable, and fine for new stores, especially if you’re still working out how to start an online store.

Interchange Plus Pricing

Interchange plus breaks the cost apart: you pay the actual interchange and network assessments, then a markup the provider discloses separately. It’s more work to read, but once you have steady volume, it usually saves money. More importantly, it lets you see exactly what the provider earns from you.

A point many merchants miss: your card mix matters. Stores whose buyers mostly pay with debit or basic credit cards tend to overpay on flat rate plans, since their real underlying cost is well below the blended rate. If most of your buyers use premium rewards cards, the gap narrows.

The Fees Nobody Advertises

Beyond the headline rate, ask for a written list of every fee you could ever be charged. The ones that tend to surprise people:

• Chargeback fees, often charged even when you win the dispute.
• Currency conversion markups on international sales.
• Fees for refunds (some providers keep the original processing fee).
• Monthly minimums, PCI compliance fees, and “account maintenance” fees.
• Extra charges for fraud tools, recurring billing, or advanced reporting.
• Early termination fees if you leave before the contract ends.

My rule of thumb: take your last three months of real orders and run them through each provider’s full fee schedule. Not an estimate, the actual orders. The “effective rate” you get from that exercise (total fees divided by total sales) is the only number worth comparing.

Ecommerce Payment Gateway Approval Rates: The Number Nobody Quotes You

Here’s something I wish more merchants asked about. Two gateways can charge the exact same fee and produce very different revenue, because one approves more legitimate transactions than the other.

Every declined card from a real customer is a lost sale. Some declines are correct (insufficient funds, actual fraud), but plenty are “false declines,” where a good buyer gets rejected because of poor data, aggressive risk rules, or a weak connection to local card networks.

What Improves Approvals

• Local acquiring. If a provider processes a German customer’s card through a German acquiring bank, approval odds are generally better than routing it internationally.
• Network tokens and account updater services. These keep stored cards working after a customer’s card is reissued, which is huge for subscriptions.
• Smart retries. For recurring billing, a decent gateway will retry soft declines at better times rather than giving up.
• 3D Secure 2. The newer version authenticates most buyers quietly in the background and shifts fraud liability away from you on authenticated transactions.

When you talk to a provider’s sales team, ask for their typical authorization rate for businesses in your category and region. If they won’t give a number, ask whether you can test with a slice of traffic first. A serious provider will understand the question.

Ecommerce Payment Gateway Security and PCI Compliance

Every store that accepts cards falls under the Payment Card Industry Data Security Standard, known as PCI DSS. The good news is that a modern ecommerce payment gateway can take most of that burden off your plate, if you integrate it correctly.

Keep Card Data Off Your Server

The easiest path is to make sure card data never touches your server. Hosted payment pages, embedded payment fields (iframes), and redirect checkouts all achieve this. Merchants set up that way usually qualify for the shortest self assessment questionnaire, called SAQ A.

What Changed Under PCI DSS v4.0.1

The rules around SAQ A changed recently, and it’s worth knowing the details. According to Adyen’s documentation, version 4.0.1 dropped requirement 6.4.3 (covering payment page scripts) and requirement 11.6.1 (covering tamper detection) from SAQ A, and the updated questionnaire took effect on March 31, 2025. But there’s a catch. The PCI Security Standards Council added a new eligibility condition: merchants must confirm their site isn’t vulnerable to script attacks that could compromise their ecommerce systems.

How do you confirm that? The Council clarified that one acceptable route is getting written confirmation from your PCI compliant payment provider that its embedded payment form protects your page from script attacks, as long as you implement it the way they instruct.

In plain terms: when choosing an ecommerce payment gateway, ask whether they will give you written confirmation that their embedded checkout protects against script attacks, and ask for their current Attestation of Compliance. If they look confused by the question, that tells you a lot about how much compliance work will land on you.

Security Is Also a Conversion Issue

Shoppers judge safety by feel. A Baymard study covered by Multichannel Merchant found that 18% of shoppers had abandoned a checkout within three months because they didn’t trust the site with their card details. Familiar wallet buttons, a clean payment form that looks visually separate from the address fields, and a fast loading page all help here.

Fraud Tools and Chargeback Handling

Fraud is where small stores get hurt the most, because one bad weekend can wipe out a month of profit. Every gateway claims to “prevent fraud.” What you need to know is how.

Questions I always ask:

• Is machine learning fraud screening included, or is it a paid add on?
• Can I write my own rules (for example, block orders where billing and shipping countries differ above a certain amount)?
• Can I review flagged orders manually before they’re captured?
• Does the gateway support 3D Secure and liability shift?
• How are chargebacks handled? Is there a dashboard for submitting evidence, or is it all email?

Be careful with fraud tools that are too aggressive. A system that blocks every slightly unusual order will protect you from chargebacks and quietly kill your conversion rate at the same time. You want controls you can tune, plus reporting that shows how many orders were blocked and why.

Also pay attention to chargeback thresholds. Card networks monitor merchants whose dispute rates climb too high, and a provider may hold funds or close your account if you cross certain limits. Ask what those limits are before you need to know.

Integration With Your Platform and Hosting

This is the part people underestimate until launch week. The best gateway on paper is useless if it fights your store software.

Hosted Platforms

If you’re on a hosted platform like Shopify or BigCommerce, your options are partly made for you. Shopify, for instance, pushes merchants toward its own payments product and may charge additional fees for third party gateways. That’s not necessarily bad, but it’s a cost to factor in, and it’s one of the trade offs covered in our Shopify vs WooCommerce comparison.

Self Hosted and Custom Stores

If you’re on WooCommerce, Magento, or a custom build, you have more freedom and more responsibility. Check:

• Is there an official, actively maintained plugin or extension, or only a third party one last updated two years ago?
• Does it support the checkout type you want (embedded fields, express wallet buttons on product pages, one click checkout for returning buyers)? Express buttons should fit your product page SEO and layout, and one click checkout pairs well with ecommerce personalization for repeat customers.
• Does it play nicely with your caching, security plugins, and hosting setup? Payment pages and webhooks break more often than you’d think when aggressive caching is involved, which is why the best web hosting for ecommerce matters here too.
• Is there a proper sandbox environment for testing?
• Are webhooks reliable, and does the gateway retry them if your server is briefly down?

Choose the Ecommerce Payment Gateway Last

A Speckyboy guide for web designers makes a point I agree with: the payment gateway shouldn’t be the first piece you lock in on an ecommerce project. Settle your platform (start with the best ecommerce platform for small business shortlist), your product catalog and ecommerce inventory management, and your order fulfillment process first. Then choose the ecommerce payment gateway that fits that stack, rather than bending the whole store around a payment provider. This matters even more if you’re taking a brick and mortar store online and already have an in-store payment provider.

Speed matters too. A heavy payment script that adds seconds to your checkout page on a mid range Android phone costs sales and drags down the page experience signals covered in our ecommerce SEO guide. Test the checkout on a real device over a mobile connection, not just on your office WiFi.

Payouts, Cash Flow, and Account Stability

Revenue on a dashboard isn’t revenue in your bank. How quickly and reliably your money arrives can matter as much as the fee.

Ask about:

• Payout schedule. Daily, weekly, or on request? Is there a longer delay for new accounts?
• Rolling reserves. Some providers hold a percentage of sales for weeks or months as protection against chargebacks, especially for preorders, high ticket items, or industries they see as risky.
• Instant payouts. Often available for an extra fee. Useful in a pinch, expensive as a habit.
• Account freezes. What triggers a review, and how long does it usually take?

The Risk of Sudden Freezes

That last one deserves real attention. Aggregator style providers (the ones that let you sign up in minutes) approve accounts easily because they take on risk collectively. The flip side is that they can freeze funds quickly when something looks unusual, like a sudden sales spike after a viral post. I’ve seen stores lose access to their money right during their best week of the year.

If you sell anything that providers classify as higher risk (supplements, CBD, travel, firearms accessories, subscription boxes with free trials), be upfront during signup. A provider that knowingly approves your business model is far safer than one that approves you by accident and shuts you down later.

Selling Across Borders

If you sell internationally, or plan to, your gateway choice gets more important.

Look for:

• Multi currency pricing. Shoppers convert better when they see prices in their own currency.
• Settlement currencies. Can you receive funds in more than one currency, or will everything be converted (with a markup) into your home currency?
• Local payment methods. As covered earlier, cards don’t dominate everywhere.
• Tax and compliance support. Some providers help calculate and collect VAT or sales tax; others leave it to you.
• Regional regulations. In Europe, Strong Customer Authentication rules mean your gateway must handle 3D Secure properly, or you’ll see high decline rates.

A common mistake is choosing a gateway that’s great at home and then bolting on a second one for international sales. That can work, but it doubles your reconciliation work. If cross border growth is part of your omnichannel retail strategy for the next two years, factor it in now.

Support and the Exit Plan

Payment problems never happen at convenient times. They happen during a flash sale on a Saturday night.

Before signing, test the support. Send a pre sales technical question through each provider’s channels and time the response. Ask whether merchants at your volume get phone support or just email. Look for status pages and incident histories.

Then think about leaving, because one day you might want to. The key question is card data portability. If you have subscribers or customers with saved cards, can the provider export that tokenized card data to a new PCI compliant provider? Most major ones will, but the process and timelines vary. A gateway that holds your customers’ card data hostage effectively locks you in, and lock in weakens your position at every pricing negotiation.

How I Score Each Ecommerce Payment Gateway With Clients

When a client is choosing between providers, I keep it practical. We score each candidate from one to five on these criteria, weighted by what matters for that business:

1. Payment methods your actual customers use.
2. Effective rate based on your real order history.
3. Expected approval rate and authentication support.
4. Compliance help (SAQ A eligibility, written confirmations).
5. Fraud tools and chargeback workflow.
6. Platform integration quality and checkout speed.
7. Payout timing and account stability.
8. International capabilities, if relevant.
9. Support quality and data portability.

Weighting the Scores

A subscription business might weight approval rates and card updater services heavily. A store running big seasonal sales might weight account stability and support. A small store just starting out might weight ease of setup above everything else, accepting a slightly higher rate for now.

One more tip: you don’t have to pick just one forever. Many growing stores run a primary ecommerce payment gateway plus a secondary option (often PayPal or a buy now, pay later provider) at checkout. Larger merchants sometimes use payment orchestration tools to route transactions between providers based on cost or approval odds. You probably don’t need that on day one, but it’s good to know the door is open.

Final Thoughts

Choosing an ecommerce payment gateway isn’t glamorous, and it rarely gets the attention it deserves during a store build. But consider the stakes. Baymard Institute’s running average, drawn from 50 separate studies, puts cart abandonment at roughly 70%, and checkout friction, missing payment methods, trust concerns, and declined cards all feed that number. Your gateway touches every one of them.

So start with your buyers. Work out the true cost using real orders. Ask uncomfortable questions about approval rates, reserves, and compliance. Test the checkout on a phone. And make sure you can leave if you need to.

Do that, and you won’t be the store owner sending a confused dashboard screenshot next year. You’ll be the one who knows exactly what they’re paying, why, and what they’re getting for it.

Frequently Asked Questions

What is the difference between a payment gateway and a payment processor?

The gateway securely captures and sends payment details from your checkout, while the processor communicates with the banks and card networks to authorize the payment and move the funds. Many providers now bundle both. Stripe’s comparison of processors and gateways explains how they work together.

Do I need a merchant account to accept online payments?

Not always. All in one providers like Stripe, PayPal, and Square give you an aggregated account, so you don’t need a separate merchant account. Larger stores sometimes prefer a dedicated merchant account for better pricing and stability. This guide on choosing a payment gateway provider covers the setup options.

Is flat rate or interchange plus pricing better for an online store?

Flat rate is simpler and works well for new or low volume stores. Interchange plus tends to cost less once volume is steady, and it shows you exactly what the provider earns. Toast’s explainer on interchange plus and flat rates walks through the trade offs.

How does my ecommerce payment gateway affect PCI compliance?

If you use hosted or embedded payment fields so card data never touches your server, you may qualify for SAQ A, the shortest self assessment. Under PCI DSS v4.0.1, you must also confirm your payment page is protected from script attacks. See the PCI Security Standards Council’s FAQ on SAQ A eligibility for details.

Which payment methods should my ecommerce payment gateway support?

At minimum, major cards plus the digital wallets your customers use, such as Apple Pay, Google Pay, and PayPal. Add local methods for each country you sell into, and consider buy now, pay later for higher priced items. Worldpay’s Global Payments Report findings show how strongly wallets now dominate online spending.

Can switching your ecommerce payment gateway reduce cart abandonment?

It can, if your current gateway lacks popular payment methods, declines too many good cards, or makes checkout feel untrustworthy. Baymard Institute’s cart abandonment research lists the most common checkout issues to fix.

References

1. Stripe. Payment processor vs payment gateway: What they are and how they work together
2. Worldpay. 10 Years of Cash, Cards and Crypto: Worldpay’s Global Payments Report Tracks a Decade of Transformation
3. Baymard Institute. Cart Abandonment Rate Statistics
4. Multichannel Merchant. Nearly One Fifth of Consumers Don’t Trust Ecommerce Sites with CC Info
5. PCI Security Standards Council. FAQ Clarifies New SAQ A Eligibility Criteria for E Commerce Merchants
6. Adyen Docs. SAQ A Eligibility
7. SecurityMetrics. PCI DSS v4.0.1 Ecommerce FAQs
8. CoreCommerce. What Is Interchange Plus Pricing?
9. Toast. Interchange Plus vs. Flat Rate Credit Card Processing
10. Speckyboy. How to Help Your Clients Choose the Right eCommerce Payment Gateway
11. CustomerThink. How to Choose a Payment Gateway Provider For Your Ecommerce Business