Understand statuses, required verification, and possible errors for Persons.
status
of created
.verified
in order to send or receive funds. However, some use cases allow a person to have a status of created.
Your use case will be determined during onboarding and will dictate which Persons Status is required to transact. The respective data requirements are listed below:
Created Person
status_reason
field in the API response.
If a person fails customer identification and is set to the rejected status, Orum will automatically kick off a manual review and attempt to retry the customer identification workflow to resolve the issue.
person_rejected
or person_restricted
webhook. The person object in the webhook will have a status of rejected
or restricted
and a status_reasons array that explains why the person failed customer identification.
Status Reasons contain:
reason_code
: a word-based code that describes the customer identification failurereason_code_message
: a friendly description of the reason code that can be surfaced directly to your end usersstatus_reasons
will also be present in the GET /persons and GET /persons/id API responses.
reason_code | reason_code_message |
---|---|
deceased_person | User is reported as deceased |
incomplete_address | Address submitted is missing some or all required elements |
incomplete_dob | Date of birth submitted is missing some or all required elements |
incomplete_ssn | SSN submitted is missing some or all required elements |
ineligible_age | Age submitted is under 18 and not eligible for this product |
invalid_address_type | Address submitted is a non-supported address type |
invalid_dob | Date of birth is invalid |
invalid_name | Name is invalid |
invalid_ssn | SSN is invalid |
matched_alertlist | Matched a list of known fraudulent users |
matched_watchlist | Matched one or multiple sanctions lists |