Verify the phone code
Identity verification
Verify the phone code
Checks the code the user read back. On success the verification stays fresh for 60 days and funding sessions can be created.
POST
Verify the phone code
Notes
phone_numberis required when the user had no phone on file at start (e.g. a fresh connection before KYC) — the code was sent to the number you supplied, can only be checked against it, and there’s no stored number to fall back on, so a call without it returnsphone_number_required. Keep passing that same number on verify until the user is verified: the code is only ever valid against the number it was sent to, so don’t switch to a stored number that shows up mid-flight (a KYC backfill between start and verify). Omitphone_numberonly when start sent the code to a number already on file. It’s optional in the schema only because that stored-number case exists.- On
verified, the user can fund immediately — the verification stays fresh for 60 days. invalid_codecarries areason(incorrect,expired,too_many_attempts, orno_code) so you can decide between “try again” and “send a new code”.
Authorizations
A platform access token. Get one on the Create an access token endpoint by exchanging your client_id + client_secret, then send it as Authorization: Bearer <token>. Tokens live one hour.
Body
application/json
Response
Verified.
Allowed value:
"phone_verification"Available options:
sent, already_verified, verified Where the code was sent (status sent only).
Available options:
sms, email The masked destination number (status sent only).
How long the code stays valid (status sent only).