Named Accounts in Mexico

🚧 Named Accounts is coming soon. This feature is currently under development and not yet available. Stay tuned — we'll update this page as soon as it's released. In the meantime, feel free to reach out to your Key Account Manager if you have any questions.

Surface merchant identity in SPEI transactions for PSPs and Payment Aggregators in Mexico

Named Accounts enable Payment Service Providers (PSPs) and Payment Aggregators (PAs) operating in Mexico to surface their merchants’ identities in SPEI transaction records for both pay-ins and pay-outs. Instead of showing only the PSP or Payment Aggregator name in SPEI records, Named Accounts allow transactions to display a combined identifier such as [PSP Name] | [Merchant Name].

This capability helps PSPs and Payment Aggregators provide a better merchant experience, improve reconciliation, and increase transparency in bank statements, CEP receipts, and payment records — without requiring each merchant to go through a full individual KYB onboarding with Cobre.

ℹ️ Named Accounts is a gated feature. It must be enabled for your client_id by Cobre before it can be used. Contact your Key Account Manager to request access.

1. What Cobre Enables with Named Accounts

With Named Accounts, Cobre enables PSPs and Payment Aggregators to:

Screen merchants through a simplified compliance process

Assign dedicated CLABE accounts to approved merchants

Surface merchant names in SPEI sender and beneficiary fields

Support merchant-level visibility for both pay-ins and pay-outs

Improve reconciliation using merchant-identifiable SPEI records

Reuse an approved Subclient across multiple Named Accounts

Maintain standard Cobre Balance capabilities while improving transaction transparency

2. Named Accounts in the Cobre Model

Named Accounts extend the standard Cobre Balance model in Mexico by linking an account to an approved Subclient, which represents the merchant.

Conceptually:

Subclients represent merchants within a PSP or Payment Aggregator ecosystem.

Named Accounts are Cobre Balance accounts linked to approved Subclients.

CLABEs are assigned to Named Accounts and carry merchant identity in SPEI records.

Money Movements can be executed from Named Accounts for pay-outs.

Pay-ins can be received directly into the merchant’s Named Account.

Transactions include records that help identify the merchant behind the movement.

This allows PSPs and Payment Aggregators to operate at merchant scale while keeping Cobre as the account, movement, and reconciliation infrastructure.

3. Key Capabilities / Options

3.1 Subclient Registration and Screening

A Subclient is a lightweight merchant identity record created inside Cobre.

Before a merchant can operate under their own name in SPEI, they must be registered as a Subclient and pass a simplified compliance screening. This screening is designed for PSPs and Payment Aggregators operating at scale and replaces the need for each merchant to complete a full individual KYB process with Cobre.

Subclient screening is asynchronous:

The Subclient starts in a processing state

Cobre reviews the submitted merchant information

The final result is communicated through status updates

Once approved, the Subclient can be linked to one or more Named Accounts

A Subclient only needs to be registered once and can be reused across multiple accounts for the same merchant.

3.2 Named Account Creation

Once a Subclient is approved, a standard Cobre Balance account can be created and linked to that Subclient.

Cobre then registers the account with the underlying provider, which assigns a CLABE and configures the SPEI display name using a combined identifier:

[PSP Acronym] | [Merchant Name]

For example:

PXT | MerchantABC

Once the account is enabled, the merchant can operate under their own identity in SPEI while still being part of the PSP or Payment Aggregator’s Cobre setup.

3.3 SPEI Name Surfacing

Named Accounts allow SPEI records to show merchant-level identity in both sender and beneficiary fields.

This is valuable because, by default, when a merchant transacts through a PSP or Payment Aggregator, SPEI records typically show the PSP or PA name — not the underlying merchant.

With Named Accounts:

Pay-ins can show the merchant as the receiving party

Pay-outs can show the merchant as the sending party

CEP receipts, bank statements, and reconciliation records become easier to interpret

End users and counterparties can recognize the merchant behind the transaction

3.4 Standard Cobre Balance Capabilities

Named Accounts support the same capabilities as standard Cobre Balance accounts.

Once enabled, a Named Account can support:

Pay-ins — receive SPEI transfers directly to the merchant’s CLABE

Pay-outs — send SPEI payments from the Named Account

Virtual CLABEs — generate additional reference CLABEs linked to the Named Account

R2P SPEI — initiate Request to Pay from the Named Account

This means PSPs and Payment Aggregators do not need to choose between merchant identity and product functionality. Named Accounts add identity surfacing while preserving the standard account capabilities.

4. Core Concepts and Terminology

Named Account: A standard Cobre Balance account linked to an approved Subclient. It functions like a regular account but surfaces the merchant’s identity in SPEI transaction records.

Subclient: A lightweight merchant identity record held within Cobre. It contains the legal, tax, and beneficial ownership information required for simplified compliance screening.

Subclient Screening: An asynchronous compliance review performed before a merchant can be linked to a Named Account.

SPEI Name Surfacing: The ability to display a combined PSP and merchant name in SPEI transaction records, such as [PSP Acronym] | [Merchant Name].

Short Name: The merchant name used in the SPEI display label. It should be concise because SPEI applies a 40-character limit to the combined PSP and merchant identifier.

PSP Acronym: The identifier defined by the PSP or Payment Aggregator and included as part of the SPEI display name.

CLABE: The Mexican bank account identifier assigned to the Named Account for SPEI transfers.

5. Speed, Settlement & Reliability

Named Accounts follow the standard behavior of the underlying Cobre Balance and SPEI flows.

