How to review existing customer addresses with Myaza Trust
Review the address evidence already in your customer book. Upload a permitted CSV, inspect the quote and use the resulting grades to choose the right next capture or presence check.
Charles Archibong, Co-founder
· 3 min read
Key takeaways
- The quote matches the intended row count and choice.
- Previewed and ungraded rows remain distinct.
- Export retains the row-level grades.
- Recapture attaches to the intended existing customer.
- A pending job is not presented as a completed audit.
Review the address evidence already in your customer book. Upload a permitted CSV, inspect the quote and use the resulting grades to choose the right next capture or presence check.
Before you begin
An authorised customer book in the supported format
Available existing address evidence
Review the quote before running triage
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: Prepare the customer-address CSV
Create a UTF-8 CSV with an address column. Add customer_id, name and country where supported and known. Use the customer reference your organisation actually holds; preserve the original address text rather than inventing a structured house number. Review the current file and row limits in the upload requirements. Include only records your team is permitted to process.
Integration reference: Book triage
Step 2: Open Address checks in the right workspace
Select the organisation and environment, then open Risk Intelligence → Address checks. The retained route is address-triage. Choose Sample CSV to inspect the current format before using Upload addresses. Read access and upload-management access are separate. If uploading is unavailable, ask for the correct role rather than sending the book to another workspace.
Integration reference: Book triage
Step 3: Review the quote before choosing a run
After selecting the file, inspect the parsed row count, file issues and current quote. Choose the free first-row grading option when offered or the full-book option at its displayed amount. If the entire book fits the free sample, the interface offers that complete choice. Resolve insufficient credit or malformed columns before running a paid full-book job.
Integration reference: Book triage
Step 4: Wait for the job and inspect row coverage
Open the resulting run and monitor progress until its recorded result is ready. Distinguish graded rows from rows that remain ungraded after a preview. Review the distribution and each row’s actual grade. A pending or failed job is not a finished address audit, and a small preview cannot establish the quality of the unprocessed remainder.
Integration reference: Book triage
Step 5: Choose remediation from the recorded grade
corroborated means held evidence agrees at locality level. confirmable_in_app points to a short recapture journey for an existing customer relationship. needs_presence points to a presence-verification path. Use the run’s available remediation controls and the customer’s correct reference. A triage grade is a next-step recommendation; it does not independently prove residency or complete a new verification.
Integration reference: Address-only workflows (standalone, no identity step)
Step 6: Export and follow through on the next capture
Use the supported CSV export to preserve the row-level plan. Send an address-scoped session to the intended customer or add the relevant address step to their next workflow. Multi-day presence still needs the native app’s reporter and consent setup. Review later capture results against the original plan rather than treating the upload itself as proof that every gap is fixed.
Integration reference: Stability, re-attestation and the certificate
Get more from the capability
Run an offered preview before committing to a large paid run, then keep the ungraded population explicit.
Use stable customer IDs so remedial capture lands on the right existing record.
Prioritise the grade-specific next step instead of forcing every customer through an unnecessary full KYC 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.
The quote matches the intended row count and choice.
Previewed and ungraded rows remain distinct.
Export retains the row-level grades.
Recapture attaches to the intended existing customer.
A pending job is not presented as a completed audit.
Troubleshooting
The CSV will not parse
Compare its columns and encoding with Sample CSV and inspect the returned file issues.
The full run is disabled
Check the quote and balance. A free preview may still be available.
The customer needs another capture
Use an address-only session with their external reference; triage cannot invent missing evidence.
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.
