How to understand customer risk with Myaza Trust
Read customer risk with its evidence and assessment basis. Customer risk helps explain a customer’s recorded state; it is different from the risk decision for a specific payment.
Charles Archibong, Co-founder
· 3 min read
Key takeaways
- A real zero differs from unassessed or incomplete evidence.
- History pins an exact snapshot.
- Expired current data disappears until refresh succeeds.
- A workspace switch discards earlier customer evidence.
- Reads create no checks, charges or execution authority.
Read customer risk with its evidence and assessment basis. Customer risk helps explain a customer’s recorded state; it is different from the risk decision for a specific payment.
Before you begin
The relevant customer-risk read capability enabled
Authorised typed customer access
Evidence basis and freshness available
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: Confirm that customer-risk reads are available
This read capability is a Shadow preview and is disabled by default. Myaza must enable it for the environment. Current scores also require reviewed configuration and qualified evidence. Check your organisation’s product access and individual- or business-read permissions. An API key or a legacy risk tier does not activate this preview or supply a live decision policy.
Integration reference: Availability
Step 2: Choose Current or As assessed
Open Customer assessments and choose the basis deliberately. Current asks for qualified current evidence. As assessed reads retained historical assessment evidence. When viewing one customer, use the corresponding Risk evidence view and selected snapshot. Do not switch to an older score and label it Current if the current read is unavailable.
Integration reference: Choose a read
Step 3: Read one customer from your backend
Use GET /api/v1/risk-intelligence/customers/{entityId}/risk with the environment’s secret key. Use the history endpoint for previous assessments and the snapshots endpoint for one exact historical assessment. The key supplies organisation and environment. Request the customer type you are permitted to access; inaccessible or unknown customers must not become a neutral score.
Integration reference: Choose a read
Step 4: Check state, score and coverage together
A current number needs the response’s Current assessment state. A null score is not zero; a valid zero is Low. The documented bands are Low 0–24, Medium 25–49, High 50–79 and Critical 80–100. This index is not a probability of fraud. Pending, stale, incomplete or unavailable evidence must retain its state instead of borrowing a retained number.
Integration reference: Display the result safely
Step 5: Trace why the selected score exists
Use Why this score, Connections and History for the same assessment. Inspect retained factors and coverage. Supporting context adds no points, and a minimum-risk adjustment is model evidence rather than another paid check. Paging the map changes visible evidence, not the recorded score. A score-lineage map is not a live network of customer or wallet owners.
Integration reference: Read customer risk
Step 6: Refresh combined customer views correctly
For current cohort filtering, use the documented basis=CURRENT and typed subject filters. Include monitoring only through the supported combined read. Refresh rows and totals together at the returned transition window; do not join independently paginated lists. When the validity window expires, remove the current numbers until refresh succeeds. These reads do not buy checks, publish rules or authorise payments.
Integration reference: Filter risk and monitoring together
Get more from the capability
Use exact snapshot links for an audit question so historical evidence cannot silently change to today’s evidence.
Keep coverage visible next to the score. A complete Low result and an incomplete assessment require different interpretation.
Treat connections as explanation for the selected assessment and avoid adding context into the score twice.
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 real zero differs from unassessed or incomplete evidence.
History pins an exact snapshot.
Expired current data disappears until refresh succeeds.
A workspace switch discards earlier customer evidence.
Reads create no checks, charges or execution authority.
Troubleshooting
The preview is unavailable
Check environment activation, current configuration and permissions. Do not fall back to a legacy tier as current proof.
The score is missing
Read the assessment state and coverage. Missing does not mean zero or Low.
Risk and monitoring totals disagree
Use the supported single combined population rather than intersecting separately paginated results.
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.
