Mandate Webhook

For general webhook mechanics (response requirements, security, IP whitelisting, troubleshooting), see Webhooks - Async Updates or Webhook Security.

ℹ️ Do not validate against a strict schema. Feezback or the bank may add additional fields to any of these events over time — parse only the fields you need.

Event: MandateStatusChanged

Fired on any status transition of a mandate.

Payload fields

{
  "timestamp": "2021-03-04T12:26:32.212913+00:00",
  "event": "MandateStatusChanged",
  "payload": {
    "user": "user-00112233",
    "mandateId": "7fh64-fjue749-fn378hr004",
    "psuId": "222222222",
    "psuCorporateId": "519999999",
    "accountNumber": "10-123-1234567",
    "context": "tx-20250113001",
    "previousStatus": "received",
    "currentStatus": "valid",
    "validUntil": "null",
    "lastActionDate": "2025-03-04T12:26:32.212913+00:00"
  }
}

Event: MandateDataChanged

Fired when the mandate's underlying data (amount, expration date, etc.) changes.

Same fields as MandateStatusChanged, plus:

Event: MandateAboutToExpire

Fired up to 30 days before a mandate's validUntil.

Same payload as MandateStatusChanged.

Not included in this event: psuId, psuCorporateId, accountNumber, previousStatus.

Added — only in this event: data (Object, Fixed — the mandate's current data).

Mandate statuses

Testing (Mock Bank)

1. Create a Mandate link without a debtor account in the JWT.
2. Choose MockBank on the Feezback screens.
3. Enter a 5-digit account number: 12345.
4. Use one of these test IDs (psuId) to trigger a specific outcome: