How to verify a new customer with Myaza Trust
Verify a new customer with a published individual workflow. The customer completes the document and selfie journey; your backend receives the outcome and applies your onboarding policy.
Charles Archibong, Co-founder
· 4 min read
Key takeaways
- A supported passing test ID reaches your intended onboarding outcome.
- A mismatch and an unavailable-check result reach different recovery paths.
- Review stays pending until the reviewer decides.
- A repeated notification does not create another customer.
Verify a new customer with a published individual workflow. The customer completes the document and selfie journey; your backend receives the outcome and applies your onboarding policy.
Before you begin
Supported country and identity document or number
Customer consent
Published workflow for customer capture
Use a team member with permission for this control. Check the organisation and environment before changing a setting. Review the current price before a paid check or ongoing enrolment. Screenshots show an example workspace or the public integration reference; they do not show a real customer or a completed paid check.
Set up and use the capability
Step 1: Choose the organisation and Sandbox
Open the dashboard and check the workspace selector. Choose your organisation and Sandbox, then open Configuration → Workflows. Start with an individual verification workflow; business workflows collect a different subject. If you already run onboarding, open the workflow your integration actually uses. Check its ID before editing. Missing workflow access needs the appropriate role from your organisation owner.
Dashboard example: Choose the organisation and Sandbox
Step 2: Choose the countries and accepted IDs
In the editor, select ID Verification → Countries. Select the countries you serve and the document or number-based ID types you accept. Review the checks available for each country and ID. Choose requirements your customers can fulfil. A passport document check, government-database lookup and face comparison are different evidence. Do not assume selecting a country enables every ID or every check.
Dashboard example: Choose the countries and accepted IDs
Step 3: Keep selfie capture and liveness deliberate
Select Presence Intelligence → Setup and keep the step enabled. Choose the available liveness method for your journey. A live-person check and a comparison with the ID photo answer different questions. Keep facial matching enabled where your policy requires proof that the applicant is the ID holder. Inspect the customer preview for the journey and price, rather than adding every optional check without a reason.
Dashboard example: Keep selfie capture and liveness deliberate
Step 4: Save and publish the workflow
Wait for Saved in the editor. Select Publish, or Publish changes for an existing workflow. In the publication review, check the target environment, workflow ID, price and readiness warnings. Resolve blocking issues, then confirm Publish version. A saved draft is not the version customers use. New sessions use the new published snapshot; sessions already created retain their original version.
Dashboard example: Save and publish the workflow
Step 5: Connect the published workflow to your app
Copy the workflow ID. Give that ID to your supported Web, React Native or Flutter SDK, with a publishable key from the same organisation and environment and a stable customer reference. Alternatively, create a customer-bound hosted session on your backend with POST /api/kyc/sessions, using a secret key. Return the session URL only to the intended customer. A camera preview does not run a verification or prove your backend handles the result.
Integration reference: Request
Step 6: Read the final outcome on your backend
After capture, store the verification ID against your own customer reference. Follow status updates or retrieve current status. Read status for the outcome and checkStatus, reason and reasonCode for the explanation. When a workflow has decision rules, a checks-completed event can arrive before the final workflow decision. Keep processing and human-review results pending; do not approve an account merely because the customer finished the camera screens.
Integration reference: Status and checkStatus
Get more from the capability
Use different workflows when countries or products need genuinely different requirements. Keep their IDs recorded in your application configuration.
Add contact verification before expensive checks when you need proof of contact access. Add screening only when it belongs in your onboarding policy.
Use stable customer references across verification and subsequent activity. Store the final decision alongside the check evidence so an exception remains explainable.
Test before relying on it
Run the supported Sandbox or simulator scenarios for this product. Where a tool is Production only, check access and scope first, then use only a permitted, deliberately reviewed Production test. A documentation screenshot or a successful page load is not an end-to-end integration test.
A supported passing test ID reaches your intended onboarding outcome.
A mismatch and an unavailable-check result reach different recovery paths.
Review stays pending until the reviewer decides.
A repeated notification does not create another customer.
Troubleshooting
The old journey still opens
Check the key environment, workflow ID and published version. Start a new session after publishing.
Checks passed but the customer is waiting
Read the current status and waiting requirements. The decision graph or a reviewer may still need to decide.
An ID was not found
Read the reason code and correct the input or ask for another supported ID. Do not replace the result with approval.
Open the setup and integration references
Read the integration reference
Back to Solutions. Choose the capability you want to activate, then follow its own guide.
Sources
Charles Archibong
Co-founder
Charles Archibong co-founded Myaza Trust. He writes about identity verification, financial technology, and the practical work of building trusted digital services.
