Payment gateway integration in Egypt: cards, Meeza, Fawry, wallets, InstaPay and cash on delivery
By Dr. Hani Elimam Manager & CEO, SmartTech Studio
In Egypt, a store that only takes cards turns customers away. Shoppers also pay with the national Meeza card, a mobile wallet, a Fawry reference code paid at a shop or in an app, an InstaPay transfer, or cash to the courier. The checkout has to offer the methods your customers actually use, and the back office has to know, reliably, which orders are paid.
That second part is where most stores go wrong. A payment that shows as successful in the browser but never reaches the order system, a Fawry order that stays "pending" forever, a cash-on-delivery order that is shipped twice: these are integration problems, not design problems.
This guide explains the payment methods, the kinds of provider, how a safe integration works, where the Egyptian Tax Authority’s e-receipt fits, and what the Personal Data Protection Law means for card data. It is written for owners and operations teams. It names no fees, because they are negotiated per merchant and change; ask each provider for a written quote.
The payment methods Egyptian customers expect
Cards. Visa and Mastercard debit and credit cards, accepted online through a payment provider. Card payments are confirmed in seconds, which makes them the simplest method to automate.
Meeza. Egypt’s national payment scheme, developed by the Egyptian Banks Company under the supervision of the Central Bank of Egypt and launched in 2019. Meeza cards are issued by Egyptian banks, prepaid or linked to an account, and work for local purchases and local e-commerce, not abroad. If some of your customers pay with Meeza, check that your provider accepts it; not every one switches it on by default.
Mobile wallets. Wallets run by banks with the mobile operators. The customer approves the payment on the phone. Many gateways offer wallets as one option alongside cards.
Fawry reference codes. The customer chooses Fawry, receives a reference number, and pays it later at a Fawry outlet or in an app. The order is not paid when it is placed. It stays pending until Fawry confirms payment, and an unpaid reference expires.
InstaPay. The Central Bank of Egypt’s instant payment network, which moves money between bank accounts and cards in seconds. Customers like it, but how a store can accept it depends on your bank and provider. Some stores simply show their InstaPay address and confirm transfers by hand, which works at low volume but needs a reconciliation step.
Cash on delivery. Still part of e-commerce in Egypt, especially for first orders and outside the big cities. It costs you in failed deliveries and cash collection, so most stores confirm the order by phone or WhatsApp before shipping.
Instalments. Consumer-finance and buy-now-pay-later providers let customers split larger purchases. They are integrated like a gateway option, and the provider takes the credit risk.
Which kind of provider do you need?
Payment aggregators and gateways. One contract and one integration give you several methods: cards, Meeza, wallets, often Fawry-style cash payments and instalments. Paymob is the best-known example in Egypt; banks and other providers offer similar services. For most small and medium stores this is the sensible start.
Fawry directly. Fawry also contracts with merchants directly, for its reference codes and its own card acceptance. Stores whose customers lean heavily on cash payments sometimes add it next to a gateway.
Your bank. Larger merchants can get card acceptance directly from an acquiring bank. It can mean better terms at volume, but each extra method becomes a separate integration.
Whatever you choose, check the licence. In 2025 the Central Bank of Egypt issued rules requiring payment system operators and payment service providers to be licensed, with a transition period for existing firms and a registration duty for foreign providers serving residents of Egypt. Ask any provider which licence it holds, and keep the answer on file.
The provider decides your integration work. Before signing, ask for the developer documentation, a sandbox account, the list of methods it will actually switch on for your business, how it notifies you of payments, how refunds work, and how and when it settles money to your account.
How a safe integration works
1. Prefer a hosted checkout. The provider’s payment page, or its embedded frame, collects the card details, so card numbers never touch your server. This removes most of the security burden and is the right default for almost every store.
2. Create the payment from your server. When the customer checks out, your server creates the order, then asks the provider for a payment session with the exact amount in Egyptian pounds and your own order number. The browser never sets the amount.
3. Trust the server callback, not the redirect. After paying, the customer is sent back to your site, but that redirect can be lost, closed or faked. The real confirmation is the callback (webhook) the provider sends to your server. Gateways sign these messages, commonly with an HMAC; verify the signature before you mark anything paid.
4. Make it idempotent. Providers retry callbacks, so the same notification can arrive twice. Record each transaction ID once, and make "mark as paid" safe to repeat. This is what stops double shipments and double receipts.
5. Handle pending properly. Fawry references, some wallet payments and manual InstaPay transfers are not instant. Give these orders a clear pending state, reserve the stock for a set time, and release it when the reference expires. A scheduled job that asks the provider for the status of old pending orders catches any callback that never arrived.
6. Build refunds and partial refunds into the back office, through the provider’s API, so staff never refund by hand outside the system.
7. Reconcile every day. Match the provider’s settlement report against your orders: what was paid, what was refunded, what was deducted in fees, and what reached your bank. Differences found the next day are easy to fix; differences found at year end are not.
Cash on delivery without the losses
Cash on delivery needs its own flow, not a payment method that is simply switched on. Confirm each order before it ships, by phone, WhatsApp or an automatic message the customer answers. Limit it where returns are high, for example above a certain order value or for customers with earlier refusals.
Track the cash. The courier collects the money and pays it to you later, minus its charges. Your system should show, per order, whether it was delivered, whether the cash was collected, and whether the courier has settled it. Without that, cash on delivery becomes the place where money quietly disappears.
Offer a nudge to prepay. Some stores show the card and wallet options first, or offer free delivery for prepaid orders. Each prepaid order is one less failed delivery.
Where the ETA e-receipt comes in
If your business has been brought into the Egyptian Tax Authority’s e-receipt system, each sale to a consumer, online sales included, needs an e-receipt submitted from the system that made the sale. Business customers get an e-invoice instead. Our guide to ETA e-invoice and e-receipt integration explains how to check whether you are obligated and what the integration involves.
The practical point for payments is timing and matching. Decide with your accountant at which event the receipt is issued, for example when a card payment is confirmed or when a cash-on-delivery order is delivered and paid. A refund then needs a matching return document. If the store, the payment status and the receipts live in one system, this happens automatically; if they live in three, someone does it by hand.
VAT is 14% in Egypt, and the tax on each receipt must match what the customer paid. Prices shown at checkout should therefore come from the same item data that feeds the receipts.
Card data and the Personal Data Protection Law
Egypt’s Personal Data Protection Law, Law No. 151 of 2020, with its executive regulations issued in 2025, applies to the customer data your store collects. The law treats financial data as sensitive data, and processing sensitive data needs prior permission from the Personal Data Protection Center. Most stores avoid holding financial data at all.
That is the second reason for a hosted checkout: the card number goes to the licensed provider, and your system keeps only what it needs, such as the order, the amount, the provider’s transaction ID and, for repeat payments, the provider’s token. Never store full card numbers or security codes, never write them to logs, and never ask customers to send card details by WhatsApp or email.
For the rest of your customer data, the same discipline applies: collect only what the order needs, say in a clear privacy notice what you do with it, protect access to the back office, and decide how long you keep it. This is orientation, not legal advice; a lawyer should confirm what your business needs from the Center.
A checklist before you go live
Methods: the methods your customers use are switched on in the live account, not just in the sandbox, Meeza included.
Confirmation: orders are marked paid only by a verified server callback, and a repeated callback changes nothing.
Pending: Fawry and transfer orders have a pending state, a stock hold and an expiry, and a scheduled status check runs.
Refunds: full and partial refunds run from the back office through the provider, and create the matching tax document.
Receipts: if you are in the e-receipt system, every paid consumer order produces an accepted e-receipt.
Money: a daily reconciliation compares orders, provider settlements and bank deposits, cash on delivery included.
Data: no card numbers in your database, logs or messages; a privacy notice is published.
Tests: a real low-value payment by every method, a refund of each, and a callback replayed on purpose, before launch day.
How SmartTech can help
SmartTech Studio is an Abu Dhabi software house that serves businesses in Egypt remotely; we have no office in Egypt. We build bilingual online stores and websites with the payment methods above, and POS, stock and ERP systems that issue ETA e-receipts from the same data. We work with the provider you choose and integrate it against its own documentation.
Every Egyptian project is quoted in writing for its scope. More on how we work with Egyptian clients is on our Egypt page.
FAQ
Do I need my own Central Bank licence to accept payments on my store?
Generally no. The licence duty falls on the payment providers. A store selling its own goods contracts with a licensed provider, which is why you should check and record the provider’s licence. If your business would hold or move other people’s money, for example as a marketplace paying sellers, take legal advice first.
Can my online store accept InstaPay?
It depends on your bank and payment provider, so ask them what they support today. Many small stores show their InstaPay address at checkout and confirm each transfer by hand. That works at low volume, but every transfer has to be matched to an order, so keep those orders pending until the money is confirmed.
How does a Fawry payment work for the store?
At checkout your system asks Fawry for a reference number and shows it to the customer, who pays later at an outlet or in an app. The order stays pending. When the customer pays, Fawry notifies your server and the order becomes paid; if the reference expires unpaid, your system should cancel the order and release the stock.
Is cash on delivery still worth offering?
For most Egyptian stores, yes, because many customers will not place a first order any other way. Keep it under control: confirm orders before shipping, limit it where refusals are high, track every courier settlement per order, and give customers a reason to prepay.
Do online sales need an ETA e-receipt?
If your business has been brought into the e-receipt system, yes: sales to consumers need an e-receipt whether they happen in a shop or online, and business customers get an e-invoice. Check your status first; our ETA integration guide explains how.
Should my website store customers’ card details?
No. Use the provider’s hosted checkout so card numbers go straight to it, and keep only its transaction ID and, for repeat payments, its token. Egypt’s data protection law treats financial data as sensitive, and holding it adds obligations most stores do not need.