How to Choose a Payment Gateway for Egypt and the Gulf

Picture a store owner who spends a week comparing gateway fee sheets, picks the cheapest one, and launches. On day two a customer in Riyadh tries to pay with Mada and the checkout throws an error. On day nine the money from the first sales still hasn't reached the bank account. Nothing was wrong with the fee sheet. The owner just compared the one thing that was easy to compare.

Short answer: Choose a payment gateway by the payment methods your customers actually use, then by how fast and in which currency you get paid, then by how well the provider's technical side behaves. Price matters, but it comes last. For a store selling in both Egypt and the Gulf, that usually means a local gateway for each market instead of one provider for everything.

What does a payment gateway actually do?

A payment gateway is the service that collects your customer's payment details at checkout, sends them to the bank or wallet for approval, and tells your store whether the payment went through. It also keeps card data off your own server, which spares you a lot of security and compliance trouble.

Some providers are only a gateway. Others also act as the payment processor, and some hold your money for a while before settling it to you. You don't need to memorise the vocabulary. You need three answers about any provider: which payment methods it accepts, when and in what currency you get paid, and what happens when something goes wrong.

Which payment methods do your customers actually use?

Start here, before you open a single provider's website. The best gateway on paper is useless if it doesn't offer the button your customers reach for.

In Egypt, shoppers commonly pay with local and international cards, mobile wallets, cash at a Fawry outlet for online orders, and a growing number of instalment plans. In Saudi Arabia, Mada cards are used by a huge share of shoppers, with Apple Pay and international cards close behind, and wallets and buy-now-pay-later options on top.

Don't guess. If you already sell through social media or WhatsApp, look at how people pay you today. That list is your shortlist of methods, and it will often surprise you.

Which gateways do stores in each market use?

These are examples of providers that Egyptian and Gulf stores commonly look at, not a ranking:

• Egypt: Paymob, Fawry and Kashier
• Saudi Arabia and the Gulf: Tap Payments, Moyasar, HyperPay and PayTabs

Names change, products get added, and what you can use depends on your business type and your documents. Check current availability and fees with each provider before you commit to any of them.

What should you ask before you sign?

A call with a provider's sales team is the cheapest research you'll do. Go in with these questions:

• Which currencies can I be paid in, and which one do you settle in?
• How many days pass between a customer paying and the money arriving in my bank account?
• What documents does onboarding need, and how long does approval usually take?
• How are full and partial refunds handled, and can I trigger them from my own admin panel?
• Is there a test mode with test cards, so we can try failures and not only successes?
• Does your API send webhooks, meaning server-to-server messages about payment status?
• How good is the documentation, and is there a real person to contact when a payment gets stuck?

One warning from experience. Approval and onboarding often take longer than the website build itself, because the provider verifies your business. Start the paperwork in week one, not the week before launch.

Why one gateway is rarely enough

Two reasons. First, coverage: the gateway that's best for Egyptian cards and wallets may not be the one that handles Mada well, so a store that sells in both markets ends up needing more than one. Second, resilience. When your only gateway has a bad afternoon, your checkout is closed.

On Shop2Change, a custom digital services store we built, five payment gateways and eight service providers feed one order flow, and each order is processed according to its service and provider type. The architecture is designed so adding a provider is a small, contained change. The same principle works for gateways: keep each one behind its own small piece of code, so the rest of the store never needs to know which one took the money.

How does the gateway connect to your store?

There are three common patterns. The customer can be sent to the provider's hosted payment page and returned afterwards. The provider's payment fields can be embedded inside your own checkout. Or your server can talk to the provider's API directly, which is rare and carries the heaviest security responsibility.

The hosted page is the simplest and safest, and the embedded fields feel smoother. Both are fine. What matters more is a rule that applies whether you run a plugin on WordPress or a custom build (we compare those in Laravel or WordPress):

Never mark an order as paid because the customer's browser landed on your thank-you page. Browsers close, connections drop, and anyone can type a URL. The reliable signal is the webhook the gateway sends to your server, which your code verifies with the provider's signature before marking the order paid.

Two details separate a careful build from a fragile one. The same webhook can arrive twice, so handling it a second time must not ship a second order. And a webhook can arrive before the customer is even back on your site, so the order has to be ready to receive it.

What about refunds, chargebacks and currency?

Refunds are where a gateway shows its real character. Find out where the money goes back to (the customer's card, a wallet, something else), how many days it takes, and whether your team can issue a refund without opening a ticket with the provider. Your customer will judge you on that wait, not the provider.

A chargeback is a different thing. It's a dispute the customer opens with their own bank, and the money can be pulled back while the case is reviewed. Keep proof for every order, such as the delivery confirmation, the customer's messages and the order record, because you'll need them to answer within the provider's deadline.

Currency is the quiet one. If you price in Saudi riyals but settle in Egyptian pounds, or the reverse, the exchange rate and the party who applies it change your real margin. Ask for the answer in writing before you sign.

Mistakes we'd steer you away from

Choosing on fees alone. A cheaper rate with a slow settlement or poor support can cost you more in cash flow and lost orders than the percentage you saved.

Launching without testing the ugly paths. Test a declined card, an abandoned payment, a refund and a duplicated webhook. The happy path always works in demos.

Hardcoding one gateway into the whole store. When the provider changes its terms, you'll want to be able to change providers without rewriting your orders.

Never reconciling. Once a week, compare the gateway's report with your own order list. Small differences are easy to fix when they're a week old and miserable when they're a year old.

Frequently asked questions

Do I need more than one payment gateway?

If you sell in one country to one type of customer, one good gateway can be enough to start. If you sell in Egypt and the Gulf, or you depend on specific methods like Mada and wallets, plan for more than one, or at least a design that lets you add one later.

Can I switch gateways later without rebuilding my store?

Yes, if the store was built with the gateway isolated from the order logic. If payment code is scattered through the checkout, switching becomes a rebuild. Ask your developer how the gateway is separated before the project starts.

What is a webhook, and why does it matter?

A webhook is a message the gateway sends to your server when a payment changes status, such as paid, failed or refunded. It's the trustworthy way to confirm payments, because it doesn't depend on the customer's browser behaving.

If you're planning a store and want the payment side designed properly from the start, look at our e-commerce development service or tell us what you sell and where, and we'll tell you honestly what you need.