Skip to main content
FawryPay is a popular payment method in Egypt. Customers get a FawryPay reference at checkout and pay it later, in cash or by card, at a Fawry outlet, kiosk or point of sale, or in the myFawry app. Payrails processes FawryPay through three payment service providers (PSPs). The flow is similar with each one, but the required request fields and the supported workflows differ. Pick a PSP below for its setup steps and request examples.

​
How a FawryPay payment works

FawryPay is a redirect payment method with a delayed, offline payment step:
  1. The customer selects FawryPay at checkout.
  2. Payrails returns a redirect URL from the PSP, and the customer goes to the PSP’s FawryPay page.
  3. The customer enters their details and receives a FawryPay reference.
  4. The customer returns to your returnInfo URL. The payment stays pending.
  5. The customer pays the reference at a Fawry outlet or in the myFawry app.
  6. The PSP notifies Payrails, and Payrails updates the payment.
The payment can stay pending for hours or days, until the customer pays. Payrails captures FawryPay payments immediately, so a paid reference is final. To return funds, refund the payment. Refunds work with dLocal and Fawry, but not with Flutterwave.

​
Supported currencies and countries

FawryPay supports EGP (Egyptian pound) as its only presentment currency.

​
Integrate FawryPay

Choose the PSP that processes FawryPay for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

dLocal

FawryPay via dLocal

Fawry

FawryPay via Fawry

Flutterwave

FawryPay via Flutterwave

​
Compare PSPs

FawryPay is a one-off payment method: no PSP saves a FawryPay instrument for later merchant-initiated transactions (MIT). With dLocal and Fawry, cancel a FawryPay payment to stop a reference the customer hasn’t paid yet.

​
Ways to integrate FawryPay

  • Payrails SDK: the Web SDK shows FawryPay when your workflow returns it as a payment option, and redirects the customer to the PSP’s FawryPay page. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with fawryPay as the paymentMethodCode. Each PSP guide lists the meta fields that PSP requires.
In both cases, confirm the final result through webhook notifications or the execution status. Don’t treat the customer’s return to your success URL as proof of payment: the customer pays later, offline.
Last modified on October 2, 2026