Plugin details checked 1 October 2026.
Quick answer: the practical setup for Gulf WooCommerce stores
For most Gulf stores, WooCommerce payment gateways work best as one multi-country gateway for cards and Apple Pay, plus the local scheme each market expects: mada in Saudi Arabia, KNET in Kuwait, and Benefit in Bahrain.
In Saudi Arabia, gateway guides advise choosing a gateway licensed by the Saudi Central Bank (SAMA) that supports mada through 3-D Secure. In the UAE, cards, Apple Pay and buy-now-pay-later options such as Tabby and Tamara carry most of the weight. Before you choose, check three things on the gateway’s own pages: which countries and local methods it supports for your merchant account, whether its WooCommerce plugin is actively maintained, and what going live requires from your business. I checked the plugin details in the table below on 1 October 2026. Fees, availability and rules change, so confirm with the provider before you commit.
WooCommerce payment gateways compared: plugins and status
I built this comparison of WooCommerce payment gateways from each plugin’s WordPress.org listing and the vendors’ own documentation, not from other blogs. Where I could not confirm something, the cell says so.
| Gateway | Countries and local methods named by the vendor or plugin | Where the WooCommerce plugin comes from | Plugin last updated | WordPress “tested up to” |
|---|---|---|---|---|
| Moyasar | Saudi Arabia and MENA. Mada, Visa, Mastercard, American Express, Apple Pay, Samsung Pay, STC Pay | WordPress.org (900+ installs) | 27 Sep 2026 (v8.4.1) | 7.0.6 |
| HyperPay | Credit card, mada, STC Pay “and more”. Countries are not stated in the listing | WordPress.org (600+ installs) | 13 Aug 2026 (v6.6.0) | 6.9.9 |
| PayTabs | Saudi Arabia: mada, STC Pay, Ur Pay. Kuwait: KNET (KN Pay). Oman: OmanNet. Cards, Apple Pay and UnionPay globally | PayTabs download. Not found in the WordPress.org directory on 1 Oct 2026. The vendor’s article describes plugin v1.5 | See the vendor’s release notes | Not applicable |
| Tap Payments | Tap’s WooCommerce page documents KNET and cards. Confirm mada and Benefit in your Tap account | Download from Tap’s GitHub repository (Tap-Payments/Tap-WooCommerce-V2) | See the repository | Not applicable |
| MyFatoorah | The listing appears in WordPress.org searches for KNET. Confirm the methods for each country in your account | WordPress.org (2,000+ installs) | 17 Feb 2026 (v2.2.11) | 6.9.9 |
| Payzah | Kuwait. KNET and credit cards | WordPress.org (40+ installs) | 25 Feb 2026 (v1.8.15) | 6.9.9 |
| Telr | Dubai-based, with several Gulf markets. I could not verify methods or the plugin source on 1 Oct 2026, so confirm directly with Telr | Vendor | Not verified | Not verified |
| Tabby (buy now, pay later) | Instalment payments | WordPress.org (4,000+ installs) | 19 Aug 2026 (v5.13.3) | 7.1.2 |
| Tamara (buy now, pay later) | Instalments. The listing says it accepts mada, Apple Pay or cards | WordPress.org (2,000+ installs) | 8 Sep 2026 (v1.9.9.23) | 7.0.6 |
| Amazon Payment Services | Cards across the Middle East | WordPress.org listing last updated 15 Dec 2023, tested up to 6.4.12. Check the vendor for a current build | 15 Dec 2023 | 6.4.12 |
One thing the table shows. WordPress itself was at 7.1.2 on the day I checked. Several Gulf gateway plugins still list 6.9.9 or 7.0.6 as the newest version they have been tested with. That does not mean they are broken, and many keep working. It does mean you should test every plugin on a staging copy before updating WordPress or WooCommerce, and ask the vendor how quickly they certify new releases.
How Gulf checkout differs from the rest of the world
Shoppers in the region pay in several ways at once. Local debit schemes sit next to international cards:
- mada in Saudi Arabia, KNET in Kuwait, and Benefit in Bahrain.
- Apple Pay and cards, which most stores should offer everywhere.
- Wallets such as STC Pay in Saudi Arabia.
- Buy now, pay later, with Tabby and Tamara common in Saudi Arabia and the UAE.
- Cash on delivery, which many regional stores still offer.
A store that only takes international cards will lose shoppers who expect their local scheme. The aim of your gateway choice is to cover those expectations without adding a different plugin for every payment method.
WooCommerce payment gateways in the UAE
Cards and Apple Pay do most of the work in the UAE, and buy-now-pay-later is common at checkout. UAE VAT is 5%, so set your WooCommerce tax rates and invoice format accordingly. Most stores here choose a multi-country gateway so the same integration can serve other Gulf markets later.
If you are building or fixing a store, see my WordPress developer in Dubai, WooCommerce developer in Dubai, WordPress developer in Abu Dhabi and WooCommerce developer in Abu Dhabi pages.
WooCommerce payment gateways in Saudi Arabia
mada is the debit network Saudi shoppers expect. SAMA describes it as one of the national payment systems it owns, launched in 1990, that reaches e-commerce sites through the international card networks. Gateway guides advise using a SAMA-licensed provider that supports mada through 3-D Secure, and a merchant account typically needs your commercial registration and bank details. Your gateway’s own documentation is the authority on what it needs from your business.
Saudi stores also have to think about e-invoicing. VAT is 15%, and ZATCA’s Phase 2 integration requirements are rolling out in waves. See my guide to ZATCA e-invoicing for WooCommerce.
I have integrated mada acceptance on WooCommerce stores. For Saudi stores I usually start from a gateway that is clearly licensed and supports mada, then add STC Pay or buy-now-pay-later only if your customers ask for them. See my pages for WordPress developer in Riyadh and WooCommerce developer in Riyadh.
WooCommerce payment gateways in Kuwait
KNET is Kuwait’s national debit scheme and the method most shoppers expect. You can reach it through a direct integration with your bank, or through a gateway that includes it. PayTabs lists “Knet – KN Pay” in Kuwait, Tap’s WooCommerce page documents KNET, and Payzah’s plugin is built specifically for KNET and cards in Kuwait. Kuwaiti dinar prices use three decimal places, which affects your WooCommerce currency settings. See my full guide to KNET on WooCommerce and my page for a WordPress developer in Kuwait.
WooCommerce payment gateways in Bahrain
Benefit is Bahrain’s national scheme. The FaltaPay plugin listing says it accepts mada, KNET and Benefit through HyperPay or Tap, so a multi-country gateway is one way to cover it. Bahraini dinar prices also use three decimals. Confirm Benefit support in your own merchant account before you promise it to customers. See my page for a WordPress developer in Bahrain.
WooCommerce payment gateways in Qatar
Verified, plugin-level information for Qatar is thinner than for the other markets, so the safe approach is to confirm with the provider. A multi-country gateway for cards and Apple Pay is the usual starting point, and you should ask which local debit schemes your account supports. See my pages for a WordPress developer in Doha and a WooCommerce developer in Doha.
WooCommerce payment gateways in Oman
PayTabs lists OmanNet for Oman. Omani rial prices use three decimal places. As elsewhere, confirm what your own account supports. See my page for a WordPress developer in Oman.
WooCommerce payment gateways setup checklist for the Gulf
This is the list I work through on every Gulf integration, whichever gateway you pick.
- Currency and decimals. Set the store currency first. KWD, BHD and OMR use three decimal places, so check that WooCommerce and the gateway both round the same way, or totals will not match.
- HTTPS everywhere. Gateways redirect shoppers back to your site and call your server. Both need a valid certificate.
- Server-to-server confirmation. Do not mark an order paid because the shopper landed on a thank-you page. Rely on the gateway’s callback or webhook, and make sure your firewall, CDN or security plugin does not block it.
- Order statuses. Map every outcome: paid, failed, cancelled, expired and refunded. Test each one.
- 3-D Secure. Test the full challenge flow on a real phone, including when the shopper abandons it.
- Sandbox first. Run success, failure, cancel and timeout cases in the gateway’s test mode before going live.
- Cache exclusions. Cart, checkout and account pages should never be cached. Check your caching plugin and CDN rules.
- Refunds. Decide whether refunds start in WooCommerce or in the gateway dashboard, and test a partial and a full refund.
- Tax and invoices. Set the VAT rate for each country you sell in, and check what your invoices must show.
- Arabic checkout. Check labels, error messages, emails and the gateway’s own payment page in Arabic and in right-to-left layout. See my Arabic RTL WooCommerce checklist.
- Logging. Turn on gateway logging while you test and turn it off, or restrict who can read it, when you go live.
- Staging for updates. Test plugin and WooCommerce updates on a copy of the site before updating the live store.
Payment scripts and checkout speed
Gateway plugins often add scripts and styles to every page. On a phone, that can slow your whole store, not just the checkout. Load payment scripts only where they are needed, defer what you can, and measure the cart and checkout pages on a throttled mobile connection rather than a fast desktop. If your checkout feels slow, see my WordPress performance optimization service and the WooCommerce performance case study.
How to choose the right WooCommerce payment gateways
- Start with your markets. List the countries you sell to now and in the next year.
- Pick one multi-country gateway that supports cards, Apple Pay and the local scheme in each of those markets, and has a recently updated WooCommerce plugin.
- Add buy-now-pay-later only if your average order value and customers suit it.
- Keep cash on delivery only if you can handle the fulfilment and returns.
- Test before you launch, using the checklist above, in each country you sell to.
If you want a second pair of eyes on a gateway choice or a failing checkout, see my WooCommerce developer page.
Frequently asked questions
Which WooCommerce payment gateways support mada?
Several do, including Moyasar, HyperPay, and Tamara, whose plugin listings name mada, and PayTabs, which lists it for Saudi Arabia. Confirm that your own merchant account has it enabled.
Does PayTabs work with WooCommerce?
Yes. PayTabs documents a WooCommerce plugin and lists mada, STC Pay and Ur Pay for Saudi Arabia, KNET (KN Pay) for Kuwait, and OmanNet for Oman. It is a vendor download, not a WordPress.org plugin.
How do I accept KNET on WooCommerce?
Use a direct KNET integration through your bank or a gateway that includes KNET, such as PayTabs, Tap, or Payzah. Set your currency to Kuwaiti dinar and test the full flow first. See my KNET guide.
Which WooCommerce payment gateways cover every Gulf country?
No single gateway is certain to cover every country and local scheme for every merchant account. Multi-country providers such as PayTabs and Tap cover several, but you should confirm each country and method for your account.
Do I need a local company to open a gateway account?
Often a gateway asks for business documents such as a commercial registration, and requirements differ by provider and country. Ask the provider before you build.
Can I accept Apple Pay with these gateways?
Several of the gateways in the table list Apple Pay, including Moyasar and PayTabs. Apple Pay also needs domain verification and a supporting checkout, so test it on a real device.
Why does my checkout show the wrong decimals?
Kuwaiti, Bahraini and Omani currencies use three decimal places. Set the number of decimals in WooCommerce and check that the gateway rounds the same way.
How do I test a gateway before going live?
Use the gateway’s sandbox with test cards or accounts, and run success, failure, cancellation, and timeout cases. Check order status and emails after each one.
