Openpay

Openpay: PSP Overview for Merchants in Mexico

Openpay is a payment service provider from BBVA that helps Mexican businesses accept and manage online payments across cards, bank transfers, cash at affiliated stores, QR payments with CoDi, and payment links. If you are building or scaling ecommerce in Mexico, Openpay combines multiple collection methods, anti-fraud tools, and flexible integrations under one contract and dashboard. This overview explains how Openpay works, what it supports, and key considerations for merchants evaluating their options.

What Openpay Offers

Openpay provides a gateway and acquiring solution designed for businesses that sell online or collect remote payments. It supports major card brands, local rails, and alternative options so you can offer customers familiar ways to pay while keeping reconciliation within a single portal.

Openpay is part of BBVA’s merchant solutions in Mexico, which means funds settle to a Mexican bank account and you can use BBVA’s onboarding and support processes. Some features are available via plugins and low-code options, while others require direct API integration.

Who It Is For

Openpay fits merchants that:

• Sell to customers in Mexico and settle in a Mexican bank account

• Need to combine cards, SPEI transfers, cash deposits at stores, and CoDi QR in one integration

• Want anti-fraud screening included by default

• Prefer flexible integration paths such as payment button, ecommerce plugin, or direct API

• Plan to support subscriptions or stored cards through tokenization

Payment Methods Supported

Cards

• Accepts national and international cards. Supported brands include Visa, Mastercard, American Express, and Carnet.

• Installments are available as “meses sin intereses” up to 12 months, subject to configuration and applicable fees.

• International cards are accepted for credit transactions.

Bank Transfers (SPEI)

• Customers can pay via interbank transfer using SPEI.

• Funds from SPEI transactions typically settle the next business day to the merchant account.

Cash Payments In Stores

• Customers can select cash and receive a reference number to pay at affiliated physical stores in Mexico, through Openpay’s Paynet network.

• Cash collections usually settle within three business days.

CoDi QR Payments

• Openpay supports CoDi, the QR-based real-time payment platform from Banco de México.

• CoDi enables contactless collections by scanning a QR code or sending a push notification to the customer’s mobile app.

Payment Link

• You can generate a payment link and share it via SMS, email, or social networks.

• Payment links work with the same methods enabled on your account, which can simplify remote invoicing without a checkout page.

Loyalty and BNPL Options

• Openpay supports accepting BBVA loyalty points in applicable scenarios.

• Kueski Pay is available as a buy now, pay later option when integrating by API.

Integration Options

Openpay offers three main integration paths. You can start simple and move to direct API if you need advanced control.

Payment Button

• A prebuilt checkout form that you embed in your site.

• Fastest to implement and includes anti-fraud by default.

• Basic customization for branding.

Ecommerce Plugins

• Ready-made plugins for popular ecommerce platforms so customers can pay without leaving your site.

• Minimal development required and includes anti-fraud protections.

Direct API

• Full REST API for custom checkout experiences and advanced capabilities.

• Supports features like tokenization, subscriptions, and recurring charges.

• Client libraries and SDKs are available for JavaScript, iOS, Android, and common server-side languages such as Node.js, Java, .NET, Ruby, PHP, and Python.

Settlement Times

Settlement depends on the payment method:

• Visa, Mastercard, SPEI: next business day

• American Express and Paynet cash: three business days

You can configure automated payouts to your bank account. Automatic weekly payouts typically have no fee, and merchants can request manual payouts on a 24-hour cadence for an additional fee.

Risk and Compliance

Security is a core element of Openpay’s setup:

• PCI DSS: Openpay states it holds PCI DSS certification for storing card data.

• Network certifications: Openpay references PROSA certification for card handling.

• Anti-fraud: All transactions are evaluated by Openpay’s anti-fraud tool. Screening is included and does not require a separate add-on.

For checkout flows that store or process card data, follow PCI DSS scoping guidance in your implementation. Using Openpay’s tokenization and hosted fields can minimize direct card data exposure in your environment.

Merchant Dashboard and Operations

Openpay provides a portal to:

• Monitor sales, approvals, cancellations, and refunds in real time

• Manage methods enabled on your account

• Access reporting for reconciliation by method and date

• Generate payment links for remote collections

Operational considerations:

• Chargebacks: Openpay notifies merchants via webhook or email and supports document submission to the issuer for dispute resolution. The FAQ notes there is no separate fee for chargeback processing.

• Refunds and cancellations: Manageable through the dashboard or API, depending on your integration path.

Onboarding and Requirements

For businesses incorporated in Mexico, BBVA lists the documentation needed to contract the payment gateway:

• Constancia de Situación Fiscal

• Official ID (INE or passport)

• Power of attorney document for legal representative, if applicable

• Articles of incorporation for legal entities

Once you complete onboarding, you can choose your integration type and request activation of payment link if needed.

Conclusion

Openpay brings together cards, SPEI transfers, cash at stores, and CoDi QR under BBVA’s merchant platform in Mexico. With multiple integration paths and anti-fraud included, it suits businesses that want a single PSP for the Mexican market with options to grow from a plugin or payment button to a fully customized API build. Confirm rates and settlement terms for your specific profile, then choose the integration that matches your development resources and checkout goals.