WafaCash via dLocal

Accept WafaCash payments from customers in Morocco with dLocal as the payment service provider (PSP). The customer gets the payment details on a dLocal-hosted page and pays at a WafaCash agency.

Supported workflows

Before you begin

Complete these steps before you send your first WafaCash 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 WafaCash on your dLocal account for Morocco.
In the Payrails Portal, go to Settings → Integrations, open your dLocal integration, select WafaCashWallet under Payment methods, and save.
Add WafaCash 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 `MAD`. Payrails rejects other currencies.
`meta.customer.name`	Required	The customer’s first name. 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 the payment to dLocal with the country `MA`, whatever value you send.
`meta.customer.lastName`	Optional	Added to the payer name.
`meta.customer.phone`	Optional	Sent to dLocal as the payer phone.
`meta.customer.identityCardNumber`	Optional	Sent to dLocal as the payer document.
`meta.customer.birthDate`	Optional	Sent to dLocal as the payer’s birth date.
`meta.customer.reference`	Optional	Sent to dLocal as the payer’s user reference.
`meta.clientContext.ipAddress`	Optional	Sent to dLocal as the payer’s IP address.
`meta.clientContext.deviceFingerprint`	Optional	Sent to dLocal as the payer’s device ID.
`meta.order.billingAddress`	Optional	Sent to dLocal as the payer address. `meta.order.deliveryAddress` takes priority when you send both.
`meta.order.description`	Optional	Sent to dLocal as the payment description.

Authorize a WafaCash payment

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

Authorize request

{
  "amount": {
    "value": "100.00",
    "currency": "MAD"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "wafaCashWallet",
      "amount": {
        "value": "100.00",
        "currency": "MAD"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Yasmine",
      "lastName": "Benali",
      "email": "yasmine.benali@example.com",
      "country": {
        "code": "MA"
      }
    },
    "clientContext": {
      "ipAddress": "203.0.113.10"
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}

The payment stays pending until the customer pays at a WafaCash agency. Confirm the result through webhook notifications or the execution status before you fulfill the order.

How dLocal handles WafaCash

Payrails sends WafaCash payments to dLocal with the country MA and checks that the currency is MAD.
The payment stays pending after authorization. dLocal sends Payrails a notification when the customer pays, and Payrails then completes the payment.
Payrails removes digits and punctuation from the payer name before it sends the name to dLocal.
Payrails sends full and partial refunds to dLocal against the original payment.

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 WafaCash payment

How dLocal handles WafaCash

​Supported workflows

​Before you begin

​Request fields for dLocal

​Authorize a WafaCash payment

​How dLocal handles WafaCash

Supported workflows

Before you begin

Request fields for dLocal

Authorize a WafaCash payment

How dLocal handles WafaCash