How to Pay Contractors in Egypt: Bank Routes, IPN and FX

Choose an Egypt payout route before promising a delivery time#

To pay an independent contractor in Egypt, decide the invoice currency, funding origin and actual receiving account first. A foreign-funded EGP bank payment and an Egyptian company’s domestic EGP transfer have different funding and conversion steps. The contractor’s preference for InstaPay does not settle those questions or give a platform access to a business payout API.

InstaPay is an application; the Instant Payment Network (IPN) is the underlying network; Meeza is Egypt’s national payment scheme, including cards. They are not three interchangeable payout providers. This guide separates their roles, gives concrete bank-payment setup and shows how to reconcile a quoted EGP obligation without issuing a second payment after a timeout.

Step 1: Confirm the obligation and receiving details#

Record the contracting entity, contractor identity, service period, invoice, approval and amount/currency owed. Establish that the relationship is genuinely independent contracting under the applicable rules. A domestic bank payment does not make an employee a contractor. Keep any employee payroll obligations in the correct payroll process rather than routing them as freelance invoices.

Ask the contractor for bank-issued receiving instructions, the exact account-holder name and the account’s supported currency. For an EGP bank payout through the Wise route below, the required destination is a 29-character Egyptian IBAN and full recipient name. Format validation is not ownership validation: confirm the account belongs to the intended person or business through your established verification process.

If an invoice is denominated in USD but the parties agree to receive EGP, document the conversion basis, date, fee allocation and whether the EGP amount settles the full invoice. If the contract requires USD into a USD account, choose a bank route that actually delivers USD. Sending EGP at an assumed rate can underpay the invoice even when the local transfer succeeds.

Retain the service agreement, invoice, approval and purpose narrative as your internal evidence. The sending provider and receiving bank can impose additional onboarding, source-of-funds or payment-purpose requirements. These are not all a single universal Egyptian document list. Use the real service description; do not describe a contractor’s service payment as a family remittance to fit a consumer-only product.

Step 2: Select a supported funding and delivery path#

Wise’s EGP transfer guide supports EGP delivery to individual and business bank accounts in Egypt, but excludes charities and trust beneficiaries. It lists a 5 million EGP per-transfer limit. This gives a concrete route to assess for an eligible foreign business; it does not guarantee that every sender country, platform model or service is accepted.

For that route, use your verified eligible business profile, select the funding currency and EGP destination, enter the recipient’s full account-holder name and IBAN, obtain the actual quote and fund by an offered method. The guide says conversion can take up to two working days and bank arrival is usually the same working day after receipt and conversion. Use the transfer’s own estimate rather than promising instant cross-border delivery.

CBE’s December 5, 2024 announcement confirms that approved banks can credit inbound remittances through IPN. The pilot used licensed bank correspondents and foreign exchange companies abroad. It is therefore inaccurate to say IPN can never participate in a cross-border payment. The approval does not show that your particular overseas business can initiate contractor payments through the consumer app or a public API.

Ask a remittance partner to confirm commercial-service eligibility, funding jurisdiction, local bank partner, conversion rate, recipient instrument, limits and returned-payment handling for your specific business. A product marketed to Egyptian expatriates may have a different permitted purpose or customer population. If it does not accept the actual contractor payment, use an eligible bank/business provider instead of changing the declared purpose.

For a domestic company account, Banque Misr’s corporate transfer service lists bank, card, wallet and international transfer options and subscription through a branch. It is an example of a business banking channel, not proof of an unrestricted automated payout API. Obtain the bank’s actual corporate permissions, workflow and file/API arrangements before designing bulk disbursements.

Step 3: Treat InstaPay limits and Meeza destinations correctly#

CBE describes IPN as the national instant-payment network, including transfers to bank accounts, Meeza cards and mobile wallets. Its National Payments Council page identifies Meeza as a national scheme and card system. A Meeza card is a possible receiving instrument in a supported route, not an FX conversion service.

The InstaPay FAQ lists EGP 70,000 per transaction, EGP 120,000 daily debit per bank and EGP 400,000 monthly debit per bank. Those app limits are not the Wise bank-payout limit or an incoming-account limit. Check the relevant channel and receiving instrument separately, including remaining capacity already used by the sender.

