WooCommerce Payment Gateways: Compare, Choose, and Set Up

What a Payment Gateway Actually Does

WooCommerce payment gateways are the tools that let your store accept money, and understanding what they do makes every later decision easier. WooCommerce runs the shop, the cart, and the order, but it does not touch a customer's card directly. When a shopper clicks the button to pay, WooCommerce hands the transaction to a gateway, and the gateway carries it the rest of the way.

Behind the scenes, a few different players are involved. The gateway is the software that securely collects and passes along the card details. The payment processor talks to the card networks such as Visa and Mastercard to check that the card is valid and has funds. The acquiring bank receives the money on your behalf, and eventually it lands in your business bank account. For most store owners, all of this is bundled into one service you sign up for, so you rarely have to think about the separate pieces. What matters is that the gateway is the bridge between your store and the money.

Here is the flow in plain terms. A customer fills their cart and goes to checkout. They enter their card or choose a wallet. The gateway encrypts those details and sends them off to be authorized. The card network and bank approve or decline. If approved, WooCommerce marks the order as paid and your customer sees a confirmation, while the funds are queued to be paid out to you, usually on a schedule of a day or a few days. That whole round trip happens in a couple of seconds.

Why does the choice of gateway matter so much if they all move money? Because they differ in the countries and currencies they support, the fees they charge, whether they support wallets and subscriptions, how the checkout feels to your customer, and how much security work lands on you. A gateway that is perfect for a store in one country may not even be available in another. One that handles simple one time sales beautifully may not support recurring billing. Getting this decision right early saves you from a painful migration later. If you are still planning the store itself, our guide on how to build a WooCommerce store covers the wider setup that payments fit into.

Hosted vs On-Site Checkout

One of the first things to understand about any gateway is where the card details are actually entered. This is the hosted versus on-site question, and it affects both how the checkout feels and how much security responsibility you carry.

With a hosted checkout, sometimes called a redirect, the customer is sent from your store to the gateway's own secure page to enter their card. After they pay, the gateway sends them back to your store, where they see the order confirmation. PayPal's classic flow is the familiar example: you click pay, you land on PayPal, you approve, and you come back. The big advantage is security. Because the sensitive card data is entered on the gateway's page and never touches your server, your compliance burden is much lighter. The trade off is that the customer briefly leaves your site, which can feel like a small interruption and, on a poor connection, an extra step where a few shoppers drop off.

With an on-site checkout, the card fields appear right on your own checkout page. Modern gateways do this safely by embedding a secure field, often an iframe hosted by the gateway, so the raw card number is captured directly by the gateway rather than by your server. To the customer it looks like they never left your store, which feels smoother and keeps your branding in front of them the whole time. Stripe and WooPayments are common examples of this approach. The trade off is a slightly larger compliance responsibility and a little more that can go wrong technically, though a well built store handles this cleanly.

There is also a middle style where the gateway provides a set of drop in fields or a modal that pops up over your site. Practically, it behaves like on-site checkout from the customer's point of view while still keeping card data off your server. The important thing is not the label but the answer to one question: does a full card number ever get typed into a field that your own server processes or stores? If the answer is no, you are in good shape.

Which should you use? For most stores, an on-site card checkout gives the best experience, especially on phones, provided it is built with a gateway that keeps card data off your server. Adding a hosted option such as PayPal alongside it gives shoppers a familiar fallback. You do not have to pick only one, and offering two well chosen paths often converts better than forcing everyone through a single option.

PCI Compliance and Security Basics

Any store that accepts cards has to think about security, and the standard that governs it is PCI DSS, the Payment Card Industry Data Security Standard. It sounds intimidating, but for a typical WooCommerce store the practical version is manageable, especially when you choose your gateway wisely. The core idea is simple: card data is valuable and dangerous, so the rules exist to keep it protected.

The single most important decision for reducing your PCI burden is to never let raw card numbers touch your own server. When you use a gateway that either hosts the checkout or captures card details in a secure embedded field, the card number goes straight to the gateway, and your site only ever sees a token, a harmless reference that stands in for the real card. This keeps you in the lightest compliance category, usually satisfied with a short self assessment questionnaire rather than a heavy audit. Almost every reputable modern gateway is designed to work this way, which is a strong reason to stick with well known providers.

Beyond the gateway choice, a few basics apply to every store:

