---
title: "Cancel payment (Pismo account ID)"
method: POST
path: "/cash-management/v2/payments/cancel"
tags: ["Payments (Pismo account ID)"]
---

# Cancel payment (Pismo account ID)

`POST /cash-management/v2/payments/cancel`

Cancel an existing payment operation.

NOTE:
- This endpoint requires an account token - an access token encoded with a Pismo account ID. Tokens can expire quickly, which can result in a `401 Unauthorized` message.

This endpoint generates the following events:
- [Platform authorization created](https://developers.pismo.io/events/docs/platform-authorization-platform-authorization-1)
- [Account balance changed](https://developers.pismo.io/events/docs/account-balances-balance-change-1)
- [Account balance changed (Availables)](https://developers.pismo.io/events/docs/availables-change-available-1)

Refer to [Data and reporting](https://developers.pismo.io/pismo-docs/docs/data-reporting-overview) for more information on events and setting up event notifications.

## Request body

- CancelPaymentV2Request
  - `original_tracking_id` string, required — Tracking ID for the original operation.
  - `tracking_id` string, required — Customer created tracking ID. Must consist of alphanumeric characters (a-z, A-Z, 0-9), hyphens (-), and colons (:), with a length from 1 to 128. The Pismo platform uses this field to implement idempotency and prevent duplicates.
  - `cancellation_method` 'INSTANT' | 'ORIGINAL_DATES' — Define the cancellation method used to determine which dates the cancellation will impact the account balance. * `INSTANT` (default): Cancels the payment using the current business date. * `ORIGINAL_DATES`: Cancels the payment using the original payment dates.
  - `skip_account_date_validation` boolean — If `FALSE`, the `payment_datetime` is validated against the account creation date and time. If `TRUE`, the validation is skipped.
  - `metadata` ConfirmPaymentMetadata — Key-value pairs containing data intended for storage in the Pismo system.<br> **Note**: This field must not be used to send Personally Identifiable Information (PII), Payment Card Industry (PCI) data, or any sensitive/regulated information. Metadata fields are intended for operational, non-sensitive data only. For sensitive data, use the specific parameters designed for that purpose. For more information, refer to [Get started with Pismo APIs](https://developers.pismo.io/pismo-docs/reference/get-started-with-pismo-apis).

## Response `201`

Created

- SettlementV2Response
  - `original_tracking_id` string — Tracking ID for the original operation.
  - `tracking_id` string — Customer created tracking ID. Must consist of alphanumeric characters (a-z, A-Z, 0-9), hyphens (-), and colons (:), with a length from 1 to 128. The Pismo platform uses this field to implement idempotency and prevent duplicates.
  - `event_datetime` string, date-time — Event date and time displayed in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format.<br> `minLength: 1` `maxLength: 30`

## Other responses

- `400` — Bad request
- `401` — Unauthorized
- `403` — The request has been lost
- `404` — Bad request
- `409` — Conflict
- `423` — Locked
- `500` — Internal server error

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/revisions/935b62e16de4/schema)