Payment Gateway Egypt

Many Egyptian customers already hold a mobile wallet that is opened against their mobile number. For an online merchant, that number serves as the routing key: the customer gives it at checkout, and the payment request goes to the wallet linked to it.

Payment Gateway Africa is a payment gateway in Africa that covers seven markets through one merchant relationship. In Egypt, the supported method is mobile wallet payment by phone number, settled in EGP. This page covers what the method looks like for your customers, which operations you can run, how to integrate, and what onboarding requires.

If you are comparing providers for a launch in Egypt, the sections below set out what we offer so you can check it against your own requirements.

Currency: Egyptian pound (EGP). Pay-ins through Payment Gateway Africa in Egypt are made in local currency.

Local method supported by Payment Gateway Africa: mobile wallet payments made by phone number. The customer's wallet is tied to their mobile number, so the number they enter at checkout identifies the wallet to be charged.

Typical way a payment is confirmed: the customer approves the request inside their own wallet, following the steps their wallet provider sets. Your checkout does not collect wallet credentials.

Regulator: the Central Bank of Egypt (CBE) is the country's monetary and banking authority. Market context like this does not confirm that any specific merchant can be onboarded. Availability for your project depends on our onboarding review.

We do not publish market-size or adoption figures on this page. If you need numbers for a business case, take them from official sources, and look at the figures for the customer segment you actually serve.

Step 1. Order created: your platform builds the order with an amount in EGP and starts a payment session, either by sending the customer to the Payment Gateway Africa hosted payment page or by calling the API from your backend.

Step 2. Phone number entered: the customer selects the phone-number wallet option and enters the mobile number registered to their wallet.

Step 3. Request sent to the wallet: the payment request goes to the wallet linked to that number, where the customer sees what they are being asked to pay.

Step 4. Customer approves: the customer confirms the payment in their wallet using the method their provider requires. If they decline or do not respond, the payment does not complete.

Step 5. Status delivered to you: Payment Gateway Africa sends the result to your system through postbacks and webhooks. These notifications go to you, the merchant. We do not run a separate notification service for buyers, so your order confirmation emails or screens remain under your control.

Step 6. Order fulfilled: once your backend records a successful status, you release the goods or service. You can reconcile the transaction later in reporting.

Pay-ins, payouts and settlement are three separate flows on Payment Gateway Africa. Each one moves money in a different direction, so we describe them separately.

Pay-ins: you collect EGP from customers who pay with their phone-number wallet, either on the hosted page or through your API-driven checkout.

Payouts: you send funds to customers, sellers or partners, where available for the method and project. Whether payouts are enabled for your Egyptian setup is confirmed during onboarding, so you should not plan around them until that is confirmed.

Settlement: this is how the balance you have collected is transferred to you as the merchant. Payment Gateway Africa dispatches merchant settlements same-day (T+0). That date marks when we release the funds. It does not mean the money shows up in your account instantly, because bank posting times vary and the receiving side may need its own processing time.

Reporting: transaction records let your finance team match each payment status to an order and reconcile settled amounts.

Adding methods later: existing merchants can activate any additional supported payment method without a connection surcharge, and how many methods you enable has no impact on your connection price. For existing clients, switching on a method we already support can usually be done within one day. Find more details on our pricing page.

Payment Gateway Africa offers two ways to connect. Both use the same gateway, so you can pick based on how much of the checkout you want to build yourself.

Hosted Payment Page: you redirect the customer to a payment page that Payment Gateway Africa hosts. The customer enters their phone number there and completes the wallet flow. This is the faster option for teams that do not want to build payment screens.

H2H (API): your backend talks directly to the gateway, and you keep the checkout experience inside your own interface. H2H means a direct host-to-host connection. It is not a white-label product. Postbacks deliver the final status to your backend. If your product is a mobile app, the payment step opens in a browser page rather than a native in-app SDK.

With either option, postbacks and webhooks send transaction statuses to your backend. Your system should treat that status as the trigger to fulfil an order, rather than relying on the customer returning to your site.

Request formats, status handling and connection steps are covered in the integration guide. Full API reference and credentials are provided after merchant onboarding.

Before we activate any project, we run a know-your-business (KYB) review. Expect to share company registration details, information about the people who own and control the business, a description of what you sell, your website, and the markets and methods you plan to use.

Egypt has its own financial regulation, and wallet providers set their own rules on how they can be used. During onboarding we check whether your business model fits the EGP wallet route. If something needs clarification, we raise it before go-live rather than after.

Your own legal obligations in Egypt, such as consumer, tax or data rules, depend on your structure and your activity. You should get local legal advice on them. Our general approach to verification and monitoring is explained on the AML and KYC page.

The right gateway depends on your customers, your volume and your operations, not on rankings. These questions help you compare providers on facts.

Method fit: does the provider support the way your customers already pay? In Payment Gateway Africa's case, that is wallet payment by phone number in EGP.

Flow separation: are pay-ins, payouts and settlement treated as distinct flows, with payouts confirmed for your project rather than assumed?

Settlement timing: when do you receive funds? Payment Gateway Africa offers same-day dispatch (T+0) for merchant settlements.

Status handling: will your backend receive reliable postbacks and webhooks, so that orders update without manual checks?

Growth path: if you later expand to other African markets, can you add supported methods without paying an extra connection fee?

Pricing clarity: do you get a quote based on your real volumes and markets? Payment Gateway Africa does not publish fixed rates. You can request a quote for Egypt based on your expected profile.

Many merchants that start in Egypt later add other markets. In North Africa, Payment Gateway Africa also covers Tunisia, where customers can pay with D17 and Flouci in TND. See the payment gateway for Tunisia for details.

In East Africa, we support CBE Birr, M-Pesa and local transfers in Ethiopia, paid in ETB. The Ethiopia payments page explains that route.

To compare all wallets and the countries they cover, see our phone-number wallet payments and other mobile money methods overview. For the full list of seven markets, browse all countries we cover.

Getting started takes four steps: submit your application, complete the KYB review, test in a dedicated test project with separate keys, and go live. Tell us your expected EGP volumes, whether you need payouts, and whether you prefer the hosted page or the API. We will then confirm what we can enable for your project.

Start your Egypt onboarding or review how pricing works before you apply.