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

# OXXO

> Accept OXXO cash payments in Mexico, where customers get a voucher with a reference code and barcode and pay it in cash at an OXXO store.

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

OXXO is a cash payment method in Mexico. Customers get a payment voucher for their purchase online, then pay it in cash at an OXXO convenience store. It gives customers who prefer cash, or don't have a card, a way to pay online. Payrails processes OXXO through dLocal as the payment service provider (PSP).

## How an OXXO payment works

OXXO is a voucher payment method:

1. The customer selects OXXO at checkout.
2. Payrails returns a redirect URL from dLocal, and the customer goes to the dLocal payment page.
3. The page shows an OXXO voucher with a reference code and a barcode.
4. The customer pays the amount in cash at an OXXO store with the reference code or the barcode.
5. Payrails receives the final result from dLocal and updates the payment.

The payment stays pending until the customer pays at the store. Each payment is single-use: every purchase gets its own voucher. Payrails captures OXXO 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

OXXO supports MXN (Mexican peso) as its only presentment currency.

OXXO is available to customers based in:

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

  <tbody>
    <tr><td>**Latin America**</td><td>🇲🇽 Mexico</td></tr>
  </tbody>
</table>

## Integrate OXXO

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

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

## Check PSPs

<table>
  <thead>
    <tr><th>Workflow</th><th>[dLocal](https://docs.payrails.com/docs/integrations/payment-methods/oxxo/dlocal.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>

## Ways to integrate OXXO

* **Payrails SDK:** the [Web SDK](https://docs.payrails.com/docs/sdks/web.md) shows OXXO when your workflow returns it as a payment option, and redirects the customer to the dLocal 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 `oxxo` as the `paymentMethodCode`. The PSP guide lists the `meta` 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. A customer who returns to your site hasn't paid yet, so wait for the result before you ship the order.


## Related topics

- [OXXO via dLocal](https://docs.payrails.com/docs/integrations/payment-methods/oxxo/dlocal.md)
- [Create a new Ruleset](https://docs.payrails.com/reference/createruleset.md)
- [Update a Ruleset](https://docs.payrails.com/reference/updateruleset.md)


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