Evaluation environment — TrustID is in a supervised test phase: every verification rail is simulated, and accounts, credits, API keys and history are rotated periodically without notice.

User guide

What TrustID does today, checked against the running code. Every rail on this platform is simulated while it is under evaluation — see the FAQ for exactly what that means.

1. Account & credits

  1. Create an account with an email address and a password of at least 12 characters.
  2. A new account starts with 10 free credits. One credit is consumed per live verification; sandbox verifications cost nothing.
  3. Your credit balance is on the dashboard, alongside recent verifications and your API keys.

2. Try it in the sandbox

The sandbox demo on the home page runs a verification end to end and needs no account. From the API, a key created as a sandbox key, or any request with "mode": "sandbox", is free and never touches your credits. Use it to build and test; switch to production mode when you are ready to be charged per check.

3. Run a verification from the dashboard

  1. Open Dashboard → Verify.
  2. Choose the check, enter the subject's details, and choose sandbox or production mode.
  3. The result is shown immediately and recorded in your ledger. A production check deducts one credit; if your balance is zero the check is refused rather than run.

4. The checks available

CheckReport typeField the simulator reads
South African IDsa_idid_number
Bank account (AVS)bankaccount_number
Facial liveness & matchfaceno input used — result is simulated
Vehicle & licencevehicleplate
AML & PEP screeningamlno input used — result is simulated

These five are the report types the API accepts today. The services page also describes a CIPC company lookup; that check is planned and is not yet callable.

5. Use the API

  1. Open Dashboard → API keys and create a key. Choose sandbox for development. The key is shown once; keys are stored as hashes and cannot be recovered, only replaced.
  2. Send it as a bearer token: Authorization: Bearer <key>.
  3. POST /v1/verify with a JSON body naming the report type and the subject's details. Poll GET /api/v1/verify/status/<id> if a result is pending.
  4. Usage and remaining credits: GET /v1/usage. Your history: GET /v1/verifications.

The full request and response shapes are in the API reference.

6. Buying credits

Buy from Dashboard → Billing. Purchases are listed under Purchase history. During the evaluation period card payments are not connected — see the FAQ — so the buy flow records the intent without charging a card.

7. The verification ledger

Dashboard → Verifications lists every check your account has run — type, mode, outcome and time. It is your audit record of what was checked and when.