Update Refund

PATCH /accounting/refunds/{id}

Group: Accounting › Refunds · Operation ID: updateRefund

Updates the refund with the given identifier. Only the fields in the request body change. Use the refund's id, not its refundNumber.

Only the fields in the request body change. Everything omitted is left unchanged. Only an unapproved refund can be updated: a refund created through POST accounting/refunds is approved automatically, so this endpoint succeeds only on a refund still in draft, pendingApproval or revise. Updating an already-approved refund fails with REFUND_ALREADY_APPROVED and changes nothing. Issue a new refund instead. customerId, entityId, paymentId and currency are not updatable. The response contains the updated refund's header fields.

Open in the interactive reference

Parameters

Name	In	Type	Required	Description
`Api-Version`	header	`"v1"`	yes	The API version this request targets, named by its public identifier. Required on every request; omitting it, or naming a version this company does not have, is answered with 400. This document describes version `v1`.
`Idempotency-Key`	header	string	no	An opaque caller-chosen string (1-255 characters) that makes this request safe to retry. Repeating the same key with an identical request body replays the original response instead of re-executing - but only once that original request succeeded; a failed attempt re-executes on retry. Repeating the key with a different body is answered with 422. A key still in flight is answered with 409 - as is a key whose original request was interrupted before it finished, for a few minutes afterwards, until that attempt is presumed dead. A completed response stays replayable for 24 hours. The key is scoped to the caller, not to the action: reusing it for a different action is answered with 409 or 422 rather than treated independently. On read actions this header is ignored. On write actions that cannot offer the guarantee it is answered with `400 IDEMPOTENCY_NOT_SUPPORTED` rather than silently ignored.
`id`	path	string	yes	The unique identifier for the refund to update.

Request body

Required, application/json: updateRefundInput.

Field	Type	Required	Description
`refundDate`	string (date)	no	The new issue date. Use format YYYY-MM-DD. Must fall in an open accounting period. Omit to leave it unchanged.
`refundType`	string, one of `"check"`, `"ach"`, `"wire"`, `"creditCard"`, `"directDebit"`, `"sepaCreditTransfer"`	no	The new payment method. Omit to leave it unchanged.
`refundNote`	string	no	A new free-form note. Omit to leave it unchanged.
`amount`	string (decimal)	no	The new refund amount, in the refund currency. Must be greater than 0. Omit to leave it unchanged.

Example:

{
  "refundDate": "2026-01-15",
  "refundType": "check",
  "refundNote": "<refundNote>",
  "amount": "175.00"
}

Response

200 Success

Under data (updateRefundOutput):

Field	Type	Required	Description
`id`	string	yes	The unique identifier for the refund.
`refundNumber`	string	no	The refund number, unique within the tenant, for example 'REF-1042'.
`refundDate`	string (date)	yes	The date the refund was issued. Format YYYY-MM-DD.
`approvalStatus`	string	no	The approval status after the change. Possible values: 'draft', 'pendingApproval', 'revise', 'approved', 'rejected'.
`refundType`	string	yes	The payment method used for the refund. Possible values: 'check', 'ach', 'wire', 'creditCard', 'directDebit', 'sepaCreditTransfer'.
`currency`	string	yes	The currency of the refund. Every amount on it is in this currency. Format ISO 4217, for example 'USD'.
`amount`	string (decimal)	yes	The refund amount, in the refund currency.
`customerId`	string	yes	The customer receiving the refund. See id on GET accounting/customers/:id.
`entityId`	string	yes	The legal entity issuing the refund. See id on GET base/entities.
`paymentId`	string	yes	The source payment being refunded. See id on GET accounting/payments/:id.
`lastModifiedDate`	string (date-time)	yes	The date and time the refund last changed, in UTC. Format YYYY-MM-DDTHH:mm:ss.sssZ.

Response headers

Idempotency-Replayed — Present and true only when this response replays a previously stored one for the same Idempotency-Key, rather than reflecting a live execution. Absent on a live response - never sent as false.

Errors

Code	Status
`NOT_FOUND`	400
`REFUND_ALREADY_APPROVED`	400
`INVALID_AMOUNT`	400
`IDEMPOTENCY_KEY_CONFLICT`	409
`IDEMPOTENCY_PAYLOAD_MISMATCH`	422

Statuses

400 — Invalid request or business failure. Codes: NOT_FOUND, REFUND_ALREADY_APPROVED, INVALID_AMOUNT
401 — Missing or invalid access token
403 — Not authorized
404 — Not found
409 — The Idempotency-Key is still being processed by another request.
422 — The Idempotency-Key was already used with a different request payload.
429 — Too many requests
500 — Internal server error