Technical FAQs

Some answers to the more technical questions for developers, PMs and testers..

Technical Systems & Terms

Why are many of the verifications "unknown"?

We classify an address as "unknown" when there is not enough data is being transmitted to our servers for verification. There are a few ways to mitigate unknowns here.

What is the accuracy of the verification?

The accuracy of the GPS on the device can differ greatly depending on reception and device type. We only collect data points within a few hundred meters of where they drop the pin for the address and analyse these over time. As we aggregate many of these points the accuracy of any single data point does not massively influence the verification.

Another type of accuracy is the confidence that we have in reducing false positives in the verification process. While we are constantly improving the ML models, our standards are comfortably higher than any other type of address verification.

What is re-verification?

A re-verification is when we run verification on an address that has been previously verified. This process is done to make sure a user still stays at the address they were previously or to try again after correcting for circumstances that may have resulting in a Not at address or Unknown status.

How long does verification take?

It depends widely on how much data our systems receive and we aim to verify as fast as possible - without comprimising on accuracy. For the first time an address is being verified, it takes at least 36hours for us to be sure and we will continue trying to verify the address for up to 8 days. (80% of successful verifications come in within 48 hours.)

Do OkHi's SDKs use a lot of data or battery?

No, both OkCollect and OkVerify use minimal data and will use a small percentage of data compared to the normal usage of your application.

Both OkCollect and OkVerify have been optimised to have minimal impact on the user’s phone battery. For normal usage, both SDKs will use < 1% of the battery.

Common Developer Questions

How long does it take the mode to change from 'first-time' to 'continuous' after an address is verified?

The update will take 5 to 10 minutes to be sent via the API webhook after verification is completed.

Is the email field required for a user?

Technically the email field is not required, but we advise that you do send it through whenever you can for easy user management and notifications. Note that there may be additional notification charges if we do not have email addresses for users.

Where do I get my login for the dashboard?

You can monitor the status of your customers verifications by loging into the dashboard. We will send you the initial login details along with your API information after completing this form. If you're having further trouble, get in touch with our team directly.

Why is an address not appearing on the dashboard?

Only addresses that have started verification show up on the dashboard. (So they won't show if they an address is only created without verification starting.) You can always see a full history of addresses that were previously verified on the customer dashboard.

How large are OkHi's SDKs?

Excluding native libraries that are required as dependencies:

  • Android in total is ~200kb

  • iOS in total is ~414kb?

  • React Native in total is ~900kb unpacked

  • Flutter in total is ~120kb

Questions from Testing and QA

What is the maximum address per device?

A device can not verify more than 20 locations at a time. To create more, you need to uninstall and reinstall the app to clear all data (and geofences.) This will stop new data being sent for the previous geofences.

How do I test or run Quality Assurance on an OkHi implementation?

We have a full QA and testing guide available HERE.

Have further questions? Reach out to our team directly.

Last updated