How to confirm a live person with Myaza Trust
Liveness helps establish that a real person is in front of the camera. Enable it in the workflow customers use, choose a method, and route captures your policy cannot accept.
Charles Archibong, Co-founder
· 4 min read
Key takeaways
- Permission refusal has a usable recovery path.
- Missing or unreadable recordings reach the configured action.
- Submission completion alone does not grant access.
- The intended policy works on representative supported devices.
Liveness helps establish that a real person is in front of the camera. Enable it in the workflow customers use, choose a method, and route captures your policy cannot accept.
Before you begin
Camera permission and a supported device
A workflow with an available liveness method
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: Open the customer capture workflow
Choose your organisation and Sandbox, then open Configuration → Workflows. Open the individual workflow used in your app. Check the ID at the top. The presence step is part of capture, so a change to an unused workflow cannot affect customers. Review camera permissions and the devices your customers use before choosing a method.
Dashboard example: Open the customer capture workflow
Step 2: Enable Presence Intelligence
Turn on Presence Intelligence in the left step list and select it. Open Setup in the middle panel. Keep the selfie step available in the journey. A selfie alone is a photo; the selected liveness method supplies the presence check. The preview shows the customer experience, but it does not run the live engine.
Dashboard example: Enable Presence Intelligence
Step 3: Choose the liveness method
Choose an available method: 3D Active Motion, 3D Flash Check, Dual Check or Passive Liveness. The panel describes the action and estimated time. Choose based on your risk and accessibility requirements, then inspect the preview. Keep Voice guidance when spoken instructions help customers, and review Bright screen for low-light capture. Test representative real devices before choosing Production defaults.
Dashboard example: Choose the liveness method
Step 4: Choose the missing-recording action
Open Rules and inspect the handling for a missing or unreadable liveness recording. Review needs enabled decisioning and a rule that routes the finding to your team. Decline asks for another capture according to your policy. A recording that never arrived is not a proven spoof; it is evidence your server could not re-check. Check other rules and their order before publishing.
Integration reference: When the liveness recording does not arrive
Step 5: 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 6: 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 7: 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
Keep liveness and 1:1 face comparison separate in your result handling. Passing one does not establish the other.
Use face re-authentication for a named returning customer. Use full verification for onboarding when identity checks are required.
Review completion and retry rates across low-end phones, browsers and poor networks. Adjust the capture journey using evidence, not the preview alone.
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.
Permission refusal has a usable recovery path.
Missing or unreadable recordings reach the configured action.
Submission completion alone does not grant access.
The intended policy works on representative supported devices.
Troubleshooting
Camera access was denied
Give the customer a clear permission-recovery path. Do not silently skip a required selfie.
The recording is missing
Use the recorded reason and your Review or Decline policy. Ask for a supported browser or another phone where appropriate.
A test passed instantly
Sandbox outcomes are simulated. They validate your handling, not real-world anti-spoof performance.
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.