• Use HTTPS everywhere. An SSL certificate that encrypts the connection is required, not optional, and every serious host provides one. Our overview of how to secure a WordPress website goes deeper on this and related hardening.
• Keep everything updated. WordPress core, WooCommerce, your gateway extension, and your theme all need to stay current, because outdated software is the most common way stores get compromised.
• Do not store card numbers yourself. Let the gateway hold the sensitive data through tokens. There is almost never a good reason for your store to keep full card numbers.
• Limit and protect admin access. Strong passwords, two factor login, and as few admin accounts as you actually need all reduce your risk.
• Choose quality hosting. A host built for WooCommerce with firewalls and monitoring does a lot of the heavy lifting for you.

It is worth being clear about what PCI compliance is and is not. It is a real obligation that your gateway and card brands expect you to meet, and ignoring it can mean higher fees or lost card acceptance if something goes wrong. It is not, for most small and mid sized stores, a giant project, as long as you use a modern gateway and keep your site healthy. The stores that get into trouble are usually the ones running outdated software or trying to capture and store card data in ways they should not. Choose a good gateway, keep the site current, and you have handled the large majority of the risk.

Comparing the Major Gateways

Now to the choice itself. Below is a fair, generic comparison of the gateways most WooCommerce stores consider. Every one of these is a legitimate, widely used option, and the right pick depends on your situation rather than on any of them being simply better. We describe fee structures qualitatively, because published rates change and vary by plan, volume, and country. Always confirm current pricing directly with the provider.

Stripe is a developer friendly gateway that powers a huge number of online stores. It supports on-site card checkout, digital wallets such as Apple Pay and Google Pay, a wide range of currencies, and recurring billing. Its official WooCommerce extension is well maintained. Stripe is a strong default for stores that want a smooth on-site experience and broad country support. Its pricing is typically a flat per-transaction fee combining a fixed amount plus a percentage, with adjustments for international cards and currency conversion.

WooPayments, also known as WooCommerce Payments, is the payment solution built by the makers of WooCommerce and managed inside your store's dashboard. Under the hood it is powered by Stripe's infrastructure, so it offers a similar on-site checkout, wallet support, and the convenience of managing payouts and disputes without leaving WooCommerce. For stores in supported countries that want the most native, integrated experience, it is a natural fit. Its fee structure is similar in shape to Stripe's.

PayPal is one of the most recognized names in online payments, and that trust is its biggest strength. Many shoppers will complete a purchase specifically because PayPal is offered, since they can pay without sharing card details with a store they do not know yet. PayPal supports both a redirect style checkout and newer on-site card fields, works in many countries, and can handle recurring payments. It is often best used as a second option alongside a primary card gateway rather than as the only method.

Square shines for businesses that sell both online and in person. If you already use Square for a physical location, its WooCommerce integration can sync inventory and keep online and offline sales in one system. Square supports card payments and wallets and is available in a set of specific countries. For an omnichannel retailer, the unified view of in-store and online sales is a real advantage.

Authorize.net is a long established gateway often used by businesses that already have a relationship with a merchant account provider. It separates the gateway from the merchant account, which gives some businesses flexibility in negotiating processing rates. It supports on-site card capture and recurring billing. It tends to appeal to established businesses with existing banking relationships rather than to brand new stores looking for the fastest signup.

The table below summarizes the general shape of each option. Treat it as a starting map, not a final verdict, and verify the current details for your country before committing.

A quick word on fee structures, since cost is always part of the decision. Most gateways charge a per-transaction fee that is a small fixed amount plus a percentage of the sale, and that is the shape you will see most often. Some use flat-rate pricing, which bundles everything into one simple published rate that is easy to predict. Others use interchange-plus pricing, which passes through the actual card network cost and adds a clear markup on top, and this can work out better for higher volume stores that want transparency. There may also be extra charges for international cards, currency conversion, chargebacks, or monthly account minimums. None of these numbers belong in a guide like this because they move over time, but knowing the shapes helps you ask the right questions when you compare quotes from providers.

Wallets, Subscriptions, and Currencies

Three features tend to separate a gateway that merely works from one that genuinely fits your business: digital wallets, recurring billing, and multi currency support. Which of these you need depends entirely on what you sell and to whom.

Digital wallets: Apple Pay and Google Pay

Wallets let a shopper pay with a card they have already saved to their phone or browser, confirmed with a fingerprint, a face scan, or a tap, instead of typing a card number. On mobile, where most store traffic now lives, this is one of the single biggest levers for reducing abandoned carts, because it removes the most tedious part of checkout. Gateways such as Stripe, WooPayments, and Square support wallets, and enabling them usually requires an on-site checkout. Apple Pay additionally needs a quick domain verification step, which is a one time setup task. If a large share of your visitors are on phones, wallet support should weigh heavily in your choice.

Subscriptions and recurring payments

