FAQs
Common questions and pitfalls when dealing with Verification Statuses.
When do you send verification status update?
You can expect our API to push an update to your webhook whenever the status of the address changes:
from initial no status to
"verified".from no status to
"not_at_address"from no status to
"unknown"from
"not_at_address"to"verified"etc
Address verification statuses
(no status)
first_time
the verification just got initiated for the first time
verified
continuous
the verification process has completed and the address is verified.
not_at_address
first_time / continuous
verification window has come to an end and the address was not verified due to user not frequenting the address. Common cause for this is that the user created a wrong address hence appears as though the user did not frequent the address much`
unknown
first_time / continuous
verification window has come to an end and the address was not verified due to lack of sufficient data from the user's device. Common cause of this is that that user did not give sufficient location permissions or phone was offline
How long does verification take?
We expect an address to be verified within 2-8 days. During this time, as soon as we can verify an address we will return a status of verified that the address is verified. Otherwise, on the 8th day, you'd get a status update that the address is unknown or not_at_address.
What are the modes
When a new verification has started it will be in the first_time mode. Once we have determined that the address is verified or not_at_address, we will change the mode to continuous. If by the 8th day we have not been able to determine if the address is verified or not_at_address then we will classify it as unknown and change the mode to continuous.
In continous mode, we will continue to periodically collect data from the device to improve or update this status but do not post these changes via the webook or to the Dashboard.
Last updated