Payment gateways

Every payment gateway in Egypt, connected and run.

Fawry, Paymob, Kashier, Geidea, PayTabs, Visa, Mastercard, Apple Pay, Google Pay, Meeza and the banks: we integrate, install, design and run the payment step, on your own merchant account.

Get a quote

Five things we do for your payments

A gateway is only useful once it is connected, shown well, and kept working. That is the whole job, and it is ours from the first key to the hundredth day.

  1. 01

    Integrate

    We connect the gateway’s API to your site or app, with webhooks that confirm every payment on your side.

  2. 02

    Install

    We set up the ready-made plugin on WordPress, WooCommerce or Magento, with keys, methods and callbacks in place.

  3. 03

    Design

    We shape the payment step to your brand: which methods appear, in which order, and what the customer reads at each screen.

  4. 04

    Run

    We keep test and live keys, refunds and the reconciliation of what the gateway paid you in working order.

  5. 05

    Monitor

    We watch every payment: the failed ones, the abandoned ones, a callback that never arrived, a gateway that is down.

The gateways and methods we work with

Each line says only how that provider lets a merchant connect. We do this on your merchant account, whichever of them you already hold or choose.

Cards and wallets

The methods your customers already carry. Each one is switched on through the gateway you use, so one integration covers several.

  • Visa

    Cards on every gateway below, with the 3-D Secure check run by the gateway.

  • Mastercard

    Debit, credit and prepaid cards, listed at checkout beside Visa.

  • Apple Pay

    One-touch payment on Apple devices, switched on through your gateway where it offers it.

  • Google Pay

    One-touch payment with a card saved in the customer’s Google account, through your gateway.

  • PayPal

    For customers paying from abroad: PayPal’s own checkout, its REST API or a plugin.

  • Vodafone Cash · Orange · e&

    Telecom wallets that customers pay from with their phone number, through a gateway that supports them.

Egyptian gateways

Local providers with an Egyptian merchant account, each with its own way of connecting.

  • Fawry

    A hosted checkout link, a checkout button, a server API and plugins; customers can also pay at a Fawry outlet by reference number.

  • Paymob

    The hosted Unified Checkout page, or the Pixel card form inside your own page; a WooCommerce plugin; webhooks checked by signature.

  • Kashier

    Hosted checkout, payment links and invoices, plugins for the common store platforms, and free test credentials to build against.

  • Geidea

    Redirect, pop-up or embedded checkout in your branding, with plugins for WooCommerce, Magento 2, PrestaShop and more.

  • PayTabs

    A hosted payment page or a managed form, plugins and SDKs, payment links and repeat billing.

  • Fawaterak

    Payment pages, payment links and invoices sent by WhatsApp or SMS, with plugins for the common store platforms.

Bank schemes, banks and instalments

The national rails, the banks’ own gateways and the pay-later plans.

  • Meeza

    Egypt’s national card scheme, accepted through the gateways that list it.

  • InstaPay

    Instant bank payment from the customer’s phone, connected where your gateway or bank offers merchant acceptance.

  • National Bank of Egypt

    Online card payments through the bank’s own gateway: you contract with the bank, we connect, style and test it.

  • CIB

    The bank’s own online gateway for websites and mobile apps; we connect it to your checkout and test it end to end.

  • Banque Misr

    The bank’s own online payment gateway: you apply through the bank, and we connect and test it once you hold the credentials.

  • valU

    Buy now, pay later plans, offered through a gateway that lists valU.

Also the pay-later and instalment providers such as Souhoola, Aman, Contact and Halan, wherever your gateway lists them.

How a payment project runs

Five stops, in this order, and no real customer is charged until the fourth is finished.

  1. Your merchant account

    You open it with the provider you choose. It is your company’s account and the provider decides on approval; we help you choose and prepare.

  2. Sandbox

    We build against the provider’s test mode with test keys, so no real card is ever charged while we work.

  3. Checkout design

    Hosted page or embedded fields, the methods and their order, the wording, and the success and failure screens.

  4. Live test

    Real keys, one real small payment and its refund, watched from the button to your bank before the public sees it.

  5. Monitoring

    After launch we keep watching payments, callbacks and the gateway’s status, and act on what we see.

