Skip to content

From the team · Page 3

Inside Myaza Trust.

  • Myaza Trust editorial illustration: Put the address on the map.

    Identity Verification

    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.

  • Myaza Trust editorial illustration: Ask clearly. Keep the answer.

    Identity Verification

    How to collect customer declarations with Myaza Trust

    Collect the declarations your policy needs, such as source of funds or expected activity. A questionnaire gives you recorded customer answers; it does not independently verify those answers.

  • Myaza Trust editorial illustration: A contact you can actually reach.

    Identity Verification

    How to confirm contact details with Myaza Trust

    Verify contact access with an email or phone code. Use the workflow step for capture journeys, or the standalone API when your app needs a separate contact check.

  • Myaza Trust editorial illustration: Recognise the risk in a device.

    Identity Verification

    How to add device intelligence with Myaza Trust

    Device Intelligence adds context from the device and network used during capture. Configure the findings your team cares about and use them with other evidence rather than treating every shared device as fraud.

  • Myaza Trust editorial illustration: Stronger proof. From the chip.

    Identity Verification

    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.

  • Myaza Trust editorial illustration: A real person. Right now.

    Identity Verification

    How to confirm a live person with Myaza Trust

    Liveness helps establish that a real person is in front of the camera. Enable it in the workflow customers use, choose a method, and route captures your policy cannot accept.

  • Myaza Trust editorial illustration: Know who joins your app.

    Identity Verification

    How to verify a new customer with Myaza Trust

    Verify a new customer with a published individual workflow. The customer completes the document and selfie journey; your backend receives the outcome and applies your onboarding policy.

  • Myaza Trust joins NVIDIA Inception, beside a graph of identity signals feeding a risk system that decides trust, review or decline.

    Product Updates

    Myaza Trust joins NVIDIA Inception

    Matching a face to one document is a contained problem. Searching it against every identity a business has verified is not. Why our fraud work is becoming a compute problem, and why Myaza Trust has joined NVIDIA Inception.

  • The same verification screen twice on a purple gradient: the default footer reads Protected by Myaza Trust, the branded one reads Protected by acmepay.

    Product Updates

    White-label verification: putting your own logo on every verification screen

    You can replace the “Protected by Myaza” footer on every verification screen with your own logo. It costs $0.10 per production verification, and your organisation needs $750 of paid credit the first time a custom logo goes live. After that, anyone on your team can change it at any balance.

  • Headline "What wallet screening catches" beside an illustration of a wallet with a highlighted address, on a warm cream gradient.

    Risk & Compliance

    Screening crypto wallet addresses: what it catches and where it stops

    Wallet screening catches addresses that a sanctions authority has published, matched exactly. It misses unlisted addresses controlled by the same person, funds that passed through intermediaries, and anything published after your last check.