Yape via dLocal

Accept Yape payments from customers in Peru with dLocal as the payment service provider (PSP). The customer selects Yape in your checkout, approves the payment with their Yape account on the dLocal payment page and returns to your site.

Supported workflows

Before you begin

Complete these steps before you send your first Yape 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 Yape on your dLocal account.
In the Payrails Portal, go to Settings → Integrations, open your dLocal integration, select Yape under Payment methods, and save.
Add Yape 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 `PEN`. Payrails rejects other currencies.
`meta.customer.country`	Required	The customer’s country object. Payrails sends `PE` to dLocal for every Yape payment, whatever `country.code` you send.
`meta.customer.name`	Required	Sent to dLocal as the payer name, together with `meta.customer.lastName`.
`meta.clientContext.clientType`	Required	`desktop`, `mobile` or `app`. Sent to dLocal as the device type.
`meta.customer.identityCardNumber`	Required	The customer’s DNI. Sent to dLocal as the payer document.
`meta.customer.lastName`	Optional	Added to the payer name.
`meta.customer.email`	Optional	Sent to dLocal as the payer email.
`meta.customer.phone`	Optional	Sent to dLocal as the payer phone number.
`meta.order.billingAddress`	Optional	Sent to dLocal as the payer address. `meta.order.deliveryAddress` takes priority when both are present.
`meta.order.description`	Optional	Sent to dLocal as the payment description.
`meta.clientContext.ipAddress`	Optional	Sent to dLocal as the payer IP address.

Authorize a Yape payment

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

Authorize request

{
  "amount": {
    "value": "45.00",
    "currency": "PEN"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "yape",
      "amount": {
        "value": "45.00",
        "currency": "PEN"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Lucía",
      "lastName": "Quispe",
      "identityCardNumber": "43451826",
      "country": {
        "code": "PE"
      }
    },
    "clientContext": {
      "clientType": "mobile",
      "ipAddress": "203.0.113.10"
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}

After the customer approves the payment, they return to your success or error URL. Confirm the result through webhook notifications or the execution status before you fulfill the order.

How dLocal handles Yape

dLocal returns a redirect URL to its hosted payment page. The payment stays pending until the customer approves it, and Payrails completes it from the dLocal notification.
Payrails captures Yape payments through dLocal immediately, so a successful payment is final. To return funds, refund the payment.
Each Yape payment is a one-time, customer-initiated 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 Yape payment

How dLocal handles Yape

​Supported workflows

​Before you begin

​Request fields for dLocal

​Authorize a Yape payment

​How dLocal handles Yape

Supported workflows

Before you begin

Request fields for dLocal

Authorize a Yape payment

How dLocal handles Yape