> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# Yape

> Accept Yape mobile wallet payments from customers in Peru, who pay from their Yape account and approve each payment on their phone.

<picture noZoom>
  ![Yape logo](https://assets.payrails.io/img/logos/yape/logo.svg)
</picture>

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](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md).

## Supported currencies and countries

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

Yape is available to customers based in:

<table>
  <thead>
    <tr><th>Regions</th><th>Countries</th></tr>
  </thead>

  <tbody>
    <tr><td>**Latin America**</td><td>🇵🇪 Peru</td></tr>
  </tbody>
</table>

## 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.

> [card]
>
> dLocal logo
>
> dLocalYape via dLocal
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/yape/dlocal.md)

> [card]
>
> Mercado Pago logo
>
> Mercado PagoYape via Mercado Pago
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/yape/mercadopago.md)

## Check PSPs

<table>
  <thead>
    <tr><th>Workflow</th><th>[dLocal](https://docs.payrails.com/docs/integrations/payment-methods/yape/dlocal.md)</th><th>[Mercado Pago](https://docs.payrails.com/docs/integrations/payment-methods/yape/mercadopago.md)</th></tr>
  </thead>

  <tbody>
    <tr><td>Payrails SDK</td><td>✔</td><td>✔</td></tr>
    <tr><td>Payrails API</td><td>✔</td><td>✔</td></tr>
    <tr><td>[Delayed / Manual Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✖</td><td>✖</td></tr>
    <tr><td>[Instant Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✔</td><td>✔</td></tr>
    <tr><td>[Cancel / Void](https://docs.payrails.com/docs/orchestration/payment-acceptance/cancel-a-payment.md)</td><td>✖</td><td>✖</td></tr>
    <tr><td>[Refund / Reverse](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md)</td><td>✔</td><td>✔</td></tr>
    <tr><td>[Save Instruments](https://docs.payrails.com/docs/resources/manage-instruments.md)</td><td>✖</td><td>✖</td></tr>
    <tr><td>[Merchant Initiated Transaction (MIT)](https://docs.payrails.com/docs/resources/payments/authorization-flags.md)</td><td>✖</td><td>✖</td></tr>
  </tbody>
</table>

## Ways to integrate Yape

* **Payrails SDK:** the [Web SDK](https://docs.payrails.com/docs/sdks/web.md) 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](https://docs.payrails.com/docs/sdks/web/guides/action-required-event).
* **Payrails API:** call [lookup payment options](https://docs.payrails.com/docs/orchestration/payment-acceptance/lookup-payment-options.md), 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](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) or the execution status. Don't treat the customer's return to your `success` URL as proof of payment.


## Related topics

- [Yape via Mercado Pago](https://docs.payrails.com/docs/integrations/payment-methods/yape/mercadopago.md)
- [Yape via dLocal](https://docs.payrails.com/docs/integrations/payment-methods/yape/dlocal.md)
- [Integrate the React Native SDK](https://docs.payrails.com/docs/sdks/react-native/integrate.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.