Overview

The ManualApplicationStatusChange event fires when an underwriter manually changes a merchant application's status — approving, rejecting, or withdrawing the application. Use this event to capture underwriter-driven decisions that occur outside the automated underwriting flow, for example when a merchant supplies additional information and the underwriter approves the application by hand.

Trigger Conditions

This event is triggered when an underwriter manually changes an application's status by doing any of the following:

Manually approving an application.
Manually rejecting an application.
Manually withdrawing an application.

This event fires only for manual, underwriter-initiated status changes — not for systematic status changes.

Payload Schema

Top-Level Fields

Field	Type	Description
`Type`	Integer	Always `3` for this event.
`EventIdentifier`	String	Always `ManualApplicationStatusChange`.
`EventData`	Object	Contains the application status details. See EventData Fields below.

EventData Fields

Field	Type	Description
`MerchantApplicationId`	Integer	The merchant application ID.
`Status`	String	The status of the merchant application. Values: `Incomplete`, `Approved`, `Acquirer Review`, `New Pend`, `Follow Up`, `Re-Pend`, `Triggered Pend`, `Approved and Boarded`, `Declined`, `Processing`, `Pre-Generated`, `Triggering`, `Withdrawn`.
`StatusValue`	Integer	Numeric representation of `Status`. See Status Values below.
`ExternalApplicationIdentifier`	String	The unique ID created by the Payfac and set when the merchant application is created via API.
`MerchantIdentifier`	String	The merchant application ID.
`UnderwritingResultsURL`	String	The merchant application URL.
`UnderwritingDeclineReason`	String	The reason the merchant application was declined. Populated if the application was declined.
`InfiniceptMerchantIdentifier`	String	The merchant application UUID created by Infinicept.

Status Values

StatusValue	Status
`0`	Incomplete
`1`	Approved
`2`	Acquirer Review
`3`	New Pend
`4`	Follow Up
`5`	Re-Pend
`6`	Triggered Pend
`7`	Approved and Boarded
`8`	Declined
`11`	Processing
`12`	Pre-Generated
`13`	Triggering
`14`	Withdrawn

Note: Values 9 and 10 are not currently used.

Example Payload

{
  "Type": 3,
  "EventIdentifier": "ManualApplicationStatusChange",
  "EventData": {
    "MerchantApplicationId": 1037,
    "Status": "Approved",
    "StatusValue": 1,
    "ExternalApplicationIdentifier": null,
    "MerchantIdentifier": "860",
    "UnderwritingResultsURL": "https://resultsurl.io/tenantslug/CoBrands/MerchantUW?applicationId=860",
    "UnderwritingDeclineReason": null,
    "InfiniceptMerchantIdentifier": "192325f8-5393-4d5e-9cbd-bed3c5c905d6"
  }
}

Handling This Event

Check StatusValue to determine the outcome of the underwriter's decision — for example 1 (Approved), 8 (Declined), or 14 (Withdrawn).
Read UnderwritingDeclineReason when the application was declined to surface the reason to your team or the merchant.
Use UnderwritingResultsURL to link users or internal teams directly to the full application in the cobrand.
Store InfiniceptMerchantIdentifier and ExternalApplicationIdentifier to correlate this event with records in your own system.

Support

Have a question? Contact us on the Customer Support Portal.

Learn about updates in our Changelog.