POST/v2/sandbox/transaction/chargeback

Chargeback Transaction

Charges back an authorized fiat payout in the sandbox environment, simulating a returned payment.

Supports domestic USA payouts (ACH, domestic wire, international wire) and cross-border payouts. Deposit transactions are not supported.

The payout must belong to the calling merchant and must already be fully authorized. If it does not belong to the merchant, returns 404 Transaction Not Found. If it is not fully authorized, returns 404 Transaction not authorized. Already charged-back transactions return success.

Sandbox environment only — not available in production.

Headers

Field	Type	Required	Possible values	Description
`Authorization`	string	Required	Bearer {SessionToken}	Session token from Get Session Token, sent as `Authorization: Bearer {SessionToken}`. Replace with the value from the `x-refresh-token` response header when present (typically within 2 minutes of expiry). Secured calls must use the same IP as the auth request.

Request body

Field	Type	Required	Possible values	Description
`TransactionNumber`	string	Required	{transactionNumber}	Transaction number of the authorized sandbox payout to charge back.

Example request

{
  "TransactionNumber": "{transactionNumber}"
}

Response

Field	Type	Possible values	Description
`ResponseCode`	integer	200 \| 201 \| 204 \| 400 \| 401 \| 403 \| 404 \| 410 \| 422 \| 500 \| 301 \| 503 \| 422	API result code in the response envelope. Indicates success or the error category (e.g. 200 success, 400 bad request, 401 unauthorized).
`ResponseMessage`	string	Success \| Created \| NoContent \| BadRequest \| Unauthorized \| Forbidden \| NotFound \| Gone \| UnprocessableContent \| ServerError \| ResourceMoved \| ServiceUnAvailable \| UnProcessableEntity	Human-readable label paired with ResponseCode (e.g. Success, BadRequest, Unauthorized). Use with ResponseCode to interpret the outcome.
`ResponseData`	object	Please refer to below example for response body	Result message for the chargeback attempt.

Example response

{
  "ResponseCode": 200,
  "ResponseMessage": "Success",
  "ResponseData": {
    "Message": "Transaction successfully charged back"
  }
}

Error responses include 404 with "Transaction Not Found." (missing, unsupported type, or not owned by the merchant) and 404 with "Transaction not authorized" (not fully authorized).

Requires `Authorization: Bearer {SessionToken}` from Get Session Token. Refresh via `x-refresh-token` when supplied; use the same client IP as authentication.