How to screen a crypto wallet with Myaza Trust
Screen a saved crypto wallet and inspect the decision with its exposure evidence. Keep blockchain risk, address approval, signed control and transfer clearance separate.
Charles Archibong, Co-founder
· 3 min read
Key takeaways
- The selected network belongs to the actual wallet.
- Sandbox results remain labelled.
- Failed and completed decisions are distinct.
- An unchanged retry cannot create another charge.
- Risk-only Allow does not release funds.
Screen a saved crypto wallet and inspect the decision with its exposure evidence. Keep blockchain risk, address approval, signed control and transfer clearance separate.
Before you begin
Wallet address with explicit network context
An available screening provider and current price
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 crypto Address book
Choose the correct organisation and Sandbox. Open Risk Intelligence → Fraud Monitoring → Transactions → Crypto, then the Address book view. You need the supported crypto read access; screening actions require management access and available product access. Use the current network catalogue rather than guessing a chain from the appearance of an address.
Integration reference: Crypto operations
Step 2: Save the destination with its network context
Use the address-book add action and provide the permitted wallet address, selected network and label. Link the intended customer or provider only when your evidence supports that relationship. Check the address format and asset precision. A saved destination starts as a claimed record for review; it does not prove ownership and does not automatically run screening.
Integration reference: Crypto provider reviews and address book
Step 3: Open the saved wallet’s screening tool
Open the address details and select Screen address. Review the displayed current screening price and the available check. Keep the address and network unchanged for this run. If credit or provider access is missing, resolve that state before expecting a decision. Running, waiting for credit, failed and completed are different states; none should be replaced with a clear label.
Integration reference: Screen, edit or verify control
Step 4: Inspect the risk decision and exposure
Read the completed wallet result and its supporting exposure details. Where available, review sanctions exposure, category, direct versus indirect exposure and the recorded path distance. Use the actual returned evidence; the Solutions page’s 92/100 example is deterministic demonstration data, not a promised score. A low score does not establish legal ownership or permit a transfer on its own.
Integration reference: Types
Step 5: Integrate saved-address screening on your server
Use the documented POST /api/v1/crypto/addresses/{id}/screening action with a secret key, its required body and an Idempotency-Key. Read the current address and request schema before sending. Keep the original key and unchanged body after a timeout, and reconcile current state instead of starting another paid check blindly. Store the assessment reference against the saved address and network.
Integration reference: Screen, edit or verify control
Step 6: Use the result in your review and payment policy
Record the screening result with its checked time and apply the authorised decision to the intended action. Keep address approval and control proof separate: a passed screen does not approve the address for your team. Crypto funds release needs its separately qualified clearance and wallet-enforcement path. Keep pending, failed or unavailable checks on hold according to your policy.
Integration reference: Enforcing decisions in your app
Get more from the capability
Screen the actual sender for inbound crypto and recipient for outbound crypto when submitting a complete transaction.
Review direct and indirect exposure separately where the result supports that distinction.
Re-screen deliberately when freshness or changed evidence requires it, with the current price and a genuine new operation.
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 selected network belongs to the actual wallet.
Sandbox results remain labelled.
Failed and completed decisions are distinct.
An unchanged retry cannot create another charge.
Risk-only Allow does not release funds.
Troubleshooting
Screening is waiting for credit
Review the current rate and available credit; opening details does not complete a paid check.
No crypto provider was found
Discovery has different coverage from screening. Unknown discovery does not mean self-hosted.
Screening passed but transfer remains held
Check information requirements, approved routes, country review and current clearance separately.
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.