If you sell memberships, boxes, courses, or any product billed on a cycle, recurring payments are not optional. Two pieces have to work together: an extension that manages the billing schedule and the customer's subscription, and a gateway that can securely store a payment method and charge it automatically when each cycle comes due. Stripe, WooPayments, PayPal, and Authorize.net are commonly used for this. Beyond simply charging on a schedule, look for how a gateway handles failed payments, since cards expire and get declined. Good gateways retry intelligently and can prompt the customer to update a card, which protects revenue you would otherwise lose to what the industry calls involuntary churn. If recurring billing is central to your model, our guide on building a membership site covers how these pieces fit together.

Currencies and cross border selling

If you sell beyond your home country, currency support matters. Some gateways let customers see and pay in their own currency, which reduces confusion and abandoned carts, then settle to you in yours. Watch for currency conversion fees and for whether a gateway is even available to merchants in your country, since availability is often the real constraint rather than features. A store selling only domestically can safely ignore this, while a store with international ambitions should confirm multi currency support before committing to a gateway.

Canada-Relevant Gateway Options

For Canadian stores, the global gateways above all work, but there are also local options worth weighing, often for reasons of support, banking relationships, and pricing transparency. As always, we describe these generically and point you to the providers for current details.

Moneris is one of Canada's largest and best known payment processors, backed by major Canadian banks. For a Canadian business that values a domestic provider with local support and an established banking relationship, Moneris is a familiar and trusted name. It can be connected to WooCommerce through an integration, supporting both on-site and hosted checkout styles depending on the setup. Businesses that already process in person payments through Moneris sometimes prefer to keep their online store on the same processor for a single relationship and consolidated reporting.

Helcim is a Canadian option that has built a reputation around transparent, interchange-plus pricing and straightforward account terms. For stores that want clear visibility into what each transaction actually costs, and that like the idea of pricing that can improve as volume grows, Helcim is worth a look. It supports on-site card checkout and wallets and integrates with WooCommerce. Its appeal is largely about pricing clarity and support for growing Canadian businesses.

Which Canadian path makes sense comes down to your priorities. If you want the reassurance of a large, bank backed processor and possibly already use one in a physical location, Moneris fits naturally. If transparent pricing and a modern signup are your priorities, Helcim is compelling. And plenty of successful Canadian stores simply run on Stripe, WooPayments, or PayPal, which are all available in Canada and support Canadian dollars. There is no wrong answer here, only the one that best matches how your business banks and operates. When we build stores for Canadian clients, we help weigh these based on the client's existing banking, volume, and whether they also sell in person.

How to Set Up a Gateway in WooCommerce

Once you have chosen a gateway, connecting it to WooCommerce follows a consistent pattern regardless of which provider you picked. Here is the general process, which you can adapt to your specific gateway. For a deeper step by step walkthrough, see our dedicated guide on how to add a payment gateway in WooCommerce.

Step 1: Create your gateway account

Sign up with your chosen provider and complete their onboarding. This usually means giving business details, banking information for payouts, and identity verification to satisfy anti fraud rules. Approval can be instant for some gateways and take a day or two for others, so start this early rather than the night before launch.

Step 2: Install the official extension

In your WordPress dashboard, install the official WooCommerce extension for your gateway. Always prefer the official plugin from the gateway or from WooCommerce.com over an unofficial one, because payment code is exactly where you want vetted, maintained software. WooPayments is a special case, since it is managed directly inside WooCommerce rather than as a separate third party plugin.

Step 3: Connect and configure

Enter the API keys or connect your account through the provided button, then set your options: which card types to accept, whether to enable wallets, the checkout style, and any descriptors that appear on customer statements. Enable Apple Pay and Google Pay here if your gateway supports them, and complete any domain verification the wallet requires. Under WooCommerce settings, confirm your store currency and that the gateway shows up as an available payment method.

Step 4: Test before you accept real money

This step is not optional and it is the one people skip. Most gateways offer a test or sandbox mode with fake card numbers so you can run a complete order without moving real money. Place test orders, confirm the order status updates correctly to paid, check that confirmation emails send, and try a refund. If you sell subscriptions, test a renewal. Catching a misconfiguration here costs you nothing, while catching it after launch can mean lost or stuck orders.

Step 5: Go live and keep an eye on it

Switch the gateway from test to live mode, then place one small real transaction yourself and refund it to confirm the whole path works end to end, including the payout landing in your account. After launch, watch the first days of real orders, keep the extension updated, and periodically review declined payments and any disputes. A payment setup is not something you configure once and forget, it is part of the store you keep healthy over time.

