Resolve representative blockers

A missing_associate blocker identifies the role and minimum number of people needed:

{
  "code": "missing_associate",
  "subject": {
    "type": "associate",
    "roles": ["director"],
    "minimumCount": 1
  },
  "action": {
    "method": "POST",
    "path": "/v1/senders/associates",
    "bodyFields": ["senderId", "roles"]
  }
}

Use the supplied action path.

Representative is already a UBO

Link the associate to the existing UBO so Mesta reuses the person's stored details and verification state:

{
  "senderId": "7e701fe5-d47b-4e44-b624-c48204cfead1",
  "roles": ["director"],
  "linkedUboId": "c4de346d-7972-4139-b132-974eca8b0606"
}

Do not duplicate the linked UBO's personal or identity data in this request.

Representative is a different person

Send the representative's personal, address, nationality, and identity information:

{
  "senderId": "7e701fe5-d47b-4e44-b624-c48204cfead1",
  "roles": ["director"],
  "firstName": "Amina",
  "lastName": "Rahman",
  "birthDate": "1988-04-12",
  "email": "[email protected]",
  "phone": "+442071838750",
  "nationality": "GB",
  "address": {
    "street": "10 Example Street",
    "city": "London",
    "postalCode": "SW1A 1AA",
    "country": "GB"
  },
  "identity": {
    "countryCode": "GB",
    "documentType": "PASSPORT",
    "documentNumber": "123456789",
    "documentFront": "<base64-encoded-file>"
  }
}

Identity-document requirements vary by identity country and document type. Use the supported document-type response for the selected country, and provide Base64-encoded front/back documents when required.

Continue setup

After creating the representative, call the setup-request GET endpoint again. The request is re-evaluated from stored sender data; you do not pass an associate ID to the setup endpoint.

If the representative must complete identity verification, the setup response returns associate_verification_pending with that person's ID and the appropriate next action.