Skip to main content
Yape is a mobile wallet in Peru. Customers pay from their Yape account instead of with a card, and approve each payment with their phone. Payrails processes Yape through two payment service providers (PSPs): dLocal and Mercado Pago. With dLocal, the customer selects Yape in your checkout. With Mercado Pago, the customer selects Mercado Pago in your checkout and picks Yape on the Mercado Pago page. Pick a PSP below for its setup steps and request examples.

​
How a Yape payment works

Yape is a redirect payment method:
  1. The customer selects Yape, or Mercado Pago, at checkout.
  2. Payrails returns a redirect URL from the PSP, and the customer goes to the PSP’s payment page.
  3. The customer approves the payment with their Yape account.
  4. The customer returns to your returnInfo URL.
  5. Payrails receives the final result from the PSP and updates the payment.
Each payment is single-use: the customer approves every payment on its own. Payrails captures Yape payments immediately, so a successful payment is final. To return funds, refund the payment.

​
Supported currencies and countries

Yape supports PEN (Peruvian sol) as its only presentment currency.

​
Integrate Yape

Choose the PSP that processes Yape for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

dLocal

Yape via dLocal

Mercado Pago

Yape via Mercado Pago

​
Check PSPs

​
Ways to integrate Yape

  • Payrails SDK: the Web SDK shows the payment option your workflow returns — Yape for dLocal, or Mercado Pago for Mercado Pago — and redirects the customer to the PSP’s payment page. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with yape as the paymentMethodCode for dLocal, or mercadoPago for Mercado Pago. Each PSP guide lists the fields that PSP requires.
In both cases, confirm the final result through webhook notifications or the execution status. Don’t treat the customer’s return to your success URL as proof of payment.
Last modified on October 2, 2026