On this page
Myaza Trust combines identity verification with Risk Intelligence. Use identity verification to establish who a person or business is. Use Risk Intelligence to screen customers, decide on transactions and account activity, keep customers under continuous review, apply Travel Rule controls and manage investigations.
Choose the shortest path for the job:
- User verification for a hosted or embedded individual flow.
- Business verification for a KYB workflow and company link.
- Risk Intelligence quickstart for a server-side transaction decision.
- On-Demand Wallet Screening for an explicit wallet check.
How the integration works
Identity verification is asynchronous. You submit a verification request and receive a verification ID immediately; the result arrives later through a webhook or status read.
You can drive a verification two ways: pass the configuration in code (country, ID types, steps), or build the flow once in the dashboard as a workflow and reference it by id, adding extra checks and an approve / decline / review decision without changing your code. Every flow runs in one of our SDKs or as a shareable hosted link.
Risk activity and transaction decisions are synchronous. The response tells your backend whether to allow, review or block the action. Webhooks are optional notifications for those decisions and are the normal delivery path for ongoing monitoring changes.
Base URL
| Product | Sandbox | Production |
|---|---|---|
| Identity verification | https://trust.myaza.app/api/kyc | https://trust.myaza.app/api/kyc |
| Risk Intelligence | https://sandbox.trust.myaza.app/api/v1 | https://trust.myaza.app/api/v1 |
The official SDK chooses the correct host. API keys, webhook endpoints and resources stay isolated by environment. See Environments.
Conventions
- All request and response bodies are JSON, except media upload which is
multipart/form-data. - Timestamps are ISO 8601 strings in UTC (e.g.
2026-04-27T12:00:00.000Z). - IDs are opaque strings; do not parse them.
- Statuses in responses are lower-case (
pending,verified,failed,not_found,error).
Next steps
- User verification or Business verification: launch a workflow and receive the result.
- Verification API quickstart: a full individual verification through HTTP.
- Risk Intelligence quickstart: a first transaction decision.
- Authentication: create and use API keys.
- Create a verification: the core endpoint in detail.
- Workflows: configure a flow visually and reuse it by id or hosted link.