---
title: "Send test authorization reversal request"
method: POST
path: "/v1/authorizations/reversal"
tags: ["test-authorizations"]
---

# Send test authorization reversal request

`POST /v1/authorizations/reversal`

## Query parameters

- `auditUser` string, required

## Request body

- ReversalRequest — Reversal request
  - `id` string, required — Unique identifier of authorisation request.
  - `partialAmount` Money — Amount including currency
    - `amount` number
    - `currency` string — A valid ISO 4217 currency code

## Response `200`

Reversal request succesfully executed

- AuthResponse — Response on the authorisation request.
  - `metadata` object, required
    - `mti` string, required — Message type indicator for authorisation message.
    - `id` string, required — Unique identifier of authorisation request.
  - `transactionData` object, required
    - `authResponseCode` string, required — Response to the authorisation. Indicates to the merchant if the authorisation was approved or declined.
    - `retrievalReferenceNumber` string, required — Merchant/acquiring generated reference number for a purchase. Commonly used as the one of the main variables, in addition to cardId, to uniquely identify a transaction. Reference number is expected to remain the same for all messages during the transaction lifecycle (authorisation, clearing, reversals). This information can be used as one variable to match the authorisation message to purchase receipt data.

## Other responses

- `400` — Bad request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `500` — API is having problems

---

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