Refund transaction (proxy)
POST/api/v1/transactions/:id/refund
Refund a transaction by gross amount. A refund against a transaction with a tip requires an explicit refundedTipAmount allocation, including 0 if none of the gross refund is attributed to the tip. The allocation is not inferred. The tip and non-tip portions must each fit their remaining original balances after approved, pending, and in-doubt refunds.
Request
Responses
- 200
- 401
- 404
- 409
- 422
Refund processed successfully.
Missing or invalid bearer token.
Requested resource not found.
PAYMENT_IN_DOUBT is an unknown/pending monetary outcome, not a decline. The original operation may still complete. Retain the original key and request, query its status or replay that exact transaction request to recover the durable original result; never change the key or submit another payment. Other 409 codes (such as IDEMPOTENCY_CONFLICT) retain their own meanings.
Response Headers
Request is syntactically valid but cannot be processed.