Check Payment Webhook Events
The following webhook events are available for Check Payments:
| Event | Description |
|---|---|
| checkPayment.created | Fired when a check payment is created. |
| checkPayment.pending | Fired when a check payment status changes to Pending. |
| checkPayment.inProduction | Fired when a check payment has been sent to the printers. |
| checkPayment.inDelivery | Fired when a check payment has been accepted by the mail service and is en route. |
| checkPayment.delivered | Fired when a check payment has been delivered. |
| checkPayment.canceled | Fired when a check payment has been canceled. |
| checkPayment.rejected | Fired when a check payment has been rejected. |
| checkPayment.processed | Fired when a check payment has been processed and the deposit account was debited. |
| checkPayment.markedForReturn | Fired when a check payment has been marked for return. |
| checkPayment.returned | Fired when a check payment has been returned. |
| checkPayment.returnToSender | Fired when a check payment could not be delivered and is being returned to the sender. |
| checkPayment.deliveryStatusChanged | Fired when a check payment's delivery status changes. |
| checkPayment.additionalVerificationRequired | Fired when a check payment requires additional verification. |
| checkPayment.additionalVerificationApproved | Fired when additional verification for a check payment has been approved. |
| transaction.created | Fired when a debit transaction is created for the check payment. |
previousStatus on check payment events
Several check payment webhook payloads include a string attribute previousStatus. It names the check payment’s status immediately before the event was recorded (for example PendingReview before checkPayment.processed).
When previousStatus is "Unknown"
You may see previousStatus: "Unknown" instead of a concrete status name. That value is emitted when the processing path does not pass a prior status into the webhook payload—not because Unit lacked the earlier status on the check payment resource.
For other reprocess outcomes (for example transitions into PendingReview or MarkedForReturn), previousStatus is usually populated when the pipeline supplies an initial status; if it does not, "Unknown" can appear there as well.
See the Webhook Events documentation for detailed information about each event's payload and structure.