• France
status page
Demo shops
assistance
FAQContact support
Search
Categories
Tags
Europe (English)
France
Spain
Europe (English)
India
Homepage
Use cases
Create a payment
Create an installment payment
Create a multi-card (split) payment
Create a payment by Alias (Token)
Create a payment link
Create a recurring payment
Manage subscriptions
Manage your transactions (refund, cancel...)
Analyze your reports
API docs
Embedded Form
REST API
Hosted payment
Mobile payment
File exchange
SDD mandates by REST API
Snippets
Payment methods
Plugins
Marketplace
Guides
Merchant Back Office
Back Office Expert
Functional guides

Understanding and following up on the evolution of the enrollment request

At this stage, our sales and compliance department validates the transmitted information and documents. If necessary, they may contact you for additional information.

 If you have defined webhooks for the object registration and the KYC, you will be notified of the processing stage of each document, and of the enrollment request.

If this is not the case, or if you are unsure whether a webhook has been received, you can still interrogate the corresponding resources and retrieve the latest status.

  • For the enrollment request:

    GET/registrations/{registration_uuid}registrations_read

  • For tracking the document statuses:

    GET/registrations/{registration_uuid}/documentsregistration_documents_list

If the information transmitted is valid, the documents will each successively take the status VALIDATED, then the status of the registration will change to SUCCEEDED.

However, it is possible that one of the transmitted documents is rejected (REJECTED) or marked as expired (EXPIRED).

 Reasons for rejection
If the document is set to REJECTED status, the reject_reason property guides you through the reasons for the rejection:
  • ILLEGIBLE: ineligible document;
  • INCOMPLETE: incomplete document;
  • INCONSISTENT: irrelevant document;
  • OTHER: other case.

If the rejection concerns one of the mandatory documents, the enrollment request status will return to CREATED. In this case, the request registration cycle must be restarted:
  1. submission of a new corrective document
  2. change of the enrollment request status AWAITING_SUBMISSION ;
  3. follow-up of the new submission

It is also possible that the enrollment request itself is:
  • provisionally rejected (FAILED);

    We recommend that you contact the sales department via our support team to find out why. the enrollment request status will return to CREATED as soon as you update it, and you can resume the request submission process.

  • definitively rejected (REJECTED).

    In this exceptional case, you can no longer can no longer modify the enrolment request in question.

Jobs
Legal
GDPR
25.18-1.11