How to Add a Payment Gateway in WooCommerce

What a Payment Gateway Is

A payment gateway is the service that carries card details safely from your checkout to the bank that approves or declines the charge, then carries the answer back. When someone types a card number into your WooCommerce checkout, that data cannot go straight to a bank. It has to be encrypted, checked for fraud, routed to the right card network, and returned as an approval or a decline. The gateway is the piece that does all of that in the background, usually in under a second.

It helps to picture the journey. The shopper enters their card, WooCommerce hands the request to your chosen WooCommerce payment gateway, the gateway passes it to a processor and on to the customer bank, and the answer travels back the same way. If the bank approves, the order is marked paid and the customer sees a thank you page. If it declines, the shopper is asked to try again. All of this happens without a page reload on a modern checkout.

Why the gateway choice matters so much

The gateway shapes three things that a store owner feels every day. First, it decides which payment methods you can offer, from plain cards to wallets like Apple Pay and Google Pay to buy now pay later options. Second, it affects how quickly money lands in your bank account, since payout timing varies between providers. Third, it sets how much of the security and compliance burden falls on you, which we cover in detail later. A well chosen gateway quietly handles all three. A poorly matched one creates friction at checkout, slow payouts, or extra compliance work.

On site checkout versus a redirect

Gateways handle the actual card entry in one of two ways, and the difference matters for both trust and conversion. With on site checkout, sometimes called an inline or embedded flow, the card fields appear right on your own checkout page inside a secure element the gateway controls, so the shopper never leaves your store. With a redirect flow, the shopper is sent to the provider hosted page to pay and then returned to your site afterward. On site checkout usually feels smoother and keeps buyers in your branded environment, while a redirect can add reassurance for shoppers who trust the provider name. Most modern extensions default to on site fields with a redirect only as a fallback, which is the balance most stores want.

The gateway is part of a bigger build

Payments sit inside the larger job of running a store, so it is worth seeing the gateway as one component rather than the whole project. If you are still assembling the store itself, our guide on how to build a WooCommerce store walks through products, shipping, tax, and checkout so the gateway has a solid home to plug into. When those pieces are in place, adding a gateway is mostly a matter of installing an extension and connecting an account, which is exactly what the rest of this guide covers.

Gateway vs Merchant Account vs Processor

People use the words gateway, processor, and merchant account as if they mean the same thing, and that confusion leads to bad decisions. They are three different jobs. Understanding the split makes it far easier to compare providers, because some services bundle all three and some do not.

The three roles in plain terms

• Payment gateway: the technology that captures card details at checkout, encrypts them, and passes them along for authorization. It is the connector between your website and the money movement behind it.
• Payment processor: the company that actually moves the transaction through the card networks, talks to the banks, and settles the funds. The processor does the heavy lifting once the gateway hands off the request.
• Merchant account: a special type of bank account that holds funds from card sales before they are paid out to your regular business account. It is the holding place that makes card acceptance possible.

Why the modern setup feels simpler

In the old model you had to arrange each piece separately, signing up with a gateway, a processor, and a bank for a merchant account, then stitch them together. That was slow and technical. Modern providers such as Stripe, PayPal, and Square roll the gateway, the processing, and the merchant account into a single sign up. You create one account, connect it to WooCommerce, and everything behind the scenes is handled for you. This is why most stores today talk about their gateway as if it is the whole payment stack, because for practical purposes it is.

The distinction still matters when you compare options. A traditional provider like Authorize.net is primarily a gateway, so you may pair it with a separate merchant account from a bank or acquirer. An all in one provider gives you speed and simplicity but a little less control over the underlying processing relationship. Neither is wrong. The right answer depends on your volume, your market, and how much you want to manage. If you are unsure which model fits your business, our team can talk it through, and you can request a free quote for a setup built around your needs.

The Main WooCommerce Gateway Options

WooCommerce supports a long list of gateways, but most stores end up choosing from a short set of well supported options. Here are the ones worth knowing, with the trade offs that matter in real use. None of them is universally best. The best gateway is the one that matches your customers, your country, and the payment methods your buyers expect to see.

Stripe, including WooPayments

