in just a few minutes
for businesses and individuals
natively integrated
The user onboarding journey,
step by step
Creation of user profile
The form is pre-configured according to the type of entity. Only the necessary information is requested (identity, email, telephone, company name, SIREN number, country of residence…).
Collection of supporting documents
The platform specifies the required documents and supporting evidence (format, front and back, validity). Each document is checked upon import.
E-signature of the Terms and Conditions
Your terms and conditions are presented and signed electronically in the same process. The signature is legally valid and archived on the CentralPay platform.
Protocole de vérification d’identité (KYC / KYB)
The system combines automated analysis (performed by a partner) and supervision by the CentralPay teams. The result is communicated within a maximum of 48 business hours.
Two ways to deploy the onboarding portal
Hosted portal
CentralPay hosts and maintains the onboarding process for you. You only need to share access with your third party.
Immediate deployment
A URL dedicated to your brand
No technical resources required
Native integration
Embed the portal natively in your platform, for an experience entirely tailored to your needs.
A route 100% integrated into your environment
API integration
Full documentation and sandbox available
Control of the onboarding process,
at every moment
Real-time case status
Track progress : documents received, current stage, identified obstacles…
Automatic communication
Trigger automatic emails in case of incomplete file or expired document.
Manual piloting available
Manage everything from your central dashboard: request additional documents, suspend onboarding…
FAQs
Questions about third-party onboarding with CentralPay ?
On average, less than 10 minutes for a complete file. Actual time depends on document availability. The process resumes where the third party left off if they interrupt the session.
Yes. The list of required documents is configurable by type of third party (SAS, SARL, sole trader, etc.). You define the rules in your administration area, without any development required.
An event is triggered with the reason for the rejection. Your system can initiate a manual processing workflow or request additional documentation.