Mandate Amendments

Create the amendment.

Call POST /mandates/{id}/amendments with the new values — only the fields you want to change:

{
  "validity": {
    "to": "2027-08-31T00:00:00+00:00"
  },
  "payTo": {
    "limits": {
      "payment": {
          "maxAmount": 12000
      }
    }
  }
}

An amendment cannot mix bilateral and unilateral fields — submit them as separate amendments.

There can be only one pending bilateral amendment at a time.

The response is the amendment object:

{
  "id": "79fb2306-e199-497e-b5a1-912a68a02894",
  "mandateId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "track": "BILATERAL",
  "initiator": "CUSTOMER",
  "status": {
    "status": "AWAITING_APPROVAL",
    "details": null
  },
  "changes": {
    "validity": {
      "to": "2027-08-31T00:00:00+00:00"
    },
    "payTo": {
      "limits": {
        "payment": {
            "maxAmount": 12000
        }
      }
    }
  },
  "createdAt": "2026-06-10T12:00:34+00:00",
  "updatedAt": "2026-06-10T12:00:34+00:00"
}

track tells you whether payer approval is needed; initiator is CUSTOMER for amendments you create and PAYER for changes made by the payer at their bank; changes echoes the proposed values.

Wait for the amendment webhook.

A notification is sent to the mandate's webhook URL when the amendment status changes (see Amendment lifecycle). Unilateral amendments are applied without payer involvement; bilateral ones only after the payer approves.

You can also poll GET /amendments/{id} for the current status at any time.

(Optional) Recall a pending amendment.

DELETE /amendments/{id} recalls an amendment that is still NEW or AWAITING_APPROVAL. Once an amendment has been approved, recall is no longer possible.

Recalled amendments return 404 Not Found from GET /amendments/{id}.