Participant Statuses

Participant Status Definitions

StatusDefinition
submittedSuccessfully submitted to <POST /participants/customers/new> and given a participant code, but has not yet been approved to transact.
pending_approvalParticipant code and relationships created, but the participant requires further review by the Zero Hash compliance team before moving to approved or rejected. Most often due to customer verification (KYC) alerts.
approvedParticipant code and relationships created and the participant passes necessary approvals to transact.
rejectedParticipant rejected from becoming an active user; most often due to customer verification (KYC) failures.
lockedInvestigative state for the Zero Hash compliance team.
pending_unlockInvestigations conclude the participant may remain active on Zero Hash. Only available from Get participants, not via webhook.
pending_disableInvestigations conclude the participant should be indefinitely banned from Zero Hash. Only available from Get participants, not via webhook.
disabledIndefinitely banned from Zero Hash, but balances may exist in the participant account. Zero Hash settlement team will divest existing balances.
divestedIndefinitely banned from Zero Hash and participant balances were moved back to the platform float.
closedIndefinitely banned from Zero Hash and no balances remained at the time of ban

Example of the standard participant status flow:

Participant Reason Codes and Request Availability

Reason CodeDefinitionRequest Availability
compliance_issuelockedNone
compliance_issuepending_disableNone
compliance_issuedisabledNone
compliance_issueclosedNone
compliance_issuedivestedNone
user_requestlockedClosing only (sell/withdraw)
user_requestpending_disableClosing only (sell/withdraw)
user_requestdisabledNone
user_requestclosedNone
user_requestdivestedNone
risk_clearedpending_unlockNone - the cleared risk still needs to be approved
risk_clearedapprovedAll