Stripe is the default choice for a huge share of modern stores. It supports cards, wallets like Apple Pay and Google Pay, and many local methods, and it has a clean developer story. WooCommerce also offers WooPayments, which is built on Stripe technology and managed directly inside your WooCommerce dashboard, so you can see payouts and disputes without leaving the store admin. The official Stripe plugin gives you a bit more direct control, while WooPayments trades some of that for a tidy all in one experience.

PayPal

PayPal is the name customers recognise, and offering it can lift conversion because many shoppers trust the familiar button and already have an account. It handles PayPal balance payments, cards, and Pay Later options in supported regions. The trade off is a checkout that sometimes redirects the buyer to PayPal, though the modern PayPal Payments extension keeps more of the flow on your own site.

Square, Authorize.net, Mollie, and regional options

Square suits businesses that also sell in person, because it links online and point of sale under one account with shared inventory. Authorize.net is a long established gateway that pairs with a separate merchant account and appeals to businesses that already have a banking relationship. Mollie is popular across Europe for its wide support of local methods such as iDEAL and Bancontact. Beyond these, most countries have strong regional gateways that offer the local wallets and bank transfer methods your customers expect, and adding one alongside a global option is common.

How to shortlist quickly

If the list of options feels long, narrow it with three quick questions. First, is the gateway fully supported in the country where your business is registered, since availability is the hard limit that rules options in or out. Second, does it offer the payment methods your customers actually reach for, whether that is cards, a wallet button, or a local bank method. Third, does it keep the card entry on your own site so the checkout stays smooth. Any gateway that clears all three is a safe starting point, and you can refine later once real orders show you how people pay. Do not let a rare edge case drive the whole decision, because you can always add a second method for the exceptions.

Do not overthink the first choice. Many stores start with one global gateway such as Stripe for cards and wallets, add PayPal for trust, and layer in a regional method later if the data shows demand. You can always add or remove a gateway without rebuilding your store.

Connecting Stripe to WooCommerce

Stripe is a good first gateway because the setup is quick and it covers cards and wallets in one go. The steps below use the official Stripe extension, and WooPayments follows a very similar path from inside your dashboard. Work in this order and you will have live card payments without touching any sensitive data yourself.

Step by step

1. In your WordPress dashboard, go to Plugins, then Add New, and search for the Stripe payment gateway extension for WooCommerce. Install and activate it. If you prefer the terminal, the command is wp plugin install woocommerce-gateway-stripe --activate.
2. Create a Stripe account at the provider site if you do not have one, and complete the business details it asks for so your account can accept live payments later.
3. In WooCommerce, open Settings, then Payments, find Stripe in the list, and click Manage or Set up.
4. Connect the account. Newer versions offer a one click connect that uses a secure handshake, so you authorize Stripe and it links itself. Older setups ask you to paste API keys, a publishable key and a secret key, which you copy from your Stripe dashboard.
5. Turn on test mode first. In test mode Stripe gives you separate test keys and accepts test card numbers so you can place practice orders without moving real money.
6. Enable the payment methods you want, such as cards and the express wallet buttons for Apple Pay and Google Pay, and save.
7. Place a test order using a known test card, confirm the order shows as paid in WooCommerce and appears in your Stripe test dashboard, then switch off test mode and connect your live keys to go live.

Enable webhooks and secure the site

Stripe uses webhooks to tell your store about events that happen away from the checkout, such as a payment that completes later or a dispute that opens. Most modern versions register the webhook for you during connection. If you set keys manually, add the webhook endpoint from your Stripe dashboard so these updates reach WooCommerce. Your whole site should already run on HTTPS before you accept a single live payment, which you can enforce by keeping your certificate valid and, if needed, adding define( 'FORCE_SSL_ADMIN', true ); to wp-config so the admin area stays encrypted too.

If the connect step fails

A few things trip people up during connection. If the one click connect will not complete, confirm your site is loading over HTTPS with a valid certificate, since providers refuse to link an insecure checkout. If you are pasting keys by hand, make sure you have not mixed a test key with a live one, which is a common cause of silent failures. If payments authorize but orders never move past pending, the webhook is almost always the culprit, so check that the endpoint is registered and showing successful deliveries. Clearing your caching plugin after connecting also avoids the odd case where an old version of the checkout is served to the first test shopper.

Going live cleanly

