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

# Mercado Pago

> Accept Mercado Pago Checkout Pro payments in Latin America, and check the PSPs that process Mercado Pago through Payrails.

<picture noZoom>
  ![Mercado Pago logo](https://assets.payrails.io/img/logos/mercadopago/logo-full-bleed.svg)
</picture>

Mercado Pago is a digital wallet and payment platform in Latin America. With Mercado Pago Checkout Pro, the customer leaves your checkout for a Mercado Pago hosted page. There, they pay with a card, their Mercado Pago account balance, Mercado Pago consumer credit, or a local method that Mercado Pago offers in their country.

Payrails processes Mercado Pago through one payment service provider (PSP), which is Mercado Pago itself. Open the Mercado Pago guide below for its setup steps and request examples.

## How a Mercado Pago payment works

Mercado Pago Checkout Pro is a hosted payment page:

1. The customer selects Mercado Pago at checkout.
2. Payrails creates a Mercado Pago checkout session and returns its redirect URL.
3. On the Mercado Pago page, the customer picks how to pay and approves the payment.
4. Mercado Pago sends the customer back to your `returnInfo` URL.
5. Payrails receives the final result from Mercado Pago and updates the payment, including the payment method the customer used.

Each payment is single-use: the customer approves every payment on its own. Payrails captures Mercado Pago 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).

In Peru, customers can also pick [Yape](https://docs.payrails.com/docs/integrations/payment-methods/yape/mercadopago.md) or [PagoEfectivo](https://docs.payrails.com/docs/integrations/payment-methods/pagoefectivo/mercadopago.md) on the Mercado Pago page.

## Supported currencies and countries

Mercado Pago supports the presentment currencies ARS (Argentine peso), BRL (Brazilian real), CLP (Chilean peso), COP (Colombian peso), MXN (Mexican peso), PEN (Peruvian sol) and UYU (Uruguayan peso). Payrails picks the Mercado Pago country site from the payment currency.

Mercado Pago is available to customers based in:

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

  <tbody>
    <tr><td>**Latin America**</td><td>🇦🇷 Argentina🇧🇷 Brazil🇨🇱 Chile🇨🇴 Colombia🇲🇽 Mexico🇵🇪 Peru🇺🇾 Uruguay</td></tr>
  </tbody>
</table>

## Integrate Mercado Pago

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

> [card]
>
> Mercado Pago logo
>
> Mercado PagoMercado Pago Checkout Pro
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/mercadopago/mercadopago.md)

## Check PSPs

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

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

Customers can save their cards in their own Mercado Pago account. Payrails doesn't store a Mercado Pago instrument for later merchant-initiated transactions (MIT).

## Ways to integrate Mercado Pago

* **Payrails SDK:** the [Web SDK](https://docs.payrails.com/docs/sdks/web.md) shows Mercado Pago when your workflow returns it as a payment option, and redirects the customer to the Mercado Pago 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 `mercadoPago` as the `paymentMethodCode` and `hpp` as the `integrationType`. The Mercado Pago guide lists the `meta` fields Mercado Pago needs.

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

- [Mercado Pago](https://docs.payrails.com/docs/integrations/payment-providers/mercado-pago.md)
- [PagoEfectivo via Mercado Pago](https://docs.payrails.com/docs/integrations/payment-methods/pagoefectivo/mercadopago.md)
- [Mercado Pago Checkout Pro](https://docs.payrails.com/docs/integrations/payment-methods/mercadopago/mercadopago.md)


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