How to confirm address evidence with Myaza Trust
Collect a map pin and the address details your team needs. Address Intelligence corroborates available evidence and explains its strength; a customer’s typed address remains their claim.
Charles Archibong, Co-founder
· 4 min read
Key takeaways
- Dragging a pin works without forcing location permission.
- Missing required details give a usable recovery path.
- Claimed, corroborated and attested evidence remain distinct.
- A new session uses the published address settings.
Collect a map pin and the address details your team needs. Address Intelligence corroborates available evidence and explains its strength; a customer’s typed address remains their claim.
Before you begin
Supported address capture and corroboration
Required customer consent and location 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: Choose onboarding or an address-only flow
Open Configuration → Workflows. Use an onboarding workflow if you also need identity capture, or the Address-only verification template for customers verified elsewhere. Address-only capture still needs the intended customer reference. Choose Sandbox first. For a business workflow, the pin represents business premises and uses the relevant registry evidence.
Dashboard example: Choose onboarding or an address-only flow
Step 2: Enable Address Intelligence
Turn on Address Intelligence in the step list and open Setup. Decide whether Require pin is needed. If it is off, the applicant may skip the pin; if it is on, a missing pin is refused. Review Confirm presence at the pin for a one-time GPS observation. Denied location permission can reduce that evidence without inventing an at-address result.
Dashboard example: Enable Address Intelligence
Step 3: Choose practical address requirements
Set Property fields, Entrance photo, Directions and individual address fields to the appropriate Optional, Required or Hidden state. Require only facts the person can genuinely supply. An unnumbered building cannot supply a reliable house number. Street View is a separate capture from an applicant photo and may have no coverage; its absence cannot prove the address false.
Dashboard example: Choose practical address requirements
Step 4: Set a review policy for address evidence
Use the Rules tab or decision graph to route the address findings you need. Read the recorded tier and corroboration status instead of treating any pin as independently verified. attested describes a device fix near the pin; corroborated describes locality agreement with independent evidence. A missing comparison is unknown. Shared households and shared map cells are context, not proof of duplicate identity.
Integration reference: Assurance tiers
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: Review the captured address and evidence
Open the verification result and inspect data.addressIntel, the map pin, captured details and corroboration. Keep the applicant’s claimed fields distinct from derived and recorded evidence. Read the final workflow status before applying your account action. Use the navigation packet for delivery or field visits where authorised. A one-time GPS observation is different from a multi-day presence watch.
Integration reference: What comes back
Get more from the capability
Use field-level requirements rather than requiring every property detail for every market.
Use held address evidence with its provenance when a returning customer confirms a pin.
Add multi-day presence only after the native app’s reporting and consent journey are implemented. Enabling that switch alone is insufficient.
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.
Dragging a pin works without forcing location permission.
Missing required details give a usable recovery path.
Claimed, corroborated and attested evidence remain distinct.
A new session uses the published address settings.
Troubleshooting
The person cannot continue
Inspect missing required fields. Correct an unrealistic requirement rather than fabricating a house number.
The tier is not attested
Check whether a usable device fix was taken near the pin. Permission refusal is not a false address.
No watch starts from a hosted link
Multi-day presence requires the native mobile reporting path, not browser capture.
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.