When you flip from test to live, double check three things. Confirm the live keys are in place and the test keys are gone. Place one small real order yourself and then refund it to prove the full loop works end to end. Finally, watch the first day of real orders to make sure confirmations, emails, and payouts all behave. If anything looks off during the switch, our developers can review the configuration for you, and you can get a free quote for a hand.

Connecting PayPal to WooCommerce

Adding PayPal alongside cards is one of the easiest ways to reassure hesitant buyers, because the button is familiar and many shoppers already have an account. The modern PayPal Payments extension keeps most of the checkout on your own site while still offering the PayPal button and card fields. Here is how to connect it.

Step by step

1. In your dashboard, go to Plugins, then Add New, search for the official PayPal Payments extension for WooCommerce, and install and activate it.
2. Open WooCommerce, then Settings, then Payments, find PayPal in the list, and click Manage.
3. Click the connect button and sign in to your PayPal business account. PayPal uses a secure authorization, sometimes described as an OAuth style connect, so you grant access and it links your account without you copying long secret keys by hand.
4. Turn on sandbox mode to test. PayPal provides sandbox accounts, a fake buyer and a fake seller, so you can run practice purchases that move no real money.
5. Choose which buttons and methods to show, such as the PayPal button, Pay Later messaging where available, and card fields for shoppers without a PayPal account.
6. Run a sandbox purchase using your test buyer account, confirm the order is marked paid in WooCommerce and appears in the sandbox dashboard, then switch off sandbox mode.
7. Reconnect with your live account if prompted, place one real order to confirm the live flow, and you are accepting PayPal.

Placement and wording at checkout

Where the PayPal button sits changes how much it helps. Showing it both in the cart and on the checkout gives shoppers who prefer PayPal an early, obvious path, while the card fields serve everyone else. Avoid burying the option behind an extra click. The whole point of offering PayPal is to remove hesitation, so make it visible and let the shopper pick the method they trust. Keep the labels plain so it is clear which button charges a card and which uses a PayPal balance.

Offering Multiple Gateways

You are not limited to one gateway. WooCommerce lets you enable several at once and present them side by side at checkout, which is usually the smart move. Different customers trust different methods, and giving them a choice tends to lift completed orders. The trick is to offer enough choice to reassure people without cluttering the checkout with options nobody uses.

How enabling several works

Every gateway you install appears in WooCommerce, then Settings, then Payments as a row you can switch on or off. Enabled gateways show up at checkout in the order listed on that screen, and you can drag them to change that order. Put the method most of your customers use at the top, since the first option carries visual weight. A common, sensible mix is cards through Stripe as the default, PayPal directly under it for the shoppers who prefer it, and perhaps one regional method if your data supports it.

Restricting methods by condition

Sometimes you want a gateway to appear only in certain situations. You might offer bank transfer only for wholesale orders, hide a wallet for subscriptions, or show a local method only to customers in one country. Core WooCommerce lets you set which gateways appear, and conditional logic plugins or custom code can go further, showing or hiding a method based on cart total, product type, shipping country, or user role. Keep these rules simple and documented, because a hidden gateway that no one remembers configuring is a common source of confusion later.

• Set a clear default so most shoppers never have to think about which method to use.
• Limit the number of visible options to the ones that actually get used, since too many choices slow people down.
• Match methods to how you sell, for example enabling manual bank transfer only for invoice style business orders.
• Test every enabled method before a big campaign so a rarely used gateway does not fail during a rush.

Here is a simple example of how the ordering plays out. Say most of your customers pay by card, a meaningful share prefer PayPal, and a handful of business buyers pay by bank transfer against an invoice. You would enable cards through Stripe and list it first as the default, place PayPal directly beneath it so the loyal PayPal crowd sees it without scrolling, and enable manual bank transfer but restrict it to the wholesale user role so retail shoppers never see it. The result is a checkout that looks simple to every customer while quietly serving three different buying habits. That is the practical goal of running multiple gateways, not to show every option to everyone, but to show each shopper the one they already trust.

If you plan to run several gateways with per method rules, it is worth having someone map the logic once so it stays clean as the store grows. Our WordPress services cover this kind of setup, and a tidy payment configuration saves a surprising amount of support time down the line.

Understanding Processing Fees

