---
title: "Cancel Standing Order"
method: POST
path: "/cancel"
tags: ["Consumer"]
---

# Cancel Standing Order

`POST /cancel`

Cancelling a standing order requires user confirmation. The "Confirm" API is used to confirm a standing order action.

**SCA-enabled applications:** accepts a `verificationMethod` field (`sms`, `totp`, or `passkey`). All three factors are accepted for standing-order cancellation. Confirm the cancellation with the matching factor proof via `/standing-orders/confirm`. When using `passkey`, run `PASSKEY_APPROVAL_START` first.

## Request body

- CancelStandingOrderRequest
  - `userId` string, uuid, required — Unique ID of the user for whom the standing order is to be cancelled
  - `standingOrderId` string, uuid, required — The unique ID of the standing order to be cancelled
  - `verificationMethod` 'sms' | 'totp' | 'passkey' — SCA factor to issue the cancellation challenge against. Defaults to `sms` when omitted. All three factors are accepted. For `passkey`, run PASSKEY_APPROVAL_START before calling `/standing-orders/confirm`. Honoured only when the application has scaEnabled=true; ignored otherwise.

## Response `201`

success

- CancelStandingOrderResponse
  - `challengeId` string, uuid, required — Unique challenge ID to be used for cancelling this standing order
  - `dateExpires` string, date-time, required — Date at which this challenge ID expires. If this expires, please create a new cancellation request.
  - `verificationMethod` 'sms' | 'totp' | 'passkey' — SCA factor that the cancellation challenge is bound to.

## Other responses

- `400` — Bad Request. The request was unacceptable, often due to missing a required parameter.
- `401` — Invalid authentication header
- `500` — Unexpected server error.

---

[API](https://skmtc.net/striga/apis/striga-v1.md) · [All operations](https://skmtc.net/striga/apis/striga-v1/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/striga/striga-v1/revisions/63e57aa7df45/schema)