How to strengthen identity evidence with Myaza Trust
NFC verification adds authenticated chip evidence from a supported passport or identity card. Set it up in a mobile capture workflow and understand when the result can, and cannot, raise assurance.
Charles Archibong, Co-founder
· 4 min read
Key takeaways
- A supported native path offers chip capture.
- A phone without NFC still reaches the documented fallback.
- Inconclusive and not-authentic results remain distinct.
- Your backend records the achieved assurance rather than assuming chip assurance.
NFC verification adds authenticated chip evidence from a supported passport or identity card. Set it up in a mobile capture workflow and understand when the result can, and cannot, raise assurance.
Before you begin
Supported chip document and mobile SDK for NFC
Required documents and device permissions
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: Check your capture platform
Use React Native or Flutter on an NFC-capable phone. Passport-chip reading is not available in the Web SDK or a browser-hosted journey. Open the current NFC documentation and your SDK setup instructions. Check the live configuration for the document’s supportsNfc value; chip availability depends on the document and the trusted issuing certificate, not merely on a country name.
Integration reference: Supported documents
Step 2: Choose supported IDs in the workflow
Open Configuration → Workflows in Sandbox, then open your individual workflow. Select ID Verification → Countries and enable the supported document types you intend to offer. Document scanning must precede the chip step because the scan supplies the details used to unlock the chip. Do not offer NFC as a substitute for the initial document capture.
Dashboard example: Choose supported IDs in the workflow
Step 3: Enable NFC Chip Verification
Turn on NFC Chip Verification in the step list, then open its Countries and Setup controls. Check whether the chosen IDs can actually offer a chip read. Configure the available skip and facial-comparison options deliberately. If the panel says none of the offered IDs can be checked, correct the supported ID selection before expecting the chip screen.
Dashboard example: Enable NFC Chip Verification
Step 4: Review the chip decision rules
Use the step’s Rules tab and decisioning for the assurance you require. Distinguish verified chip data from proof that the original chip is present. An inconclusive or unreadable chip falls back to document checks; it is not automatically a tampered document. A proven authenticity failure has its own failure result. Decide how your policy handles an unknown signer-cancellation status.
Integration reference: Behaviour and availability
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 evidence behind assurance
Inspect data.nfc, the verification assurance level and the final status on your backend. Check status, chipAuthentic, dataMatch and cloneCheck. active_auth and face_bound describe different ways a copied chip was ruled out. A valid signature from an untrusted issuer cannot establish chip authenticity. Keep missing optional data groups separate from failure. Read current results before applying your customer action.
Integration reference: Where the results surface
Get more from the capability
Use the native SDK’s current configuration instead of maintaining your own list of chip-capable countries.
Keep the document, chip and selfie evidence available together for review. Do not claim fingerprints or iris extraction from a commercial passport read.
Test chipless, unsupported, unreadable and inconclusive paths as well as authenticated chips. The fallback is part of the customer journey.
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 native path offers chip capture.
A phone without NFC still reaches the documented fallback.
Inconclusive and not-authentic results remain distinct.
Your backend records the achieved assurance rather than assuming chip assurance.
Troubleshooting
No chip screen appears
Check the native SDK, phone NFC support, selected ID and current supportsNfc configuration.
Chip data is verified but assurance is lower
Check cloneCheck and the other verification evidence. Genuine chip data alone does not always establish the original chip.
An optional group is absent
Many issuers omit optional groups. Read the chip result rather than treating absence as tampering.
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.
