Payment Gateways for Online Stores in Egypt and MENA: How to Choose

Most advice about taking payments online is written for markets where everyone pays by card and the obvious gateway is available to anyone who signs up. Egypt and much of the Middle East work differently. The best-known international gateway may not accept a business registered in your country at all, a large share of your customers may want to pay with a wallet, a national debit card or cash, and the approval process can take longer than building the store.

This guide is for the point just before you choose. It covers what is actually available to a business in Egypt, Saudi Arabia and the UAE, which payment methods customers there expect at checkout, what a gateway will ask you for, and the questions worth asking before you sign anything. It does not rank providers for you, because the right answer depends on where you are registered and who you sell to, and anyone who names a single best gateway without asking those two things is guessing.

What is a payment gateway?

A payment gateway is the service that takes a customer's payment details at checkout, sends them for authorisation, and tells your store whether the payment succeeded. It usually comes bundled with the merchant account that receives the money, so in practice choosing a gateway also means choosing who settles your sales and on what terms.

The distinction that matters for a store owner is between the gateway and the payment methods it carries. A card is a payment method. So is a mobile wallet, a national debit scheme like Meeza in Egypt or mada in Saudi Arabia, a buy-now-pay-later plan, or a cash payment made against a reference code. A gateway is only as useful as the methods it supports in your market, which is why two gateways with similar fees can perform very differently for the same store.

Why can't you just use Stripe or PayPal?

You often can, but not everywhere. At the time of writing, Stripe's own list of supported countries includes the UAE but not Egypt or Saudi Arabia, so a business registered in either of those two countries cannot open a Stripe account in its own name. PayPal's business features also differ by country. Check what you can actually sign up for before you design anything around it.

This catches out more first-time store owners than any other single thing. A platform demo shows a smooth Stripe checkout, the store gets built around it, and only at the end does someone discover the account cannot be opened for an Egyptian company. Workarounds exist, such as registering a company abroad, but they bring their own tax, banking and legal questions, and they are a business decision rather than a technical setting.

There is a second, quieter problem. Even where an international gateway is available, it may not carry the local methods your customers prefer. A card-only checkout in a market where many buyers pay with wallets or cash quietly turns away orders that were ready to happen.

Which payment methods do customers in Egypt expect?

