--- title: "Create a void" method: POST path: "/void/{id}" tags: ["Voids"] --- # Create a void `POST /void/{id}` Cancels a payment authorisation before it is captured, releasing the amount held on the card. Works for **single** and **frequent** authorisations. **Required scope:** void:create ## Path parameters - `id` string, uuid, required ## Request body - VoidPostRequest - `descriptive` string, required — Free-text reason for the void. Required, up to 255 characters. This will appear in the bank statement / MB WAY application. - `transaction_key` string — Optional. Your own internal key identifying this void, up to 50 characters. Echoed back on the void details. ## Response `201` Created - VoidPostResponse - `status` string - `message` string[] — An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request. - `id` string — A unique identifier for the resource. While typically formatted as a UUID (Universally Unique Identifier), it can also be in other formats as defined by the user. This field ensures the resource can be distinctly recognized and referenced. ## Other responses - `400` — Bad Request - `403` — Forbidden - `404` — Not Found - `412` — Pre condition failed - `429` — Too Many Requests - `500` — Internal Server Error --- [API](https://skmtc.net/easypay/apis/easypay-payments-api.md) · [All operations](https://skmtc.net/easypay/apis/easypay-payments-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/easypay/easypay-payments-api/versions/cdf25a9ad7b2/schema)