Skip to main content

Introduction

OXXO uses a redirect-based payment flow. When a customer selects OXXO at checkout, they are redirected to a hosted page where an OXXO payment voucher (with a reference code and barcode) is generated. The customer then visits any OXXO store and pays using the reference code or by scanning the barcode at the register. This guide explains the process of integrating OXXO into your app or website using Payrails.

Pre-requisites

Before you start accepting OXXO payments with Payrails, there are a few requirements you must meet:

Ways to integrate OXXO

Payrails SDK

Server-to-server integration

Parse OXXO from lookup response

Pass OXXO payment method in request to authorize payment with Payrails

Note on amountsMXN uses 2 decimal places. Amounts should be provided in the smallest currency unit—for example, 180000 for $1,800.00 MXN.
OXXO is a redirect-based, single-use payment method. After calling the authorize endpoint, the customer will be redirected to a hosted page with their OXXO payment voucher (reference code and barcode). The customer pays at any OXXO store. Vouchers expire after 10–12 days depending on provider. Notification delay is immediate or up to 24 hours depending on the agreed solution. Once confirmed, the customer will be redirected back to the returnInfo.success URL.

Handle the redirect response

Supported currencies

OXXO via dLocal supports the following presentment currency:
  • MXN — Mexican Peso

Supported regions / countries

Supported workflows and services

Last modified on September 28, 2026