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.

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:

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

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.

Code
Description

100

Invalid or missing Social Security Number (SSN).

101

Invalid or incomplete address.

102

Invalid or missing date of birth.

103

Invalid or missing last name.

200

Secretary of State data mismatch.

201

Incorrect state of registration.

202

Invalid or missing tax ID.

203

Legal name mismatch.

204

Invalid physical address.

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.

Last updated

Was this helpful?