---
title: "Refund a specific voucher charge"
method: POST
path: "/charges/{id}/refund"
tags: ["Charges"]
---

# Refund a specific voucher charge

`POST /charges/{id}/refund`

This call is used to (partial) refund a specific charge that was previously done on a voucher (for example if a customer returns goods to the store).

## Path parameters

- `id` string, required

## Request body

- object
  - `amount` string, required — Amount in the currency of this voucher. Must be send as string in the following pattern: * Greater or equal than 0.01 * Less than the Charge Amount * Up to five digits before the decimal point * The decimal point (.) * Exactly two digits after the decimal point
  - `currency` string, required — The three-character ISO-4217 currency code - https://en.wikipedia.org/wiki/ISO_4217#Active_codes (must match the currency of the voucher)

## Response `201`

OK

- object
  - `id` string — Primary identification key - will be used in voucher-charge calls
  - `voucher_id` string — Voucher primary identification key (see voucher -> id)
  - `client_id` string — Client primary identification key (see client -> id)
  - `type` 'charge' | 'recharge' | 'refund' — Type of this charge. Can either be "charge", "recharge" or "refund"
  - `amount` string — Amount in the currency of this voucher. Must be send as string in the following pattern: * Up to five digits before the decimal point * The decimal point (.) * Exactly two digits after the decimal point
  - `order_number` string — Order or invoice number of the transaction
  - `created_at` string, RFC3339 — created_at - datetime in RFC3339 format, see https://tools.ietf.org/html/rfc3339
  - `updated_at` string, RFC3339 — updated_at - datetime in RFC3339 format, see https://tools.ietf.org/html/rfc3339

## Other responses

- `403` — The request contained valid data and was understood by the server, but the server is refusing action.
- `404` — The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.
- `422` — The request was well-formed but was unable to be followed due to semantic errors.

---

[API](https://skmtc.net/jtl-software/apis/scx-authentication-api.md) · [All operations](https://skmtc.net/jtl-software/apis/scx-authentication-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/jtl-software/scx-authentication-api/revisions/f979b1ea6951/schema)