Zero Hash uses participant statuses to determine whether transaction requests can be made. This field is labeled “status” in the participant object. Below outlines participant statuses and what they mean.
|Submitted||Successfully submitted to <POST /participants/customers/new> and given a participant code, but has not yet been approved to transact.|
|Approved||Participant code and relationships created and the participant passes necessary approvals to transact.|
|Rejected||Participant who was rejected from becoming an active user; most often due to customer verification declines.|
|Locked||Investigative state for the Zero Hash compliance team.|
|Pending unlock||Investigations conclude the participant may remain active on Zero Hash.|
|Pending disable||Investigations conclude the participant should be indefinitely banned from Zero Hash.|
|Disabled||Indefinitely banned from Zero Hash, but balances may exist in the participant account. Zero Hash settlement team will divest existing balances.|
|Divested||Indefinitely banned from Zero Hash and participant balances were moved back to the platform float.|
|Closed||Indefinitely banned from Zero Hash and no balances remained at the time of ban.|
Oftentimes statuses are accompanied by reason codes, which indicate request availability for the participant.
|Reason code||Definition||Accompanying status||Request availability|
|compliance_issue||Unusual activity was detected and/or confirmed.||
|user_request||Participant contacted Zero Hash or the platform to request removal.||
|Closing only (sell/withdraw)|
|risk_cleared||Investigations took place and the participant was cleared to be active again.||pending_unlock||None - the cleared risk still needs to be approved|
If a platform makes a request for a participant who has a status with no request availability, then the platform will receive the error message “Participant [participant_code] is not allowed to transact”.