# Inbound message regarding customer Identity related messages

When a customer failed to create an order for a specific reason, the status update will be sent to the provided callback endpoint to your server.

Endpoint: POST identityMessage
Version: 0 BETA

## Request fields (application/json):

  - `identity_reference` (string, required)
    A unique customer identifier provided by the partner. This field is required and must be unique for each customer.
**Important**: You must consistently reuse the same identityReference for repeat interactions with the same customer, allowing Banxa to reliably recognize and associate their identity across multiple transactions.
**Format Requirements**:
- Only ASCII letters (a-z, A-Z), digits (0-9), and hyphens (-) are allowed
- Must be between 1 and 255 characters
- Case-sensitive

**Best Practices**:
- Use a consistent format across your system
- Consider using a prefix to identify your organization (e.g., 'partner-customer-123')
- Do not include personally identifiable information (PII) in the reference
- Store the mapping between your internal customer ID and this reference securely
    Example: c-13344

  - `status` (string, required)
    | Status | Description |
|  --- | --- |
| ACCOUNT_BLOCKED | Customer account is blocked. |
    Enum: "ACCOUNT_BLOCKED"

  - `status_date` (string, required)
    The date of the status update
    Example: 2023-06-05 19:53:08

  - `internal_reason` (string, required)
    The internal body for this inbound message containing the reason of the message, this is for internal use.
    Example: Customer account is blocked.

  - `external_reason` (string, required)
    The external reason to provide to your customer via your designated messaging channel.
    Example: You order could not be processed

## Response 200:

  - `200` (unknown)
    Your server returns this code if it accepts the callback. On a failed response we will retry sending the webook.