On this page
Understand the contract before integrating
The local simulator explores fixed creation and result scenarios. It runs in the browser with synthetic data. It does not request an identity number, document, selfie, API key or webhook secret, and it does not perform identity verification.
Use it to align product and engineering on what your system should do when a journey stays pending, is approved, is rejected, expires or requires manual review. Observe the difference between status and decision instead of releasing a process based on an intermediate stage.
An exploration path
- Start with creation and identify the synthetic
transaction_id. - Select available results and compare their states.
- Map every scenario to a screen or action in your application.
- Read why duplicates and delayed events require reconciliation.
Record which decisions need a person and which can continue automatically under your policy. The goal is to turn a technical payload into an understandable operational rule.
What your integration still needs to test
The simulator does not certify credentials, networking, message delivery, biometrics or persistence. Those behaviors require validation in an enabled environment and your application’s infrastructure. Do not submit real data to extend the exercise.
Continue with the quickstart, validate your webhook consumer and complete the go-live checklist.