An EGP 80,000 obligation exceeds the app’s single-transfer limit even if the sender has unused daily capacity. Prefer the approved corporate route for a business batch. If an authorized route genuinely requires installments, keep them linked to one invoice and assess aggregate limits; do not split transfers to evade controls or present each installment as full settlement.

The app’s FAQ permits use while abroad with the Egyptian SIM matching bank records present in the device. That means a registered user can access Egyptian accounts from another location; it does not mean the app imports a foreign bank balance or converts foreign currency. Onboarding credentials and PINs belong in the official app. A platform must not ask contractors to disclose card PINs, OTPs or IPN PINs to its own staff or forms.

CIB’s September 1, 2026 digital-channel tariff lists InstaPay-app transfers between individuals at 0.10%, minimum EGP 0.50 and maximum EGP 20. Thus an EGP 10,000 transfer under that tariff costs EGP 10, while EGP 50,000 reaches the EGP 20 cap. This personal/app tariff must not be substituted for a corporate banking or international provider quote; the same sheet distinguishes channel pricing.

Step 4: Approve the quote and documentation before submission#

Freeze the invoice allocation, approved beneficiary version, funding currency, destination amount, exchange rate, quote expiry, fees and fee bearer in the payout record. Re-quote and re-approve when a quote expires or the amount or destination changes. The rate’s direction matters: EGP per USD multiplied by dollars gives EGP; reversing it gives a different result.

Use the regulated bank or authorized provider for the actual conversion and payment. Ask where conversion takes place, which entity handles it and what receiving-bank restrictions apply to that account and service purpose. Neither an app’s speed nor a market report establishes a universal FX allowance, tax exemption or required purpose code.

Wise’s business source-of-funds guidance says it may request evidence at onboarding or for unusual/large activity. For business revenue it lists bank statements, service agreements and audited statements, and may request invoices. These are provider evidence examples, not an Egyptian threshold schedule or a guarantee that only those documents will be required.

For illustration, suppose the contractor is owed exactly EGP 50,000, an accepted quote converts at EGP 50 per USD and the platform pays a separate hypothetical $10 provider fee. Principal funding is $1,000, total funding $1,010 and the contractor receives EGP 50,000 if delivered as quoted. These are invented arithmetic inputs, not a current exchange rate or Wise price. The local InstaPay tariff above is not added automatically to this bank-delivery route.

If instead a fixed $1,000 funding budget includes the $10 fee, only $990 converts, producing EGP 49,500 at the same assumed rate. That leaves EGP 500 unpaid on the agreed EGP invoice. State who bears the fee and target the promised recipient amount; do not mark a smaller delivered amount as fully paid.

Step 5: Resolve outcomes and reconcile each invoice#

Create one stable payout intent per invoice allocation and an atomic rule permitting only one live payment attempt for that allocation. Persist the provider submission reference and the approved amount/currency/destination. Use provider duplicate protection within its actual scope and retention period; do not assume one key protects unlimited retries forever.

Authenticate and deduplicate provider events, and do not let an old processing event overwrite a later confirmed outcome. If a request times out after submission, recover it by its original identifier before considering another provider. A missing response is not evidence that no payment exists. A fallback route can double-pay if the first route is still processing.

In the EGP 50,000 example, if the full $1,000 principal returns and the $10 fee is retained, the contractor is again owed EGP 50,000 and the platform has incurred $10 cost. Do not treat the returned principal as income. A replacement at the same illustrative rate with another $10 fee brings total cost to $1,020 for eventual EGP 50,000 delivery. If the new rate changes, use the actual replacement quote rather than reusing the old funding number.

Keep partial credits, bank deductions and partial returns amount-specific. Compare invoice obligations, internal payout records, provider reports and bank movements, including conversion and fees. A provider’s completed label needs the evidence defined for that actual route; app availability or request acceptance alone is not beneficiary credit. Give the contractor a clear status, reference and next review time when payment is delayed.

Start with the chosen route, invoice currency and a small approved cohort. Verify actual beneficiary credit and exception handling before expanding. Recheck live limits, prices and recipient requirements at launch and when they change. Use a route that accepts the real business purpose and can produce a traceable outcome rather than basing the decision on a familiar payment logo.