Skip to content
MyazaTrust

From the team · Page 6

Inside Myaza Trust.

  • Headline "Verification in a mobile app" beside an illustration of a phone showing a face capture guide, on a deep indigo gradient.

    Developers

    Adding identity verification to a React Native or Flutter app

    The component call is the easy part. A mobile integration is mostly native build setup, camera permission, mounting a dashboard workflow so changes skip the app store, and keeping results on your server rather than on the phone.

  • Headline "Status in, product state out" beside an illustration of three rising tiers, on a deep indigo gradient.

    Developers

    Mapping verification statuses to your product's states

    Drive your product from status, the outcome, and store checkStatus beside it as the explanation. Map each of the ten status values to one state in your own system, and take the latest status from verification.status_updated or polling.

  • Headline "Testing verification in sandbox" beside an illustration of a laboratory flask with bubbles, on a deep indigo gradient.

    Developers

    Testing a verification integration end to end in sandbox

    Use the published sandbox test IDs, whose last digits pick the outcome, to drive every result your code must handle, then test your webhook receiver with signed simulated events before switching to live keys.

  • Headline "Change flows without a release" beside an illustration of a continuous circular arrow, on a vivid purple gradient.

    Product Updates

    Changing a verification flow without shipping an app release

    Mount the SDK with a workflow ID and the flow's configuration is fetched from the server on each verification. Re-publishing changes the steps, checks, copy and decision rules for the next verification, with no app release.

  • Headline "How decision graphs decide" beside an illustration of a decision graph splitting into approve and decline, on a vivid purple gradient.

    Product Updates

    How decision graphs turn checks into approve, review or decline

    When a verification finishes, the workflow's decision graph gathers the results, walks branches over a closed set of fields, and lands on approve, review or decline. The outcome sets the customer's disposition without rewriting what the checks found.

  • Headline "Webhook signatures and retries" beside an illustration of a code window with angle brackets, on a deep indigo gradient.

    Developers

    Verifying webhook signatures and handling retries correctly

    Verify the V2 signature over the raw request bytes, reject timestamps outside the replay window, record the event ID under a unique constraint before doing any work, and return 2xx only once the event is durably stored.

  • Headline "Biometric data under African law" beside an illustration of a face outline mapped with landmark points, on a warm cream gradient.

    Risk & Compliance

    Handling biometric data under African data protection laws

    All three laws treat biometric data as a special category. Nigeria names facial images and limits sensitive data to listed grounds, Kenya treats biometric processing as high risk, and POPIA prohibits it unless an authorisation applies. Plan a lawful ground, a DPIA and minimisation.

  • Headline "The limits of device and IP signals" beside an illustration of a grid of devices with a highlighted cluster, on a warm cream gradient.

    Risk & Compliance

    What device and IP signals can and cannot tell you

    Device and IP signals describe the handset and connection, not the person. Emulators and datacentre IPs are strong warnings; shared devices, IP velocity and IP location are weak. Use them as corroboration, and trust IP location at country level only.