NMnmi
Webhook Events

Merchant: Residual Report Published

This event is triggered when merchant residuals reports are published.

postWebhookmerchant.residuals.published

Payload

event_idstring
event_type'application.updated.data.requested' | 'application.approved' | 'application.declined' | 'application.cancelled' | 'application.merchant.closed' | 'application.merchant.boarded' | 'merchant.chargeback.added' | 'merchant.deposit.new' | 'merchant.first-batch' | 'merchant.processing.start' | 'merchant.processing.stop' | 'merchant.residuals.published' | 'merchant.retrieval.added' | 'merchant.statement.new'

Example payload

{
  "event_id": "38cf9efa-8aec-4a4e-98e2-6bb2411fdc60",
  "event_type": "merchant.residuals.published",
  "event_body": {
    "month": 3,
    "year": 2024,
    "processor_id": 123,
    "processor_name": "TSYS"
  }
}

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.