What can I test before paying for production checks?

Short answer

Start in Sandbox with the documented inputs for the product you want to try. You can rehearse the applicant journey, inspect a result and test delivery of updates before sending production traffic. Free testing depends on the product and fixture; it is not a monthly allowance of free production checks.

Plan a useful rehearsal

1. Choose the customer journey: individual identity verification, business verification, screening or another Risk Intelligence flow.
2. Read that product’s Sandbox guide and use its documented test IDs or deterministic scenarios.
3. Keep the workflow, key, console environment and webhook endpoint in Sandbox throughout the test.
4. Exercise approval, a negative finding, review and a service error. Check what your own application shows for each outcome.
5. Confirm that your backend receives the expected reference and signed updates. An SDK submission callback is not a final approval.

Understand the cost boundary

Documented identity test IDs do not use paid verification credit. Wallet Sandbox screening uses simulated exposures. For other Risk Intelligence requests, use the documented scenario for a deterministic free test: an ordinary Sandbox request without one can use configured Sandbox pricing. Check the billing guide for the product you are calling.

Sandbox results demonstrate your integration and rules. They do not prove that a real identity was verified, that a live company registry was queried, or that a real wallet is clear. Keep test records separate from evidence used for customer decisions.

Before going live

Complete the business approval requirements, review your account’s current rates and create the appropriate Production keys. Repeat the configuration review for Production; do not assume your Sandbox lists and settings have been copied.

Related guides

• Sandbox and test IDs
• Billing
• Going live