CentralPay Glossary

Estimated reading: 8 minutes

1. Types of Actors

Label	Description
Actor	Any entity identified on the CentralPay platform. This may be a Merchant Profile, a Point of Sale (POS), a third-party establishment, or CentralPay.
Merchant Profile	The Merchant Profile technically and operationally represents a merchant on the CentralPay platform. It serves as the basis for: • His accounts: Payment Accounts or Electronic Money Accounts; • Administration: API access, User Profiles, available services; • Its technical configuration: webhooks, notifications, Point of Sale (POS) systems, acceptance rules, Bank Accounts; • Its regulatory documentation: KYC/KYB, AML/CFT, risk scoring, contract management, fee schedule… The Merchant Profile corresponds to the API object ` `Merchant` ` and is created automatically after the registration is validated (via the API object ` `Merchant-Enrollment``).
Standard Merchant	A legal entity or sole proprietorship that is a CentralPay customer and processes payments on its own account when selling goods or services. May be functionally linked to a Technical Partner or Integration Partner. Has a Merchant Profile of the type `STANDARD`.
Partner Merchant	A legal entity that is a CentralPay customer, has a Merchant Profile, and may fall under one of the following models: • Technical Partner: operates a shared solution (e.g., marketplace, SaaS platform) and has one or more Points of Sale (POS) open in its name, to which standard Merchants can be linked. Has a Merchant Profile of type `TECHNIQUE`. • Integration Partner: provides technical support, via access delegated by standard merchants, to facilitate integration and day-to-day operations (without sharing POSes under the partner’s name). Has a Merchant Profile of the type `INTEGRATEUR` (if applicable). A Partner Merchant may earn commissions (depending on the model) and/or be registered as a MOBSP to assist merchants during onboarding.
Intermediary Merchant	A legal entity that is a customer of CentralPay, acting on behalf of third-party accounts, under one of the following regulatory statuses: • PSP Agent: A Payment Service Provider (PSP) agent of CentralPay, registered with the ACPR (Bank of France) and authorized to act in the name and on behalf of CentralPay within a contractually defined scope (e.g., debit/credit transactions and transfers on behalf of third-party accounts). Has a Merchant Profile of the type `AGENT`. • EMD: Electronic Money Distributor registered/declared by CentralPay with the ACPR (Bank of France) for a project involving the issuance, distribution, and exchange of electronic money (CUSTOM currencies). Has a Merchant Profile of type `DME`.
Sub-merchant / Participant	A legal entity or individual who is a customer of a CentralPay Intermediary Merchant (PSP Agent or EMD). • Sub-merchant: acts to sell products or services, for an LMNP business, • Participant: acts for non-commercial purposes (crowdfunding, personal wallet, collective projects, etc.). Has a specific Merchant Profile `BASIC`, with a limited scope of functionality.
Customer	A natural or legal person who pays or issues a payment order to a CentralPay Merchant (may also be referred to as the payee, payer, or debtor). May or may not have a Customer Profile (`Customer`). Note: In CentralPay’s regulatory or contractual documents, the term “Customer” may refer to the Merchant itself, depending on the context defined in the document.
Customer Profile	Represents a customer registered by a Merchant on the CentralPay platform. It contains: • the customer’s personal information: last name, first name, email, phone number, company name, etc. • the customer’s payment methods: cards, SEPA direct debits, IBAN, Bank Accounts, etc. • the customer’s activities: payment requests, payment history, etc.. The Customer Profile corresponds to the API object `Customer`.
BO User Profiles	Individuals with access to the CentralPay Merchant Portal to view or manage one or more Merchant Profiles. • Type `Legal`: the Merchant’s legal representative. • Type `Natural`: other authorized user (finance, support, development, etc.). The BO User Profile corresponds to the API entity `BO_user`.
API User Profiles	An entity created via the CentralPay platform that identifies the user (person or system) making API calls on a Merchant Profile. Enables the tracking of actions and the management of authorizations. The API User Profile corresponds to the API entity `api_user`.
Point of Sale (POS)	Representation of a website, a brick-and-mortar store, or a sales team. They enable the segmentation of CentralPay Merchant Profile operations for the following purposes: • Features: to configure different settings for each Point of Sale (POS) (customer notifications, internal notifications, sender name for confirmation emails, logo displayed on the checkout page, etc.) • Administrative: to restrict the rights to view or edit your BO User Profiles to certain Points of Sale (POS) • Accountants: to filter transactions by Point of Sale (POS) in the Merchant Portal or in data exports The Point of Sale (POS) corresponds to the API object `PointOfSale`.

