Request to Pay (R2P) Mexico

API-Driven, Merchant-Owned Payment Experiences in Mexico

Request to Pay (R2P) at Cobre is an API-only collection capability that allows businesses to request payments while fully owning the user experience. R2P enables merchants (or anyone interested in collecting) to design and control how customers select the payment rail and complete the payment, while Cobre orchestrates the underlying bank-native payment request.

R2P is ideal for companies that want maximum flexibility and brand control over their payment journeys.

1. What Cobre Enables with Request to Pay

With Request to Pay, Cobre allows businesses to:

Initiate payment requests via API

Design and control their own payment UX

Collect funds directly into Cobre Balances

Track requests and outcomes through transactions and reports

R2P transforms Cobre into a payments orchestration layer, rather than a hosted checkout.

2. Payment Rails Available in Request to Pay

Request to Pay in Mexico supports the following rail currently:

2.1 Virtual Dynamic CLABEs

One-time-use virtual CLABE account reference

Time-bound and amount-specific

Shared directly with the payer

Immediate settlement upon authorization

Example:
703012345678901234

Contact your KAM to enable this feature

3. Webhook Notifications for Request to Pay

Request to Pay at Cobre supports webhook notifications that allow businesses to receive real-time updates about the status of their payment requests. This enables merchants to react immediately to payment events without polling or manual checks.

What Webhooks Enable

With webhooks, merchants can:

Receive notifications when a payment is completed successfully

Be informed of failed, expired, or canceled requests

Update order or invoice statuses automatically

Trigger downstream processes such as:

Order fulfillment

Service activation

Receipt generation

Internal reconciliation

Webhooks turn payment events into actionable signals for merchant systems.

Event-Driven Payment Updates

Each Request to Pay has a lifecycle, and webhook events reflect meaningful changes in that lifecycle, such as:

Payment status

Processing = awaiting user payment

Completed = payment confirmed

Rejected = payment link expired or abandoned

Failed = technical issue

This ensures merchants always have near real-time visibility into payment outcomes.

How Webhooks Fit into the R2P Flow

Conceptually:

The merchant creates a Request to Pay via API

The customer completes the payment through the selected rail

Cobre processes and settles the payment

A webhook event is sent to the merchant’s configured endpoint

The merchant’s system consumes the event and takes action

This model supports asynchronous, scalable payment processing.

4. How R2P Works Conceptually

From a high-level perspective:

The business/merchant creates a payment request via API

Cobre generates the required payment artifact:

Dynamic virtual CLABE

The business/merchant presents this artifact to the user

The user authorizes the payment through their bank

Funds are credited to the merchant’s Cobre Balance

Transactions and statuses are notified via webhook and available for tracking and reconciliation

The flow is bank-native, secure, and fully traceable.

5. Transactions, Reporting & Reconciliation

Every successful R2P payment generates Transactions in Cobre that:

Credit the business/merchant’s Cobre Balance

Reflect the selected rail

Appear in transaction lists and balance statements

Support reconciliation and accounting workflows

Failed, expired, or canceled requests are also tracked for full lifecycle visibility.

6. Typical Use Cases for Request to Pay

R2P is especially well suited for:

Custom e-commerce checkouts

Marketplaces with tailored payment flows

Embedded finance products

In-app payments

Omnichannel experiences (web, mobile, in-store)

7. Summary — What Cobre Delivers with Request to Pay

With Request to Pay, Cobre enables:

API-only, business/merchant-owned payment flows
Dynamic virtual CLABE account references
Full UX flexibility and control
Unified transactions and reconciliation

Cobre Request to Pay empowers businesses to build custom, bank-native payment experiences while relying on Cobre for orchestration, security, and settlement.

Request to Pay (R2P) Mexico

API-Driven, Merchant-Owned Payment Experiences in Mexico#

1. What Cobre Enables with Request to Pay#

2. Payment Rails Available in Request to Pay#

2.1 Virtual Dynamic CLABEs#

3. Webhook Notifications for Request to Pay#

What Webhooks Enable#

Event-Driven Payment Updates#

How Webhooks Fit into the R2P Flow#

4. How R2P Works Conceptually#

5. Transactions, Reporting & Reconciliation#

6. Typical Use Cases for Request to Pay#

7. Summary — What Cobre Delivers with Request to Pay#

API-Driven, Merchant-Owned Payment Experiences in Mexico

1. What Cobre Enables with Request to Pay

2. Payment Rails Available in Request to Pay

2.1 Virtual Dynamic CLABEs

3. Webhook Notifications for Request to Pay

What Webhooks Enable

Event-Driven Payment Updates

How Webhooks Fit into the R2P Flow

4. How R2P Works Conceptually

5. Transactions, Reporting & Reconciliation

6. Typical Use Cases for Request to Pay

7. Summary — What Cobre Delivers with Request to Pay