ApiK Y B Re verification

The business's locked-field change requests

GET
/api/b/v1/kyb/field-change-requests

Authorization

OAuth2PasswordBearer
AuthorizationBearer <token>

In: header

admin_access_token?string|null

Response Body

application/json

application/json

curl -X GET "https://example.com/api/b/v1/kyb/field-change-requests"
{  "requests": [    {      "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",      "field": "legal_name",      "old_value": "string",      "new_value": "string",      "status": "pending",      "requested_by": "cda0f200-65cd-4343-aedd-9c936b908826",      "created_at": "2019-08-24T14:15:22Z"    }  ]}

Select the business's industry and apply the industry policy POST

Record the industry and re-evaluate the application. A restricted industry flags the application `requires_underwriting` and opens an underwriting case record in the same transaction; an allowed industry leaves the application where it stands. The evaluation is idempotent: re-selecting the same industry does not stack cases.

Submit a locked-field change (forces re-verification) POST

File a change to `legal_name` or `registration_number`. When the business is verified the fields are locked: the change is recorded as a pending request, the application moves `in_review`, and live limits drop to the configured safe mode (AC1). The new value is not written to the business - applying it is a compliance operator's decision. When the business is not yet verified the field is not locked and the edit is applied immediately.