Reinstate a suspended Direct Debit mandate

Reinstates a suspended mandate. This is NOT a status flip — it re-lodges the mandate to Bacs (a new AUDDIS instruction) using the securely stored bank details, then moves the mandate to pending_lodgement (REV-3123).

Related endpoints

• POST /mandates — Create a Direct Debit mandate
• GET /mandates — List Direct Debit mandates
• GET /mandates/{id} — Retrieve a Direct Debit mandate
• POST /mandates/{id}/cancel — Cancel a Direct Debit mandate
• POST /mandates/{id}/suspend — Suspend a Direct Debit mandate
• POST /mandates/{id}/collections — Schedule a one-off Direct Debit collection

Common errors

• 400 invalid_request — malformed payload or failed validation.
• 401 unauthenticated — missing, malformed, or revoked API key.
• 404 resource_missing — the referenced resource does not exist or is not visible to your key.
• 409 conflict — Idempotency-Key collision with a different body, or a concurrent state-transition conflict.
• 422 unprocessable_entity — business-rule failure (for example, refunding more than the original charge).

Idempotency

Pass an Idempotency-Key header (UUID v4 recommended) to make retries safe. Keys are valid for 24 hours; see the idempotency guide.

curl -X POST "https://api.revkeen.com/v2/mandates/string/reinstate" \  -H "x-api-key: $REVKEEN_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "reason": "customer_request"  }'

{
  "data": {
    "id": "string",
    "status": "cancelled",
    "mandate_reference": "string"
  }
}