Skip to content
From the team · Page 2

Identity Verification

Page 2

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

  • Identity Verification

    Where verification flows lose people, and how to fix each step

    People abandon verification at predictable moments: an unexplained start, the camera permission prompt, document capture, the desktop that has no camera, and being asked to redo everything after one failure. Measure abandonment per step, then fix the step, not the whole flow.

  • Identity Verification

    Age checks that hold up: from a birthday field to a verified date of birth

    A reliable age check uses a date of birth established by an identity check (the government record, the document or its chip), compares it with a per-country limit, and fails closed when no date can be read. A typed birthday proves nothing, and a face gives an estimate with a margin of error.

  • Identity Verification

    Verifying addresses where streets have no numbers

    Where streets have no numbers, stop matching address strings. Capture a location (a map pin with the applicant's own directions and details), then corroborate it at the level of the area against independent records, and grade how strongly it is supported.

  • Identity Verification

    Proof of address: what a utility bill does and does not prove

    A proof-of-address document shows that an address was printed on a document, often with a name, at a date. Give it the weight of corroborating evidence, not verification, and set rules for name, recency and document type that fit each market.

  • Identity Verification

    Proving the person applying can act for the business

    Registration numbers are public, so anyone can type a real company's number. To know the applicant represents the business, verify who they are, check them against the officers the register names, and, where they are not named, ask for evidence of their authority.

Identity Verification Insights | Myaza Trust, page 2 · Toden