Egyptian shoppers pay with a wider mix of methods than card-first markets. Expect demand for Visa and Mastercard cards, Meeza cards (Egypt's national debit card scheme), mobile wallets such as Vodafone Cash, cash payments made against a Fawry reference code, instalment plans from providers such as valU, and cash on delivery.

Fawry deserves a specific explanation because it is unfamiliar to anyone used to card-first markets. The customer chooses Fawry at checkout and receives a reference number. The order stays pending until they pay that reference in cash at a Fawry outlet or through the Fawry app, and the gateway then confirms the payment to your store. The reference expires after a period set by the integration, so your store needs to handle unpaid orders that simply lapse.

Local providers are built around this mix. Paymob, for example, is an Egyptian payments company that also operates in several Gulf markets, and Fawry runs its own online payment service alongside its outlet network. InstaPay, the instant bank transfer network the Central Bank of Egypt launched in 2022, is widely used between individuals, and some gateways have started to offer it at checkout, so ask whether yours does rather than assuming.

What changes when you sell in Saudi Arabia and the UAE?

In Saudi Arabia the key word is mada, the national payment network behind most local debit cards. A gateway that cannot process mada online will fail many Saudi shoppers at the final step. In both Saudi Arabia and the UAE, Apple Pay and buy-now-pay-later options such as Tabby and Tamara are common at checkout.

For Saudi Arabia, confirm mada support in writing before anything else. Several regional and international providers process it online, including HyperPay, PayTabs and Checkout.com, but support can depend on how your account is set up, so it is a question to ask rather than a box to assume is ticked.

The UAE is the most open of the three markets. International gateways such as Stripe accept businesses registered there, and regional providers compete alongside them. That makes it the easiest market in which to pick a gateway and the one where comparing offers properly pays off most, because you genuinely have a choice.

If you sell from Egypt into the Gulf, or the other way round, remember that where your business is registered usually decides which gateways you can use, while where your customers live decides which methods you need. Those two answers can point in different directions.

Local gateway or international gateway?

Choose a local gateway when most of your customers are in one country and pay with local methods. Choose an international gateway when you sell across borders, mostly to card holders, and your business is registered in a country it supports. Many regional stores end up needing both.

The trade-off is fairly consistent. Local gateways tend to win on the methods your customers use and on settling into a local bank account in local currency. International gateways tend to win on developer tooling, platform plugins and accepting cards from abroad. Neither is better in general. The useful question is which one your first hundred orders will actually go through.

What should you ask a gateway before you sign?

Ask which local methods are live, whether a business with your legal form in your country can sign up, which currency you settle in, how long settlement takes, the complete fee schedule, whether it has a maintained plugin for your platform, how refunds and disputes work, and whether the payment page is hosted by the gateway.

Get the answers in writing, ideally as the contract or the published fee schedule. Sales conversations tend to quote the headline transaction rate and leave out setup fees, monthly fees, refund fees, chargeback fees and currency conversion, and those are often what decide which offer is cheaper for a small store.

What will the gateway ask you for?

Expect a commercial registration, a tax registration, identification for the owners or directors, and a bank account in the business's own name. Most gateways also review your website before approval, so the store should be live, or close to it, with prices, contact details and clear terms, refund and privacy policies.

The website review is the part that surprises store owners. A gateway is taking on risk when it processes your payments, and a half-finished site with no refund policy and no way to reach you looks like risk. Have the policy pages written and visible before you apply, not after the application is returned.

Approval is usually the slowest step in launching a store, and it is the one that working faster on the build cannot shorten. Apply early, as soon as the business documents and a reviewable version of the site exist. Our guide on how to start an online store puts this step in its place in the wider launch order.

How does the payment page affect your security work?

If customers type their card details on a page hosted by the gateway, or into fields the gateway embeds in your checkout, your own server never handles the card number. That greatly reduces the card-security work your store carries under PCI DSS, the industry's card-data security standard, though it does not remove it entirely.

Under PCI DSS, a store that sends customers to a compliant provider's hosted page, or embeds the provider's payment fields, normally qualifies for the shortest self-assessment questionnaire, known as SAQ A. Your website is still in scope, because it decides where the customer is sent, so it still needs to be kept updated and served over HTTPS. If you build a checkout that collects card numbers on your own server, the burden grows considerably. For almost every small or mid-sized store, the hosted or embedded option is the sensible default.

Card payments online usually also include an authentication step, known as 3-D Secure, where the customer confirms the payment with their bank, often through a one-time code or their banking app. It adds a moment of friction, but it also shifts responsibility for many fraud disputes away from you, and in many markets banks expect it.

Should you still offer cash on delivery?

Usually yes, if you sell within Egypt. Cash on delivery remains a common way to pay, and a store without it turns away customers who are willing to buy. Treat it as an operational choice as well as a payment method, because it brings cash reconciliation with your courier and a higher rate of refused deliveries than prepaid orders.

The practical middle ground many stores reach is to offer cash on delivery and make prepaid options easy and visible beside it, so customers who are comfortable paying online do so. Watch the share of refused cash orders over the first few months. If it is high in a particular area or for a particular product, that tells you where to ask for prepayment.

Can you use more than one gateway?

Yes, and regional stores often do. A common setup is a local gateway for local cards, wallets and cash references, plus an international gateway for customers abroad, and possibly a buy-now-pay-later provider on top. Each additional provider adds a dashboard to reconcile and an integration to maintain, so add them for a reason.

Add a second gateway when you can name the orders the first one is losing: customers abroad whose cards are declined, a market whose national scheme your gateway does not carry, or a large basket size that would benefit from instalments. Adding gateways in case they help mostly adds checkout options that confuse customers and monthly reports that do not match.

A sensible starting setup

If you sell only within Egypt, start with one local gateway that covers cards, Meeza, wallets and Fawry references, and keep cash on delivery. If you sell in Saudi Arabia, start with a gateway that confirms mada, Apple Pay and the instalment options your customers use. If you sell from the UAE to international customers, an international gateway may be enough on its own.

Whatever the market, make the first real transactions yourself before launch: a successful card payment, a declined card, a wallet payment, a refund and an unpaid reference that expires. Each one should leave the order in the right state in your store. A store that handles the failure cases correctly on day one saves a great deal of manual cleanup later.

If you are still deciding how the store itself should be built, our comparison of custom websites, builders and templates applies directly: the most common reason a store outgrows a hosted platform is a payment method the platform will not support.