The Entity Verification Sessions manages phone and identity verification sessions for Entities.
Entities need to verify their identity and/or phone in order for them to be used throughout the Method API.
Entity verification requirements differ on a team-by-team basis. A team’s unique verification process is pre-defined
during onboarding based on your team’s specific use case. Contact your Method CSM for more information.The method key in entity.verification object will enumerate the phone & identity verifications available for your Entity.
Refer to the Entity Object.
Any Entity Verification Session will expire 10 minutes after creation. If the
verification is not completed within that time limit, another verification
session will need to be created.
SMS is used to verify the Entity’s phone number by sending a SMS code and expecting to receive that same SMS code back to verify the phone.
sna
Silent Network Auth (SNA) is an authentication method to confirm an Entity’s phone number in the background without requiring the user to wait or leave the app.
byo_sms
Bring-Your-Own SMS (BYO SMS) means the Entity’s phone number has already been verified via a non-Method provider. Skipping phone verification requirement.
byo_kyc
Bring-Your-Own Know-Your-Consumer (BYO KYC) means the Entity’s identity has already been verified via a non-Method provider. Skipping identity verification requirement.
kba
Knowledge-Based Authentication (KBA) is an authentication method which confirms a person’s identity by asking a series of knowledge questions which only the true owner should know.