Every card sale carries a cost, and understanding the shape of that cost helps you choose a gateway and price your products sensibly. We will not quote figures here, because rates change and vary by country, plan, and card type, but the structure is consistent across providers, so you can compare them on the same terms.

What makes up the cost

The headline charge for a typical transaction is usually a percentage of the sale plus a small fixed amount per transaction. The percentage scales with the order value while the fixed part is the same on every sale, which is why very small orders feel proportionally more expensive to process. On top of that base, watch for a handful of extra costs that not every store notices at first.

Fees are not the only number that matters

It is tempting to pick the gateway with the lowest headline percentage, but that can be a false economy. A slightly higher rate on a gateway that converts better, pays out faster, and rarely fails at checkout often earns more than a cheaper option that loses sales. Think about the total picture, the rate, the extra charges, the payout speed, and the checkout experience, rather than the percentage alone. One point worth remembering is that WooCommerce itself does not add its own transaction fee on top of your processor, unlike some hosted platforms, so what you pay is what your gateway charges.

One more habit saves money over time. Review your gateway statements every few months rather than setting the account and forgetting it. Providers adjust pricing, your sales mix shifts, and a plan that made sense at launch may no longer be the most economical once your volume grows or your customer base spreads across new countries. A short quarterly look at what you are actually paying, against what you are selling, keeps the cost in check and flags any surprise charge such as a rising dispute rate before it becomes a habit.

Because rates depend on your volume and market, the only accurate cost is a quote built around your actual sales. If you want help reading provider pricing and choosing the most economical setup for your store, you can get a free quote and we will lay out the options in plain language.

Security and PCI Compliance

Taking card payments comes with responsibilities, and the good news is that a modern setup carries most of that weight for you. The rules that govern card handling are called PCI DSS, short for the Payment Card Industry Data Security Standard. You do not need to memorise the standard, but you do need to set up your store so that it stays in the lightest, safest part of it.

Keep raw card data off your server

The single most important rule is that your WordPress site should never see, touch, or store a raw card number. Reputable gateways use hosted fields or a hosted page, where the card details are captured directly by the gateway inside an element embedded in your checkout. The number goes straight to the gateway and never lands on your server. This is what keeps you eligible for the simplest compliance path, often referred to as SAQ A, which is the shortest self assessment because you are not handling card data yourself. If a setup ever asks you to store card numbers in your own database, walk away from it.

The layers that protect a checkout

• SSL and HTTPS encrypt everything moving between the shopper and your site, so data cannot be read in transit. Your whole store, not just the checkout, should load over HTTPS.
• Tokenization replaces a card number with a meaningless token that the gateway can use for repeat charges, so you can offer saved cards and subscriptions without ever storing the real number.
• 3D Secure and strong customer authentication add a verification step, often a prompt from the customer bank, that cuts fraud and is required in some regions. Good gateways trigger it automatically when needed.
• Hosted fields keep the sensitive input under the gateway control, which is what shrinks your PCI scope to the smallest self assessment.

Housekeeping that keeps you safe

Beyond the gateway itself, a few habits protect your store. Keep WooCommerce, your payment extensions, your theme, and WordPress core updated, since security fixes arrive through updates and an outdated plugin is a common way in. Use strong admin passwords and limit who has administrator access. Remove plugins you no longer use. A fast, well maintained site is also a safer one, and our guide on how to speed up a WordPress website pairs well with this section because performance and security upkeep go hand in hand. If you would rather have a team keep the store patched and monitored, that ongoing care is exactly what our maintenance work covers.

Testing With Sandbox and Test Cards

Never point a live gateway at real customers without testing first. Every major provider gives you a safe way to place practice orders that move no real money, and using it catches the small mistakes that would otherwise turn into failed sales or angry emails. Testing takes a few minutes and saves hours.

How test and sandbox modes work

Stripe calls it test mode, PayPal calls it sandbox, and both do the same thing. They give you a separate set of credentials and accept fake payment details so you can run the full checkout, from cart to confirmation, exactly as a customer would. In Stripe test mode you use published test card numbers, for example a common test card is 4242 4242 4242 4242 with any future expiry date and any card security code. In the PayPal sandbox you sign in with a test buyer account instead of a real one. Because the environment is separate, nothing you do in test mode affects your real orders or your real balance.

