Merchant Profile

The Merchant Profile represents a Merchant technically and operationally within the CentralPay platform.

It serves as the foundation for:
• Its accounts: payment or electronic money accounts;
• Its administration: API access, user profiles, available payment services;
• Its technical configuration: webhooks, notifications, points of sale, acceptance rules, bank accounts;
• Its regulatory file: KYC/KYB, AML-CFT, risk scoring, contracting, pricing schedule…

The Merchant Profile corresponds to the API object Merchant and is created automatically after validation of its registration (via the API object Merchant-Enrollment).

1. Profile Types by Contractual Model

Each Merchant type is associated with a specific contractual model.

Standard Type : STANDARD

The standard Merchant is a business or professional that collects payments for its own account. It has one or more payment accounts and can access CentralPay services via API or through a partner.

👉 Learn more about the Merchant model

Integration Partner Type : INTEGRATOR

The Integration Partner supports multiple standard Merchants in their technical integration with CentralPay. Each standard Merchant has its own point of sale and an individual contract. The Integrator uses the API access provided by each Merchant within the framework of a contractual relationship.

• May have a payment account and a commission account for its own needs
• A separate point of sale is created for each supported Merchant
• May perform API calls and technical actions via access delegated by the Merchant (monitoring Technical Instructions, configuration, RUN), without access to balances or authority to initiate/modify/execute a payment operation in its own name
• CentralPay invoices each Merchant directly

👉 Learn more about the Integrator Partner model

MOBSP Integration Partner Type : INTEGRATOR + MOBSP

The MOBSP Integration Partner is an Integrator with a regulatory mandate. It can initiate a relationship request on behalf of a standard Merchant and provide technical support via the onboarding API. Like any Integrator, it acts solely through the API access provided by the Merchant.

• Same rights and operation as an Integrator
• May initiate a complete enrollment request via API
• May support the merchant during enrollment

👉 Learn more about the MOBSP Integrator Partner model

Technical Partner Type : TECHNIQUE

The Technical Partner develops a shared solution (e.g., marketplace, SaaS platform) and operates from one or more points of sale opened in its name, to which standard Merchants can be attached. It uses its own API access to transmit commercial data and monitor operations linked to these points of sale, without ever having execution authority over payment operations.

• One or more points of sale may be used to consolidate merchant activities (e.g., marketplace, SaaS platform)
• CentralPay API access specific to the Technical Partner
• CentralPay invoices the Technical Partner
• Cannot initiate enrollment on behalf of and for the account of merchants (unless MOBSP framework applies)

👉 Learn more about the Technical Partner model

MOBSP Technical Partner Type : TECHNIQUE + MOBSP

The MOBSP Technical Partner is authorized to initiate a relationship request on behalf of its users. It can transmit the necessary information via the onboarding API but does not intervene in the execution of payment operations.

• Same rights and operation as a Technical Partner
• May initiate a complete enrollment request via API
• May support the merchant during enrollment

👉 Learn more about the MOBSP Technical Partner model

EMD Agent Type : DME

The EMD Agent (Electronic Money Distributor) transmits loading, transfer, or refund instructions in electronic money on behalf of Participants. It operates within the electronic money model (CUSTOM currencies) and may receive a commission on operations, without providing regulated payment services (e.g., SEPA transfer, direct debit, card).

👉 Learn more about the EMD Agent model

PSP Agent Type : AGENT

The PSP Agent is a Payment Service Provider (PSP) Agent registered with ACPR. It acts on behalf of and for the account of CentralPay within a strictly defined contractual scope. Depending on the model adopted (Simple Agent / Collecting Agent / Delegated Agent), it may support enrollment, perform certain level 1 KYC/KYB due diligence, and/or intervene in the collection, allocation, and provision of funds via mechanisms provided by CentralPay. CentralPay remains responsible for the payment services provided and regulatory controls.

👉 Learn more about the PSP Agent model

Participant Type : BASIC

The Participants are natural or legal persons who are clients of a CentralPay Intermediary Merchant (Agent or EMD). They have one or more payment accounts or electronic money accounts to receive funds issued by the Intermediary and can access the Merchant Portal to view their operations and manage their outgoing transfers.

They operate to sell products or services, for LMNP activity, or for non-commercial needs (crowdfunding, personal wallet, collective projects, etc.).

Participants open accounts with CentralPay. The relationship may be initiated and/or supported by the Intermediary Merchant, but regulated services remain provided by CentralPay. The framework for account usage is defined by the applicable CentralPay documents (and, where applicable, by the Intermediary’s Terms of Use for commercial conditions and the services it provides).

2. Contact Email Configuration

You can customize the contact email addresses associated with your merchant profile so that notifications, reminders, or contractual communications are properly addressed to the right contacts.

• Contact email: primary contact for the merchant profile
• Administrative email: responsible for legal or contractual matters
• Technical email: responsible for integration or incidents
• Financial email: responsible for billing or banking flows

ℹ️ By default, these addresses are initialized with the email of the merchant profile holder. They can be modified at any time from the Merchant Portal. 

Access to contact email configuration: