> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# FawryPay

> Accept FawryPay payments in Egypt, where customers get a reference at checkout and pay it later in cash or by card at a Fawry outlet or in myFawry.

<picture noZoom>
  ![FawryPay logo](https://assets.payrails.io/img/logos/fawrypay/logo.svg)
</picture>

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](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md).

## Supported currencies and countries

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

FawryPay is available to customers based in:

<table>
  <thead>
    <tr><th>Regions</th><th>Countries</th></tr>
  </thead>

  <tbody>
    <tr><td>**Africa**</td><td>🇪🇬 Egypt</td></tr>
  </tbody>
</table>

## 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.

> [card]
>
> dLocal logo
>
> dLocalFawryPay via dLocal
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/fawrypay/dlocal.md)

> [card]
>
> Fawry logo
>
> FawryFawryPay via Fawry
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/fawrypay/fawry.md)

> [card]
>
> Flutterwave logo
>
> FlutterwaveFawryPay via Flutterwave
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/fawrypay/flutterwave.md)

## Check PSPs

<table>
  <thead>
    <tr><th>Workflow</th><th>[dLocal](https://docs.payrails.com/docs/integrations/payment-methods/fawrypay/dlocal.md)</th><th>[Fawry](https://docs.payrails.com/docs/integrations/payment-methods/fawrypay/fawry.md)</th><th>[Flutterwave](https://docs.payrails.com/docs/integrations/payment-methods/fawrypay/flutterwave.md)</th></tr>
  </thead>

  <tbody>
    <tr><td>Payrails SDK</td><td>✔</td><td>✔</td><td>✔</td></tr>
    <tr><td>Payrails API</td><td>✔</td><td>✔</td><td>✔</td></tr>
    <tr><td>[Delayed / Manual Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✖</td><td>✖</td><td>✖</td></tr>
    <tr><td>[Instant Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✔</td><td>✔</td><td>✔</td></tr>
    <tr><td>[Cancel / Void](https://docs.payrails.com/docs/orchestration/payment-acceptance/cancel-a-payment.md)</td><td>✖</td><td>✔</td><td>✖</td></tr>
    <tr><td>[Refund / Reverse](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md)</td><td>✔</td><td>✔</td><td>✔</td></tr>
    <tr><td>[Save Instruments](https://docs.payrails.com/docs/resources/manage-instruments.md)</td><td>✖</td><td>✖</td><td>✖</td></tr>
    <tr><td>[Merchant Initiated Transaction (MIT)](https://docs.payrails.com/docs/resources/payments/authorization-flags.md)</td><td>✖</td><td>✖</td><td>✖</td></tr>
  </tbody>
</table>

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](https://docs.payrails.com/docs/sdks/web.md) 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](https://docs.payrails.com/docs/sdks/web/guides/action-required-event).
* **Payrails API:** call [lookup payment options](https://docs.payrails.com/docs/orchestration/payment-acceptance/lookup-payment-options.md), 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](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) or the execution status. Don't treat the customer's return to your `success` URL as proof of payment: the customer pays later, offline.


## Related topics

- [FawryPay via Fawry](https://docs.payrails.com/docs/integrations/payment-methods/fawrypay/fawry.md)
- [Fawry](https://docs.payrails.com/docs/integrations/payment-providers/fawry.md)
- [FawryPay via Flutterwave](https://docs.payrails.com/docs/integrations/payment-methods/fawrypay/flutterwave.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.