Successfully submitted to <POST /participants/customers/new> and given a participant code, but has not yet been approved to transact.
pending_approval
Participant 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.
approved
Participant code and relationships created and the participant passes necessary approvals to transact.
rejected
Participant rejected from becoming an active user; most often due to customer verification (KYC) failures.
locked
Investigative state for the Zero Hash compliance team.
pending_unlock
Investigations conclude the participant may remain active on Zero Hash. Only available from Get participants, not via webhook.
pending_disable
Investigations conclude the participant should be indefinitely banned from Zero Hash. Only available from Get participants, not via webhook.
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
Participant Reason Codes and Request Availability
Reason Code
Definition
Request Availability
compliance_issue
locked
None
compliance_issue
pending_disable
None
compliance_issue
disabled
None
compliance_issue
closed
None
compliance_issue
divested
None
user_request
locked
Closing only (sell/withdraw)
user_request
pending_disable
Closing only (sell/withdraw)
user_request
disabled
None
user_request
closed
None
user_request
divested
None
risk_cleared
pending_unlock
None - the cleared risk still needs to be approved
