• 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

Simulating different use cases in a test environment

The test environment enables you to force shifting an enrollment request and its KYC to the status of your choice, while respecting the overall process. For this, simply use the description field of these to objects (registration or kyc), to indicate the expected status. The object will take this status as soon as possible.

For example:
  • You would like to test the expiration of a document.

    In this case, mention "EXPIRED" (case insensitive) in the description of the document in question. The document will first take the PENDING status before taking the EXPIRED status upon the first synchronization.

  • You would like to simulate an enrollment request rejection.
    1. Create a registration containing "REJECTED" (case insensitive) in your description.
    2. Specify the mandatory documents and submit the request.

      Th enrollment request will take the status of the first synchronization.

    You can then add new documents, modify the enrollment request information - even change the description to define a new target status, which it will take as soon as possible, etc.

 

In the test environment, if the enrollment request status remains non-final for more than 7 days, it automatically changes to CLOSED.

Jobs
Legal
GDPR
25.18-1.11