FawryPay via dLocal

Accept FawryPay payments from customers in Egypt with dLocal as the payment service provider (PSP). The customer selects FawryPay, gets a FawryPay reference on the dLocal page and pays it later at a Fawry outlet or in the myFawry app.

Supported workflows

Workflow	Supported
Payrails SDK	✔
Payrails API	✔
Delayed / Manual Capture	✖
Instant Capture	✔
Cancel / Void	✖
Refund / Reverse	✔
Save Instruments	✖
Merchant Initiated Transaction (MIT)	✖

Before you begin

Complete these steps before you send your first FawryPay payment through dLocal:

Set up a dLocal integration in your workspace. Follow the dLocal integration setup guide if you don’t have one yet.
Ask dLocal to enable FawryPay on your dLocal merchant account.
In the Payrails Portal, go to Settings → Integrations, open your dLocal integration, select FawryPay under Payment methods, and save.
Add FawryPay as a payment option in your workflow.

Request fields for dLocal

Send these fields in the authorize request, in addition to the standard authorize fields. Required fields must be present for the payment to succeed. Payrails sends Optional fields to the PSP when you include them.

Field	Status	Description
`amount.currency`	Required	Must be `EGP`. Payrails rejects other currencies.
`meta.customer.name`	Required	Sent to dLocal as the payer name, together with `meta.customer.lastName`.
`meta.customer.email`	Required	Sent to dLocal as the payer email.
`meta.customer.country.code`	Required	Payrails sends `EG` to dLocal for FawryPay, whatever the value.
`meta.customer.lastName`	Optional	Added to the payer name.
`meta.customer.phone`	Optional	Sent to dLocal as the payer phone, country code first.
`meta.customer.identityCardNumber`	Optional	Sent to dLocal as the payer document.
`meta.customer.reference`	Optional	Sent to dLocal as the payer user reference.
`meta.clientContext.ipAddress`	Optional	Sent to dLocal as the payer IP address.
`meta.order.description`	Optional	Sent to dLocal as the payment description.
`meta.order.deliveryAddress` or `meta.order.billingAddress`	Optional	Sent to dLocal as the payer address. Payrails uses the delivery address first.

Authorize a FawryPay payment

Call authorize a payment with fawryPay as the paymentMethodCode. The response includes the redirect to the dLocal page.

Authorize request

{
  "amount": {
    "value": "250.00",
    "currency": "EGP"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "fawryPay",
      "amount": {
        "value": "250.00",
        "currency": "EGP"
      }
    }
  ],
  "meta": {
    "customer": {
      "email": "nour.hassan@example.com",
      "name": "Nour",
      "lastName": "Hassan",
      "country": {
        "code": "EG"
      }
    },
    "clientContext": {
      "ipAddress": "203.0.113.10"
    },
    "order": {
      "description": "Example Store order"
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}

After the customer gets their FawryPay reference, dLocal returns them to your success or error URL. The payment is still pending at that point. Confirm the result through webhook notifications or the execution status before you fulfill the order.

How dLocal handles FawryPay

The payment stays pending until the customer pays the reference. dLocal notifies Payrails when the status changes.
Payrails also checks the payment status with dLocal for up to seven days: every two hours on the first day, then once a day.

Getting Started

Payment Orchestration

Token Vault

Analytics & Reporting

Fraud Management

Chargebacks

Monitoring

Resources

Use Cases

Supported workflows

Before you begin

Request fields for dLocal

Authorize a FawryPay payment

How dLocal handles FawryPay

​Supported workflows

​Before you begin

​Request fields for dLocal

​Authorize a FawryPay payment

​How dLocal handles FawryPay

Supported workflows

Before you begin

Request fields for dLocal

Authorize a FawryPay payment

How dLocal handles FawryPay