Lock and disable participants

Release Information

Enhanced Participant Status and Locking Mechanism

Release Date

April 4, 2023

Release Type

Actionable – Responses returned from Zero Hash may impact user experience

Summary

Zero Hash has implemented improvements to its participant status system to better manage fraud and risk mitigation. New statuses and reason codes have been introduced, providing platforms with more insight into participant status changes. Additionally, a new endpoint for locking participants has been added.

New Statuses and Reason Codes

Status	Reason Code	Description
submitted	null	None - participant is awaiting initial approval
approved	null	All - participant was never under investigation
approved	risk_cleared	All - participant was under investigation but risk was cleared
locked	user_request	Closing only (sell/withdraw)
pending_unlock	user_request	Closing only (sell/withdraw)
pending_disable	user_request	Closing only (sell/withdraw)
disabled	user_request	None
divested	user_request	None
closed	user_request	None
locked	compliance_issue	None
pending_unlock	compliance_issue	None
pending_disable	compliance_issue	None
disabled	compliance_issue	None
divested	compliance_issue	None
closed	compliance_issue	None

Action Required

No specific action required, but transaction availability may be impacted based on participant status changes.
Platforms can now use the POST /participants/customers/:participantCode/lock endpoint to lock participants.

New Endpoint

Endpoint: POST /participants/customers/:participantCode/lock
- Description: Used to lock participants upon termination of relationship.
- Parameters: reason_code, notes (optional)
- Sample Request:
```
POST /participants/customers/7PJM14/lock
{
 "reason_code": "compliance_issue",
 "notes": "confirmed fraud"
}
```
- Sample Response: OK or error message

Endpoints Impacted

All transactional endpoints will reference participant status before allowing or denying requests.
GET /participants will now display expanded statuses and include a "reason_code".
Introduction of new endpoint POST /participants/customers/:participantCode/lock.

Relevant Documentation

Participant Statuses Article Participant status updates

Future Release

Zero Hash plans to develop webhooks for Q3 to alert platforms of participant status changes.

Additional Notes

Platforms are responsible for locking customers upon termination of their relationship, using the provided endpoint.