Mock Failure Data - Testing in Sandbox
Registration - The Unhappy Path
In sandbox only, you can mock future KYC failure states by using the below values for the entity upon registration.
Error Messages
This is a list of most possible error messages that can occur when registering a user.
Birthdate
"Registered user must be 18."
"Received birthdate: INPUT_DATE"
"Derived age: AGE"
"Current server date: CURRENT_DATE""Not a valid birthdate, maximum allowed AGE_LIMIT."
"Received birthdate: INPUT_DATE"
"Derived age: AGE"
"Current server date: CURRENT_DATE"Epoch
"Integer not valid epoch."
"Epoch cannot be set in the future. (Parsed epoch as: DATE)""Provided epoch in message has expired; please generate a new message and signature to retry this request. (Parsed epoch as: DATE)"
US Postal Code
"invalid_postal_code"Handle
"This value does not match the required handle pattern: PATTERN"Blockchain Address
"This value does not match the required address pattern: PATTERN"Phone Number
"This value does not match the required phone number pattern: PATTERN"Identity
"Input did not match SSN regex pattern."
"Input did not match EIN regex pattern PATTERN"
Registration Field | Error Trigger | Outcome Tags & Reasons in Response |
|---|---|---|
first_name, OR last_name, OR full_name |
| " |
first_name, OR last_name, OR full_name |
| Status: |
first_name, OR last_name, OR full_name |
|
|
first_name, OR last_name, OR full_name |
| Status: |
street_address_1 |
|
|
birthdate |
|
|
identity_alias & identity_value |
|
|
entity: type & entity_name |
|
|
identity_alias & identity_value |
|
|
device.session_identifier |
|
|
Next Steps:
-
Request KYC
Run endpoint to enable Check KYC
-
Check KYC
Run endpoint to return failure tags (see Testing Mock Failure Data for tags)
-
Identify documents to upload for failed use cases
Updated about 1 month ago