Payment Gateways for WordPress Websites (2026)

Originally published: April 30, 2025 · Last reviewed and updated: October 2026

A payment gateway is the service that takes a customer’s payment on your WordPress site and moves the money to your bank account. The one you choose affects which customers can pay you, how much each sale costs, and how much security work falls on you.

This guide explains how gateways connect to WordPress, compares the main options in 2026, and walks through choosing and setting one up.

The Short Answer

For most WordPress stores, start with Stripe or WooPayments for cards and wallets, and add PayPal as a second option if your customers expect it. If most of your customers are in one region, add a local gateway that supports the methods they actually use, such as Mollie in much of Europe, Razorpay in India, or Xendit, Midtrans, or Tripay in Indonesia.

Prefer a gateway whose payment form is hosted by the provider (a redirect or an embedded iframe). That keeps card data off your server and keeps your PCI DSS obligations as small as possible. Always run test payments before going live, and check current fees on each provider’s own pricing page.

How Payment Gateways Connect to WordPress

Integration type	How it works	Security burden on you	Example
Redirect (hosted page)	Customer leaves your site to pay on the provider’s page, then returns	Lowest	PayPal standard buttons, many local gateways
Embedded form (iframe / hosted fields)	Payment fields load from the provider inside your checkout	Low, but your checkout page must be protected from script tampering	Stripe, WooPayments, Square
Direct (card data hits your server)	Your site receives card numbers and sends them to the processor	Highest; rarely appropriate for small businesses	Older custom integrations

Since PCI DSS v4.0.1, merchants using embedded payment forms must also confirm their site is not vulnerable to script attacks that could affect the payment page. The PCI Security Standards Council explains the options in its FAQ on SAQ A eligibility. In practice, keep third-party scripts off your checkout page, keep WordPress and plugins updated, and ask your provider what they confirm on your behalf.

Payment Gateways Compared

Gateway	WordPress plugin	Best for	Notes
Stripe	WooCommerce Stripe Payment Gateway	Cards and wallets in many countries	Apple Pay and Google Pay via express checkout; strong developer tools
WooPayments	WooPayments	WooCommerce stores that want payments managed in the dashboard	Built by the WooCommerce team; check country availability
PayPal	WooCommerce PayPal Payments	Customers who prefer PayPal, international buyers	Also offers card processing and Pay Later in some countries
Square	WooCommerce Square	Businesses that also sell in person	Syncs with Square’s point-of-sale system
Authorize.Net	Official and third-party WooCommerce extensions	Merchants with an existing US merchant account	Traditional gateway; often paired with a separate merchant account
Mollie	Mollie Payments for WooCommerce	European stores	Local methods such as iDEAL and Bancontact
Razorpay	Razorpay for WooCommerce	Stores selling in India	UPI, cards, netbanking, wallets
Xendit, Midtrans, Tripay	Xendit, Midtrans, Tripay	Stores selling in Indonesia and Southeast Asia	Virtual accounts, e-wallets, QRIS, convenience-store payments

Fees vary by country, payment method, and volume, and they change often, so this guide does not list them. For example, international cards and currency conversion usually cost extra on top of the base rate. Compare the full cost on each provider’s pricing page for your country.

Check That the Plugin Is Maintained

A gateway is only as reliable as its WordPress plugin. At the time of review, the WordPress.org listings for both the Midtrans and Tripay plugins warned that they had not been tested with the latest three major WordPress releases. That does not mean they are broken, but it does mean you should test them on staging and ask the provider about updates before relying on them.

Before installing any gateway plugin, check:

Last updated date and “Tested up to” version on WordPress.org.
WooCommerce compatibility, including HPOS and the block-based Checkout. Our guide to WordPress e-commerce plugins explains both.
Who publishes it. Prefer the provider’s official plugin over third-party ones.
Support responses in the plugin’s support forum.

Step-by-Step: Add a Payment Gateway to WooCommerce

Open a merchant account with the provider and complete business verification.
Install the official plugin from WordPress.org or the provider’s site.
Connect the account (usually via OAuth or API keys) under WooCommerce → Settings → Payments.
Enable test mode and place test orders, including a failed payment and a refund.
Set up webhooks if the plugin asks for them, so orders update when payments succeed, fail, or are refunded.
Check your emails. Make sure order and payment emails arrive; see our fix for WordPress not sending emails if they do not.
Go live and place one small real order before announcing the store.

Keep Checkout Fast and Secure

Run the whole site on HTTPS; our guide to adding SSL to WordPress covers the steps.
Exclude cart, checkout, and account pages from page caching. See our comparison of WordPress cache plugins.
Load as few third-party scripts on checkout as possible.
Protect admin accounts with two-factor authentication, following our WordPress security best practices.

Common Mistakes

Choosing a gateway that does not support your country, currency, or bank for payouts.
Offering only cards in markets where customers mostly use bank transfers, e-wallets, or QR payments.
Skipping webhook setup, which leaves orders stuck as “pending payment”.
Installing an unmaintained plugin without testing it on staging.
Adding chat widgets and trackers to the checkout page, which adds risk and slows it down.

FAQ

Can I use more than one payment gateway?

Yes. WooCommerce supports several gateways at once. A common setup is one card and wallet gateway plus PayPal or a local method.

Do I need an SSL certificate to accept payments?

Yes. Every page that collects personal or payment data must use HTTPS, and most gateways require it.

Is my site PCI compliant if I use Stripe or PayPal?

Using a provider’s hosted or embedded form greatly reduces your scope, but you are still responsible for completing the right self-assessment and keeping your site secure. Ask your provider which questionnaire applies to your integration.

Which gateway is best for Indonesian customers?

A local gateway such as Xendit, Midtrans, or Tripay, because they support virtual accounts, e-wallets, and QRIS, which many Indonesian customers prefer. Test the plugin on your WordPress and WooCommerce versions first.

What payment options does WooCommerce include without extra plugins?

WooCommerce core includes offline methods: direct bank transfer, check payments, and cash on delivery. Card and wallet payments need a gateway plugin.

The Bottom Line

The right WordPress payment gateway is the one your customers already trust and use, with an official, well-maintained plugin. For most stores that means Stripe or WooPayments plus PayPal, with a local gateway for regional payment methods. Use hosted or embedded payment forms, test every flow before launch, and review fees and plugin updates regularly.