EasyPaisa via dLocal

Accept EasyPaisa payments from customers in Pakistan with dLocal as the payment service provider (PSP). The customer selects EasyPaisa, confirms the payment on the dLocal payment page and returns to your site.

Supported workflows

Before you begin

Complete these steps before you send your first EasyPaisa 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 EasyPaisa on your dLocal merchant account.
In the Payrails Portal, go to Settings → Integrations, open your dLocal integration, select Easypaisa under Payment methods, and save.
Add EasyPaisa 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. Payrails checks Required fields and returns an error when one is missing. Fields required by the PSP pass the Payrails checks but the PSP can decline the payment without them.

Field	Status	Description
`amount.currency`	Required	Must be `PKR`. 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 `PK` to dLocal for EasyPaisa, whatever the value.
`meta.customer.lastName`	Recommended	Added to the payer name.
`meta.customer.phone`	Recommended	Sent to dLocal as the payer phone, country code first.
`meta.customer.identityCardNumber`	Recommended	Sent to dLocal as the payer document, for example the customer’s national identity card number.
`meta.clientContext.ipAddress`	Recommended	Sent to dLocal as the payer IP address.
`meta.customer.reference`	Optional	Sent to dLocal as the payer user reference.
`meta.order.description`	Optional	Sent to dLocal as the payment description.

Authorize an EasyPaisa payment

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

Authorize request

{
  "amount": {
    "value": "1500.00",
    "currency": "PKR"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "easypaisa",
      "amount": {
        "value": "1500.00",
        "currency": "PKR"
      }
    }
  ],
  "meta": {
    "customer": {
      "email": "ayesha.khan@example.com",
      "name": "Ayesha",
      "lastName": "Khan",
      "identityCardNumber": "4210112345678",
      "phone": {
        "countryCode": "+92",
        "number": "3001234567"
      },
      "country": {
        "code": "PK"
      }
    },
    "clientContext": {
      "ipAddress": "203.0.113.10"
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}

After the customer confirms the payment, dLocal returns them to your success or error URL. Confirm the result through webhook notifications or the execution status before you fulfill the order.

How dLocal handles EasyPaisa

The payment is pending until the customer confirms it. dLocal notifies Payrails of the final result.
Payrails also checks the payment status with dLocal every hour, for up to one 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 an EasyPaisa payment

How dLocal handles EasyPaisa

​Supported workflows

​Before you begin

​Request fields for dLocal

​Authorize an EasyPaisa payment

​How dLocal handles EasyPaisa

Supported workflows

Before you begin

Request fields for dLocal

Authorize an EasyPaisa payment

How dLocal handles EasyPaisa