> For the complete documentation index, see [llms.txt](https://docs.xplorpay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xplorpay.com/api-reference/webhooks/working-with-webhooks/merchant-onboarding-webhooks/application-fixes.md).

# Application Fixes

The **Application Fixes** webhook event to notify about data validation issues detected in merchant applications. These events are triggered by validation checks during the underwriting process.

{% hint style="warning" %}
Applications configured with Agreement Express won’t generate these events.
{% endhint %}

### Event names

The following webhook event types are used to surface validation errors:

* `BusinessFixes`
* `ContactFixes` 

Each event provides details about the issue, the affected contact, and recommended corrections.

### Payload structure example

The webhook payload includes one or more validation messages for specific contacts. Each message contains a human-readable description and a code identifying the type of issue. Refer to the sample code below:

{% code lineNumbers="true" %}

```json
{
  "payload": [
    {
      "contactId": 131047,
      "messages": [
        {
          "message": "Fix Address",
          "code": 101
        }
      ]
    },
    {
      "contactId": 131048,
      "messages": [
        {
          "message": "Fix SSN",
          "code": 100
        }
      ]
    }
  ]
}

```

{% endcode %}

### Message codes

Each code corresponds to a specific type of validation issue. Use these codes to programmatically handle or display user-friendly error messages in your application interface.

<table><thead><tr><th width="161">Code</th><th>Description</th></tr></thead><tbody><tr><td>100</td><td>Invalid or missing Social Security Number (SSN).</td></tr><tr><td>101</td><td>Invalid or incomplete address.</td></tr><tr><td>102</td><td>Invalid or missing date of birth.</td></tr><tr><td>103</td><td>Invalid or missing last name.</td></tr><tr><td>200</td><td>Secretary of State data mismatch.</td></tr><tr><td>201</td><td>Incorrect state of registration.</td></tr><tr><td>202</td><td>Invalid or missing tax ID.</td></tr><tr><td>203</td><td>Legal name mismatch.</td></tr><tr><td>204</td><td>Invalid physical address.</td></tr></tbody></table>

### Handling validation events

To improve the merchant experience and avoid pended applications:

* Monitor for `BusinessFixes` and `ContactFixes` events.
* Display validation messages to the merchant during the application process.
* Allow merchants to update their information before submitting the application.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.xplorpay.com/api-reference/webhooks/working-with-webhooks/merchant-onboarding-webhooks/application-fixes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.