How to Choose the Right Gateway

With the options and the setup understood, choosing comes down to answering a short list of honest questions about your own business. Work through these and the field usually narrows quickly.

• Where are you and your customers? Availability by country is the first filter. A gateway that is not offered in your country is off the list no matter how good it is, and one that does not support your customers' currencies will cost you sales.
• Do you need wallets? If much of your traffic is mobile, prioritize a gateway with strong Apple Pay and Google Pay support and an on-site checkout, since wallets are one of the biggest mobile conversion levers.
• Do you bill on a recurring cycle? If yes, confirm the gateway supports stored payment methods, automatic renewals, and smart handling of failed payments before you build around it.
• How much does checkout branding matter? If keeping shoppers fully on your site is important, favor an on-site gateway. If minimizing security work matters more, a hosted option is attractive.
• What is your volume and how do you bank? Higher volume stores may benefit from interchange-plus pricing and existing merchant relationships, while newer stores often prefer the simplicity of flat-rate pricing and instant signup.
• Do you also sell in person? If so, a gateway that unifies online and in store sales, such as Square, can save real administrative effort.

A practical pattern that works for many stores is to offer two gateways: a primary on-site card gateway that also handles wallets, plus PayPal as a trusted alternative. This covers the shoppers who want a fast wallet tap, the ones who will type a card, and the ones who only trust a name they already know. You do not need five payment options cluttering your checkout, but a well chosen second one often pays for itself in recovered sales. If you are also weighing WooCommerce against other platforms entirely, our comparison of WordPress versus Shopify covers how payment flexibility differs between them, and our overview of WooCommerce custom development explains what is possible when your needs go beyond the standard extensions.

Common Mistakes to Avoid

Over many store builds, the same avoidable payment mistakes come up again and again. Knowing them in advance saves you real trouble.

Skipping test mode. The most common and most painful mistake is going live without running test transactions. A misconfigured gateway can silently fail to mark orders as paid, or fail to send confirmation emails, and you may not notice until customers complain. Always test in sandbox first.

Offering only one payment method. Forcing every shopper through a single gateway leaves money on the table. Some customers abandon a cart simply because their preferred method is not offered. A second, well chosen option often recovers those sales.

Ignoring mobile and wallets. If most of your traffic is on phones and your checkout still requires typing a full card number with no wallet option, you are making the hardest part of buying harder than it needs to be. Wallet support directly lifts mobile completion.

Trying to store card data yourself. Any setup where full card numbers are captured and stored on your own server multiplies your security and compliance burden for no good reason. Let the gateway hold the sensitive data through tokens.

Choosing on fees alone. The lowest headline rate is not always the best deal once you factor in currency conversion, chargeback handling, wallet support, and reliability. A slightly higher rate on a gateway that converts better and rarely breaks can earn far more than it costs.

Never touching it again after launch. Gateways release updates, cards expire, and disputes happen. Treating payments as a set and forget task leads to stale extensions and unnoticed failed renewals. Payments deserve a place in your ongoing site maintenance, which our guide on securing a WordPress website touches on as part of keeping a store healthy.

Get Help Setting Up Payments

For a common gateway such as Stripe or PayPal, many store owners connect payments themselves, and the steps above will carry you through it. Where it gets trickier is when you need several gateways working together cleanly, a custom or optimized checkout, a regional processor like Moneris or Helcim, subscriptions with reliable renewals, or simply the confidence that everything has been tested and hardened before a single real customer arrives.

That is the kind of work our team does every day. We build and maintain real WooCommerce stores, we configure payments so card data stays off your server, and we test the whole path before launch so orders do not slip through the cracks. You own your store, your code, and your gateway accounts, with no lock in. If a simpler setup serves you better, we will tell you that too, because honest scope advice is how we earn long term clients rather than one time jobs. You can learn more about our approach on the WooCommerce side of our work and how we help stores get found as well as get paid.

Whether you are launching your first store, migrating from another platform, or fixing a checkout that is losing sales, getting payments right is worth doing carefully. For the wider build around your payments, our walkthrough on how to build a WooCommerce store covers everything from products to launch. And when you want a hand with the payment setup itself, you can get in touch for a free, no-obligation quote and we will help you choose and configure the right gateways for your store. There is no pressure, and the first conversation is always free.

Official documentation is also a good companion as you go. The WooCommerce payments documentation lists supported gateways and their setup notes, and the Stripe developer documentation is a clear reference for how modern on-site and wallet payments work under the hood. Between those resources, this guide, and a careful test before launch, you have what you need to accept payments confidently on WooCommerce.