Cancel BACS mandate [beta]
Cancel a BACS direct debit mandate.
Cancel of an existing mandate, applied asynchronously through the BACS scheme.
Notes:
-
The cancel is persisted with status = CANCEL_PENDING under the payer account, and enqueued for the asynchronous submission worker, which submits it to Form3 through the PSP gateway.
-
Allowed only when the mandate is in SUBMITTED or CONFIRMED; any other state is rejected with a 409 Conflict (EBACS0103).
-
version is a Form3 optimistic-concurrency passthrough that must equal the stored version; a mismatch is rejected with a 409 Conflict (EBACS0104). This call does not increment it.
-
The optional status_reason records why the mandate is being cancelled; it is persisted on the mandate and forwarded on the generated event.
-
This endpoint moves the mandate to status = CANCEL_PENDING and generates a BACS mandate status changed event. Subsequent status transitions generate further events (for example CANCELLED, FAILED).
Request
- Base URLhttps://sandbox.pismolabs.io/bacs
- URLhttps://sandbox.pismolabs.io/bacs/v1/payments/bacs/directdebit/mandates/{id}/cancel
- Authnone declared. Required headers: Authorization
Path parameters
Mandate ID (the Form3-assigned ID returned at creation).
Headers
Account token - access token encoded with a Pismo account ID. Tokens can expire quickly, which can result in a <b>401 Unauthorized</b> message
Request body
Example request
{
"status_reason": "account_closed"
}Response
Cancel intent accepted and enqueued
Example response
{
"id": "b254bb5e-6f1a-4c2b-9c1e-2f0a6d3e8c11",
"status": "CANCEL_PENDING"
}Changes
No recorded changes to this operation across all 1 revision of this API.