A short test script to run every time

1. Place a normal order with a test card and confirm it reaches the thank you page and is marked paid.
2. Try a card number that is designed to be declined, so you can see how your checkout handles a failure and whether the message is clear.
3. Trigger a payment that requires 3D Secure and confirm the extra verification step appears and completes.
4. Issue a refund from WooCommerce and confirm it flows back through the gateway in test mode.
5. Check that order confirmation emails reach both you and the customer address you used.

Run this short script whenever you add a gateway, change a plugin, or update WooCommerce, because payment flows are exactly the kind of thing an unrelated update can quietly break. Only after every step passes should you switch to live mode and connect real credentials.

Failed Payments, Refunds, and Webhooks

A checkout is not just the happy path. Cards get declined, customers ask for their money back, and some payment events finish minutes after the shopper leaves. A store that handles these gracefully keeps customers calm and your books accurate. Here is how each one works in WooCommerce.

Failed and pending payments

When a card is declined, WooCommerce marks the order as failed or pending and, in most setups, keeps the cart so the shopper can try again with a different method. The most useful thing you can do is make the on screen message clear and reassuring rather than blaming the customer, since many declines are simple bank checks, not fraud. Offering a second gateway helps here, because a card that fails on one method sometimes succeeds through another. Keep an eye on your failed order rate, and if it climbs, look at whether 3D Secure prompts are completing and whether a particular card type is struggling.

Refunds

WooCommerce supports refunds directly from the order screen when your gateway allows it. Open the order, click refund, choose a full or partial amount, and the request goes back through the gateway to return the money to the customer original method. This is cleaner than refunding inside the gateway dashboard alone, because doing it from WooCommerce keeps the order status and your records in sync. Set a plain refund policy and process approved refunds promptly, since a slow refund is a common trigger for a chargeback, which costs you a dispute fee on top of the refunded sale.

Webhooks

Webhooks are messages the gateway sends to your store when something happens on their side, such as a delayed payment clearing, a subscription renewing, a payout completing, or a dispute opening. Without working webhooks, your store can miss these updates and show the wrong status. Most modern extensions set up the webhook automatically when you connect, but if you configured keys by hand you may need to add the endpoint in the gateway dashboard. After setup, confirm the connection is healthy by checking the gateway webhook log for successful deliveries. When a store shows orders stuck in a pending state, a broken or missing webhook is one of the first things to check.

These moving parts are why many owners prefer to have a developer set up and verify the whole payment loop once, then hand over a store that simply works. If you want that peace of mind, you can request a free quote and we will build and test the full flow, declines, refunds, and webhooks included.

Choosing the Right Gateway for Your Market

The best gateway on paper is the wrong one if your customers do not use it. Payment habits differ sharply by country and by industry, so the final decision should start with your buyers, not with a feature list. A gateway that dominates one market may be almost unknown in another.

Start with how your customers pay

Look at where your customers live and how people there prefer to pay. In some markets cards and global wallets cover almost everyone. In others a local bank transfer method or a regional wallet is the norm, and leaving it out costs you real sales. If you sell across borders, you will likely want a global gateway for cards and wallets plus one or two local methods for your biggest regions. The goal is that a shopper reaches checkout and immediately sees a method they already trust.

Weigh the practical factors together

• Method coverage: does it offer the cards, wallets, and local options your customers expect?
• Availability: is the gateway fully supported in the countries where you and your customers are based?
• Payout speed and currency: does it pay out in your currency on a schedule your cash flow can live with?
• Checkout experience: does it keep the payment on your site and support wallets for fast, one tap purchases?
• Support and reliability: is there real help when a payment issue appears, and is the extension actively maintained?

A simple way to decide

For most stores, a sensible default is to start with one strong global gateway such as Stripe for cards and wallets, add PayPal for the shoppers who trust it, and then review your analytics after launch to see whether a regional method would pay for itself. You can add or remove gateways at any time, so the first choice is not permanent. Begin with broad coverage, watch how people actually pay, and refine from there.

Payments reward getting the details right, from the gateway choice to the security layers to the webhook that quietly keeps your orders accurate. If you would like a store where all of that is set up, tested, and handed over ready to sell, our team does exactly this kind of work every week. Get a free quote and we will build a checkout your customers can trust.