MyazaTrust

Environments
Build with

Myaza Trust has isolated environments. Both share the same base URL — the environment is selected by the API key prefix, not the host. There is no environment query parameter or header.

EnvironmentBase URLKey prefix
Sandboxhttps://trust.myaza.co/api/kycpk_test_
Productionhttps://trust.myaza.co/api/kycpk_live_

Data does not cross environments: keys, verifications, webhook endpoints, and configuration are all scoped to one environment.

Sandbox
Build with

Use sandbox to build and test your integration. It exercises the same API surface and webhook delivery as production. Send your pk_test_ keys to https://trust.myaza.co/api/kyc — the same base URL as production.

Production
Build with

Production runs real verifications against live government databases and bills your wallet.

Production access requires an approved business

Before your pk_live_ keys can run verifications, your organization's business profile (KYB) must be approved by Myaza. Until then, production verify and upload requests are rejected:

json
{
  "error": "business_not_approved",
  "message": "Your business must be approved by Myaza before using production verification services."
}

Complete and submit your business profile under Onboarding in the dashboard, then wait for approval. Sandbox is unaffected and remains available throughout.

Billing

Each completed production verification deducts from your organization's wallet at the price configured for that country and ID type. If the wallet has insufficient credit, the verification is recorded and marked failed with an insufficient-credits reason (it still fires a verification.failed webhook) rather than being silently dropped. Top up and set low-balance thresholds under Billing.

Switching environments in the dashboard
Build with

The dashboard header has an environment switcher (Sandbox / Production). It controls which environment's data you see — including which keys you create — without changing the dashboard URL.

Checklist for going live
Build with

  1. Your business profile is approved for production.
  2. You created pk_live_ keys and deployed them as secrets to your backend.
  3. You registered production webhook endpoints and verified signatures.
  4. Your wallet is funded and a low-balance threshold is set.
  5. You swapped your pk_test_/sk_test_ keys for pk_live_/sk_live_ keys — the base URL (https://trust.myaza.co/api/kyc) stays the same.