What you receive

Not a plugin left in a folder: a working payment step, and the means to trust it.

  • The gateway connectedConnected on your own merchant account, in test mode and in live mode.
  • A checkout in your brandHosted or embedded, with the methods and the wording chosen for your customers.
  • Your platform coveredThe gateway’s plugin where it publishes one, and its API for Laravel, custom PHP and mobile apps.
  • Webhooks you can trustAn order is marked paid only when the gateway has confirmed it, checked by signature.
  • A refund flowWho may refund, from where, and how the order and the customer are told.
  • ReconciliationYour orders set against what the gateway settled, with every difference listed.
  • AlertsRaised when payments start failing, a callback goes missing or the gateway is down.

Option one

Hosted page

The customer is sent to the gateway’s own payment page and comes back to your site when it is done.

The quickest to launch, and the gateway carries most of the card-security work.

Option two, where the gateway offers it

Embedded fields

The customer stays on your page and types the card into fields the gateway draws inside it.

It feels like part of your site, and card details still go straight to the gateway.

  • WordPress
  • WooCommerce
  • Magento
  • Laravel
  • PrestaShop
  • PHP
  • Mobile apps

Why an Egyptian business needs Egyptian rails

Visa and Mastercard are the start, not the whole checkout. The rest is what the customer in front of you actually carries.

  1. 01

    Wallets and Meeza

    Some of your customers pay with a telecom wallet or a Meeza card, not with Visa or Mastercard. A checkout without them turns those customers away.

  2. 02

    Cash and pay-later

    A reference paid at an outlet, or an instalment plan, reaches the customer who will not put a full amount on a card online.

  3. 03

    Your own bank account

    The provider pays out to your company’s own bank account. The money never passes through us.

  4. 04

    Someone who reads the errors

    A payment that fails at night needs a person who understands the provider’s messages and the local banks. That is the monitoring we do.

What stays yours

We work inside your accounts. The list below is the line between what is yours and what we do.

The merchant account and the contract
Your company, with the provider.
The keys and the provider’s dashboard
Your company. We use them for the work and hand them back.
The money
Paid by the provider to your bank account, never through us.
Card numbers
Typed into the gateway’s own page or fields. We never keep them.
The connection, the checkout and the watching
Ours, from the first test key onward.

EGPHP is an independent developer. We are not an authorised partner, agent or reseller of any provider shown on this page. Their names and logos belong to their owners and appear only to say which services we connect.

Questions we are asked first

Which gateway should we choose?

It depends on three things: the methods your customers actually use, what your site runs on, and how you want the money to reach you. We compare the providers on those points, tell you what we would pick and why, and can connect more than one so a second gateway is there if the first is down.

Do you provide the gateway, or handle our money?

No. The merchant account and the contract are your company’s, with the provider you choose. We connect it, install it, design the checkout and watch it. The money goes from the provider to your bank account, never through us.

Can we use Stripe in Egypt?

Stripe’s own list of supported countries does not include Egypt, so an Egyptian business normally uses a local gateway or a bank. If your company also has an entity in a country Stripe supports, we can connect Stripe for that entity.

Are Apple Pay and Google Pay available?

Several Egyptian gateways offer both, and we switch them on through the gateway you use. Whether a customer sees them depends on their device and on their bank, which is why the checkout always keeps a card option beside them.

Do card numbers touch our server?

Not in a hosted page, and not in the embedded fields a gateway draws: the card is typed straight into the gateway’s own page or fields. We do not build checkouts that keep card numbers.

What if the gateway we want is not listed here?

We work from the provider’s public documentation. If it has an API, a hosted payment page or a plugin for your platform, we can connect it. Ask us before you sign, and we will tell you what its integration involves.

Tell us how your customers pay today

Which gateway you hold or want, what your site runs on, and which methods your customers ask for. We answer with a plan after one conversation.

Get a quote
MickeyAnswers in seconds