From an operational perspective:

Subclient screening is asynchronous and must be completed before the merchant can operate under their own identity.

Once the Subclient is approved and the Named Account is enabled, the account can operate using standard Cobre Balance capabilities.

Pay-ins and pay-outs follow the normal timing and reliability of the relevant SPEI-based flows.

Status updates and reporting allow PSPs and Payment Aggregators to track account readiness and transaction outcomes.

This ensures that merchant identity surfacing does not change the core behavior of Cobre’s payment infrastructure.

6. Typical Business Use Cases

Named Accounts are especially useful for:

PSPs enabling merchants to receive SPEI pay-ins under their own name

Payment Aggregators serving many merchants without onboarding each one through full KYB

Marketplaces that want merchant-level identity in payment records

Platforms that need better merchant-level reconciliation in Mexico

Merchant acquirers or payment facilitators that want clearer transaction records

Businesses that need pay-in and pay-out flows while preserving merchant identity

Named Accounts are a strong fit when PSPs or Payment Aggregators need to support many merchants while improving transparency in SPEI records and simplifying reconciliation across merchant portfolios.

7. Transactions, Reporting & Reconciliation

Named Accounts improve reconciliation by making merchant identity visible in SPEI transaction records.

For PSPs and Payment Aggregators, this enables:

Easier matching between SPEI records and merchant activity

Clearer identification of pay-ins received for each merchant

Better tracking of pay-outs initiated from merchant-specific accounts

More readable CEP receipts and bank statements

Stronger operational reporting at the merchant level

Because Named Accounts remain standard Cobre Balance accounts, transactions can still be tracked through Cobre’s standard reporting and reconciliation flows.

8. Governance, Controls & Auditability

Named Accounts include governance controls at both the merchant and account levels.

Key controls include:

Subclient screening before a merchant can operate under their own identity

Gated enablement by Cobre for eligible clients

Reuse of approved Subclients across multiple accounts

Auditability of the Subclient and account relationship

Traceability of transactions associated with merchant-linked accounts

Important considerations:

SPEI imposes a 40-character limit on the combined [PSP Acronym] | [Merchant Name] identifier.

The Subclient short_name is the merchant name displayed in SPEI, so it should be concise.

If the combined identifier exceeds the SPEI character limit, account registration may fail at the provider level.

A rejected Subclient cannot be resubmitted; a new Subclient record must be created.

An approved Subclient may become rejected in the future due to post-approval compliance review.

If a Subclient is later rejected, Cobre notifies the client. Existing accounts linked to that Subclient are not automatically affected, and the client should contact their KAM for guidance.

9. Named Accounts vs Standard Cobre Balance Accounts

Dimension	Standard Cobre Balance Account	Named Account
SPEI display name	PSP or Payment Aggregator name	`[PSP Acronym] - [Merchant Name]`
Merchant identity in SPEI	Not surfaced	Surfaced in sender and beneficiary fields
Merchant screening	Not applicable at account level	Required through Subclient screening
Pay-ins	Supported	Supported
Pay-outs	Supported	Supported
Virtual CLABEs	Supported	Supported
R2P SPEI	Supported	Supported
Best for	PSP-owned or platform-level operations	Merchant-level operations with SPEI identity visibility

Named Accounts are best when the PSP or Payment Aggregator wants to preserve standard Cobre Balance functionality while making the merchant visible in SPEI records.

10. Summary — What Cobre Delivers with Named Accounts

Cobre enables PSPs and Payment Aggregators in Mexico to:

Surface merchant identities in SPEI transaction records
Register merchants as Subclients through simplified screening
Link approved Subclients to dedicated Cobre Balance accounts
Display combined PSP and merchant identifiers in SPEI records
Support pay-ins, pay-outs, Virtual CLABEs, and R2P SPEI
Improve reconciliation, transparency, and merchant-level reporting
Scale merchant operations without full individual KYB onboarding for each merchant

Named Accounts give PSPs and Payment Aggregators a scalable way to operate merchant-level payment flows in Mexico while preserving the transparency required by merchants, payers, counterparties, and finance teams.

Named Accounts in Mexico

Surface merchant identity in SPEI transactions for PSPs and Payment Aggregators in Mexico#

1. What Cobre Enables with Named Accounts#

2. Named Accounts in the Cobre Model#

3. Key Capabilities / Options#

3.1 Subclient Registration and Screening#

3.2 Named Account Creation#

3.3 SPEI Name Surfacing#

3.4 Standard Cobre Balance Capabilities#

4. Core Concepts and Terminology#

5. Speed, Settlement & Reliability#

6. Typical Business Use Cases#

7. Transactions, Reporting & Reconciliation#

8. Governance, Controls & Auditability#

9. Named Accounts vs Standard Cobre Balance Accounts#

10. Summary — What Cobre Delivers with Named Accounts#

Surface merchant identity in SPEI transactions for PSPs and Payment Aggregators in Mexico

1. What Cobre Enables with Named Accounts

2. Named Accounts in the Cobre Model

3. Key Capabilities / Options

3.1 Subclient Registration and Screening

3.2 Named Account Creation

3.3 SPEI Name Surfacing

3.4 Standard Cobre Balance Capabilities

4. Core Concepts and Terminology

5. Speed, Settlement & Reliability

6. Typical Business Use Cases

7. Transactions, Reporting & Reconciliation

8. Governance, Controls & Auditability

9. Named Accounts vs Standard Cobre Balance Accounts

10. Summary — What Cobre Delivers with Named Accounts