Integrating a payment gateway with your system means that your system creates the payment request with the gateway, receives a verified notification of the result of every transaction, and then matches what reaches your bank account against orders and invoices. In Egypt, gateways such as Paymob and Fawry cover cards, mobile wallets and cash payment by reference number, and InstaPay can be accepted through some gateways by QR code or a request to pay. The real decision is not the gateway's name. It is the payment methods your customers use, the fees, the settlement period, how refunds work and how well the integration fits your accounting.
This guide is for companies and stores that sell products or services. We explain each payment method and what your system needs for it, how to read a fee structure, how the integration works technically from order to notification, and then settlement, refunds and reconciliation. If you sell training courses specifically, you will find the automatic enrolment details in our article on collecting course payments in Egypt.
Which payment methods does your company need in Egypt?
Each payment method follows a different path inside your system, and the most important difference is when you know the money has actually arrived:
| Payment method | How the customer pays | What your system needs |
|---|---|---|
| Bank cards | Enters card details on the gateway's secure payment page | A success or decline result within seconds, and a clear path to refund to the same card |
| Mobile wallets | Confirms the payment on their phone with their wallet number | Waiting for the customer's confirmation, then a notification of the result |
| Cash by reference number | Gets a reference number and pays at a Fawry outlet | An order "awaiting payment" for hours or days, an expiry for the number, and a notification when it is paid |
| InstaPay | Scans a QR code or approves a request to pay in their banking app | A notification from the gateway when the request is approved, declined or expires |
| Instalments and pay later | Chooses an instalment provider on the payment page | Available through some gateways depending on your account setup, with its own settlement terms |
Payment by reference number deserves special attention. According to the FawryPay developer documentation, you can set an expiry for the reference number, after which the customer can no longer pay with it, and set a URL where your system is notified whenever the order's status changes. So your system has to know how to hold stock for an unpaid order, and when to release it.
How do you choose the right payment gateway for your company?
Compare gateways on these criteria before price, because the cheapest gateway can cost you more if it does not support the payment method your customers prefer:
- The payment methods actually enabled for your account. Some methods are enabled depending on your type of business and account setup, so ask for a written list of what will be activated for you.
- The full fee structure. The percentage and fixed amount per transaction, plus any setup, subscription or refund fees.
- Settlement period. When the money reaches your bank account, and whether faster settlement is available and at what fee.
- Refunds and disputes. Whether partial refunds are possible from the dashboard or through the API, and how cardholder disputes are handled.
- Documentation quality and a test environment. Clear documentation of the APIs and notifications, and a test account where you can try every scenario before launch.
- Ready plugins for your platform. If your store runs on a ready-made platform, make sure there is an official plugin the gateway supports and keeps updated.
You do not have to settle for a single gateway. Many companies use a main gateway for cards and wallets and add cash by reference number or InstaPay to match their customers' habits. What matters is that your system handles every gateway the same way when it records orders and reconciles them.
What fees do you pay, and how do you read the structure?
Fees differ between gateways and between accounts, so always rely on the official page and your contract. For example, as things stand (November 2026), Paymob's pricing page shows a standard rate of 2.75% plus EGP 3 per transaction with no monthly or subscription fees, weekly settlement to your bank account, and a note that rates are adjusted as your business grows. At that rate, an order worth EGP 1000 carries about EGP 30.5 in fees, and about EGP 969.5 reaches you.
Do not stop at the percentage. Ask about these items and get them in writing:
- Refund fees. Is the original transaction fee returned on a refund, or is another fee deducted?
- Fees per payment method. Does the percentage differ between cards, wallets, cash and InstaPay?
- Minimums and fixed charges. Is there a monthly minimum, a setup fee or an annual fee?
- Faster settlement. If it is available, at what extra fee?
Then calculate the fees on your real average order value, not on a generic example, because the fixed amount per transaction weighs far more on small orders than on large ones.
Is a ready-made plugin enough, or do you need a custom integration?
If your store runs on a ready-made platform and sells only by card and wallet, the gateway's official plugin is usually enough, as long as you test it well and keep up with its updates. You can review the differences between the platforms themselves in our comparison of Shopify, WooCommerce and a custom-built store.
A custom integration becomes necessary in specific cases: when every payment must reach your accounting system or ERP automatically, when you sell through more than one channel, such as a store, an app and branches, and want a single record of payments, when you need special logic such as deposits, staged payments or splitting an amount between several vendors, or when you want the e-invoice or e-receipt issued automatically after every successful transaction.
How does a payment gateway integration work technically, from order to notification?
Whatever the gateway, a sound integration goes through these steps:
- Create the order in your system first. With a unique number, a fixed amount and an "awaiting payment" status, before contacting the gateway.
- Request the payment from the gateway. Your server sends the order number and amount, and gets back a payment page link, a reference number or a QR code.
- Let the customer pay with the gateway. Card details are entered on the gateway's secure page, not in your system.
- Rely on the server notification, not the return page. Paymob's developer documentation separates a notification that reaches your server to update orders and records from a redirect that brings the customer back to your site to show the result. The first is the source of truth.
- Verify the notification's signature. Every gateway offers a way to confirm that a notification really came from it, such as an HMAC signature, so do not update any order before verifying it.
- Update the order only once. The same notification can arrive more than once, and stock must not be deducted twice or an invoice issued twice.
- Issue the invoice or receipt after payment is confirmed. Then record the gateway's transaction number next to the order number, ready for reconciliation.
How do you handle settlement, refunds and reconciliation?
Money does not reach your account order by order. It arrives in grouped settlement batches after fees and refunds are deducted. So your accounts team needs to link three numbers for every transaction: the order number in your system, the transaction number at the gateway, and the settlement batch number on the bank statement.
| Item | Where it comes from | What you match |
|---|---|---|
| Paid sales | Gateway notifications recorded in your system | That every paid order has exactly one successful transaction at the gateway |
| Fees | The gateway's settlement report | That the fees deducted match the percentage and fixed amount in your contract |
| Refunds | The refund log in your system and at the gateway | That every return has one refund for the correct amount |
| Net settlement | Your bank statement | That the amount transferred equals sales minus fees and refunds |
The more automated this matching is, the fewer differences you discover at month end. Our article on invoices, reconciliation and e-invoicing explains how this matching is built and followed day to day.
What are the common mistakes when integrating a payment gateway?
- Confirming the order from the return page. The customer may close the browser before returning, or reach the page without the payment completing.
- Ignoring pending states. An unpaid reference number and an expired InstaPay request both need handling that releases the stock and informs the customer.
- Gateway keys inside the code. Production keys belong in secure server settings, fully separate from test environment keys.
- Recording the net instead of the gross. Record the full sale amount and the fees as a separate expense, or reconciliation and tax filings become harder.
- Launching without testing the hard cases. Try declines, partial refunds, duplicate notifications and lost connections before your first real customer.
How does HBS approach payment gateway integration?
At HBS we start by mapping your systems and the data that has to move between them: the store or app, the gateway, accounting and e-invoicing. We then design the integration before writing code, test it in a preview environment against every scenario, and document what we deliver. Security is built into the design from the start: API keys stored securely, encrypted connections, input validation, rate limiting and an audit log for every integration.
One example from our work is Hala Nur, a multivendor marketplace app we built for a charitable organisation that helps artisans and small vendors sell their handmade products. The app includes payments integrated with payment gateways, order tracking, a dashboard for each vendor showing their sales and earnings reports, and an admin panel that tracks sales across the platform. In multivendor marketplaces, reconciliation matters even more, because every payment must be attributed to its vendor and their earnings calculated from it accurately.
Legal details and fees in this article reflect the situation in November 2026 and may change; check the official source before you decide.
If you want to connect a payment gateway to your store or system and be sure every pound is recorded correctly, from the first order until it reaches your account, tell us which payment methods your customers use and which systems you run. We will sit down with you in a free discovery session and tell you honestly what fits, and you can learn more about HBS payment gateway and API integration services.





