Partner Merchant

CentralPay offers two distinct models for partners wishing to assist CentralPay merchants with their technical integration: the Technical Partner and the Integration Partner. In both cases, merchants remain in a direct contractual relationship with CentralPay; the terms regarding API access, resource sharing, and billing differ depending on the model.

Depending on the nature of their business, these partners may also be registered with ORIAS asIOBSPs (intermediaries—“MOBSPs”) in order to provide a legal framework for certain activities involving the introduction andsupport of merchants during onboarding with CentralPay. This article of association does not confer any right of access to funds or any authority to execute payment transactions.

1. Integration Partner

An Integration Partner is a technical service provider contracted by one or more standard merchants. It acts on their behalf and for their account to facilitate their connection to CentralPay services.

Each standard merchant has its own Point of Sale (POS), its own CentralPay Merchant Profile, and signs its application documents and contract (CCSP) directly with CentralPay. The Integrator has no contractual rights to the merchant’s accounts or funds.

1.1. Responsibilities and Operations

• The Integrator uses the API access credentials delegated by each Merchant (dedicated “Integrator” credentials) under a contractual agreement between the Integrator and the Merchant
• He or she may perform the technical tasks necessary for Integration and RUN (configuration, following technical instructions, maintenance), exclusively through these access points, without being able to view account balances or initiate, modify, or cancel a payment transaction.
• Transactions are generally conducted on a “one-to-one” basis: a customer (Payer) pays a single Merchant, with each Merchant retaining its own environment and access points.

1.2. Billing

• Each Merchant is billed directly by CentralPay for the services subscribed to in their CCSP
• The Integration Partner does not get involved in the financial flows at any time

1.3. To learn more about the Integrator model

2. Technical Partner

A Technical Partner is an entity that develops a shared solution (e.g., marketplace, SaaS platform) intended for multiple standard merchants. It operates through one or more Points of Sale (POS) registered under its name in CentralPay, to which merchants can be linked.

Transactions are processed by CentralPay through an internal “Technical Partner Account” mechanism (used by CentralPay to temporarily receive and process funds prior to their transfer to the final Beneficiary). The Technical Partner has no right to dispose of these funds: it merely transmits commercial data and maintains visibility into the cash flows associated with its POSes, without ever being able to initiate a transfer.

2.1. Responsibilities and Operations

• The Technical Partner has its own API credentials issued by CentralPay
• It can transmit technical instructions (sales data, shopping cart, commission, product codes, logistics events, etc.) and track transactions associated with Merchants linked to its Point of Sale (POS) locations
• He has no access to transfer features (including the endpoint transfer) and cannot view balances or make Payouts: CentralPay decides on and executes transactions and fund transfers.
• In this context, CentralPay can process “1-for-X” payments: a customer (payer) can pay multiple Merchants simultaneously, and CentralPay then handles the allocation and disbursement of funds to the Merchants.

2.2. Billing

• CentralPay bills the Technical Partner based on the transactions processed through its Point of Sale (POS) systems, in accordance with the terms set forth in the CCSP and the applicable subscription documents.
• When a commission is applicable, CentralPay may, based on the transaction data provided and in accordance with the terms of the agreement, allocate the funds: the commission portion is then credited to the Technical Partner’s Commission Account, without the Technical Partner holding any third-party funds

To learn more about the Technical Partner model

• The Technical Partner develops a shared solution (e.g., marketplace, SaaS platform) that integrates CentralPay. It operates through one or more Points of Sale (POS) registered in its name, which process transactions from affiliated standard merchants.
• Each participating merchant enters into a contract directly with CentralPay (CCSP and subscription documents) and has its own CentralPay Merchant Profile
• The Technical Partner transmits transaction data (transaction amount, reference numbers, commission, logistics events, etc.) to CentralPay. This data does not trigger any automatic financial action: CentralPay analyzes and verifies the data, then decides whether to process the transaction and initiate the necessary fund transfers.
• CentralPay may decide to impose a temporary hold and/or set a Release date for the funds to be made available to a Merchant (e.g., pending delivery or shipment), in accordance with its risk policy, network rules, and regulatory obligations.
• The Technical Partner never holds third-party funds, does not issue any payment orders, and cannot intervene in payouts or account management. It acts neither on behalf of third parties nor in the name of CentralPay.
• The Technical Partner’s access is limited to the views and features strictly necessary for the transmission and tracking of Technical Instructions; there is no access to the “Technical Partner Account” as an account (no right of execution, no right of disposal, no access to balances)
• In the event of ORIAS registration as an IOBSP (intermediary – “MOBSP”) and if a separate contractual framework so provides, the Technical Partner may assist merchants in onboarding (providing a registration link, assisting with documentation), subject to prior approval by CentralPay

3. Common Compliance Rules

For both models:

• The Partner is not a Payment Service Provider (PSP), has no authority to execute payment transactions, and does not hold any third-party funds in connection with payment services
• Accounts, the provision of funds, payouts, and the protection of funds are managed and overseen by CentralPay in its capacity as a payment service provider (PSP)
• No regulatory delegation of authority to provide payment services (such as a PSP agent) is granted to these partners

3.1. Contractual Relationship with Merchants

The Partner (whether a technical partner or integration partner) maintains its own business relationship with its users and remains responsible for the services offered on its platform. It is free to define the terms and conditions of use applicable to its services.

For their part, the affiliated merchants:

• Create their own CentralPay Merchant Profile as part of a personalized Enrollment process
• Sign the CCSP and the applicable subscription documents (including the designation of a partner, if applicable) directly with CentralPay
• Acknowledge that the partner may perform certain technical actions as part of its integration (e.g., submitting an order, submitting a shopping cart, following technical instructions), without this constituting a payment order or access to funds

CentralPay then works directly with the affiliated Merchant to:

• creating and managing their account (electronic signature, POS assignment, linking to a partner)
• the regulatory processing of submitted supporting documents (KYC/KYB, anti-money laundering and counter-terrorism financing)
• updating documentation or conducting additional verifications necessary for the proper execution of payment services

This entire organization is based on a strictly defined contractual framework:

• The partner signs a dedicated contract with CentralPay that outlines its role and access rights (API/portal) and, if applicable, the commission terms.
• Affiliated merchants sign their CentralPay contractual documents (CCSP and subscription) directly, in which their affiliation with the partner may be specified
• The partner’s terms and conditions apply solely to the use of its own platform. They may not interfere with CentralPay’s payment services or supersede CentralPay’s contractual documents.

4. ORIAS Declaration (IOBSP / “MOBSP”)

An Integration Partner or a Technical Partner may, if required by its business activities, be registered with ORIAS as an IOBSP (intermediary—“MOBSP”). This status is distinct from thatof a Payment Service Provider (PSP) agent (as defined in Article L.523-1 of the Monetary and Financial Code).

Depending on the applicable contractual framework, this registration may allow for:

• To present CentralPay’s services and assist the Merchant with the Onboarding process
• To assist with the preparation of the application (without ever replacing the regulatory reviews conducted by CentralPay)

This status does not alter the restrictions set forth above in any way: it does not confer any rights to the funds or any authority to execute payment transactions. CentralPay remains solely responsible for onboarding, conducting regulatory checks, and executing payment services.