2. Types of Accounts

Label	Description
Payment Account	An account opened in CentralPay’s books in a Merchant’s name. This account is used exclusively for payment transactions (collecting payments in ISO currencies, performing Payouts to a Bank Account, etc.). It is represented by the ` `Wallet` ` object of type ` `PS` ` in the CentralPay API.
Electronic Money Account	An account opened in CentralPay’s books in the name of a Merchant. This account is used exclusively for the storage and exchange of Electronic money within the distributor’s network (CUSTOM currencies). It is represented by the ` `Wallet` ` object of type ` `EM` ` in the CentralPay API.
Commission Account	A secondary Payment Account used to segregate commission flows and/or certain fee deductions (depending on the model). Under the Partner/Agent models, this account can receive commissions allocated to transactions by affiliated/participating merchants, in accordance with the applicable contractual rules. It is represented by the object ` `Wallet` ` of type ` `CM` ` in the CentralPay API.
Reserve Account	A secondary Payment Account used to set aside CentralPay reserve funds (account balance, collateral, or Rolling reserve). It is not authorized to make Payouts. It is represented by the ` `Wallet` ` object of type ` `RS` ` in the CentralPay API.
“Agent” Collection Account	A Payment Account opened in CentralPay’s books in the name of an Agent. It is used to receive funds related to transactions initiated through the Agent model, prior to their allocation or transfer to the Payment Accounts of Participant Merchants. It is not authorized to make payouts. It is represented by the ` `Wallet` ` object of type ` `CL` ` in the CentralPay API.
CentralPay Technical Partner Account	The Technical Partner Account refers to an internal, temporary mechanism used by CentralPay to receive, identify, and temporarily process funds related to a payment transaction, with a view to transferring them to the final Beneficiary. It is not a Payment Account opened for a customer, is not made available to any third party, and does not confer any right of disposal. Depending on the technical implementation, this mechanism may be implemented using internal objects (e.g., `Wallet` of type `TR`) used exclusively by CentralPay for operational processing.

3. The names of objects or operations

Label	Description
CentralPay Fees	All fees owed to CentralPay, deducted from the corresponding transactions, debited from a dedicated Commission Account, or billed at the end of the month (depending on the applicable contractual terms).
ISO Currencies	Standard currencies in accordance with ISO 4217 (e.g., EUR, USD, CHF, GBP…)
CUSTOM Currency	Electronic money created for a CentralPay EMD. The value of the CUSTOM currency is always pegged to that of an ISO currency (e.g., EUR).
Technical Instruction	Data or events for strictly technical and commercial purposes transmitted to CentralPay (e.g., order references, shopping cart, commission, logistics events). A Technical Instruction is not a payment order and does not trigger any automatic financial action: CentralPay retains sole discretion over the processing and, where applicable, the release of funds.
Release date	A deferred availability date that CentralPay may apply to make funds available to a Beneficiary (e.g., after delivery/shipment), in accordance with applicable risk policies and rules. It may be determined based on submitted commercial information, without constituting a payment instruction.
Bank Account	External Bank Account linked to: • a Merchant Profile for making outgoing Payouts (`payout`) • or a Customer Profile for making SEPA Direct Debits or outgoing Payouts. It is represented by the ` `BankAccount` ` object in the CentralPay API.
Outgoing payment	Outgoing bank transfer from a CentralPay account to an external Bank Account. Can be made via SEPA or SWIFT. It is represented by the ” `Payout` ” object in the CentralPay API.
Card Authorization	An operation to check the availability of funds on a credit card, followed by a hold in anticipation of a Card Transaction (max. 7 days). It is represented by the ` `Transaction` ` object in the CentralPay API.
Card Transaction	A debit transaction from a bank card, credited to a CentralPay account. It is represented by the ` `Transaction` ` object in the CentralPay API.
SCT Transaction	Operation to receive a SEPA or SWIFT bank transfer credited to a CentralPay account. It is represented by the ” `sctTransaction` ” object in the CentralPay API.
SDD Transaction	A transaction that debits a Bank Account and credits a CentralPay account. It is represented by the ` `sddTransaction` ` object in the CentralPay API.

CONTENTS