Skip to main content
Refund a deposit

Used in these guides

Authorizations

X-TXC-APIKEY
string
header
required

The public WhiteBIT API key.

X-TXC-PAYLOAD
string
header
required

Base64-encoded JSON request body.

X-TXC-SIGNATURE
string
header
required

HMAC-SHA512 signature of the payload, hex-encoded. Computed as hex(HMAC-SHA512(payload, api_secret)).

Body

application/json
transactionId
string<uuid>
required

Transaction UUID of the deposit. Obtain from the deposit.canceled webhook (uniqueId field) or from the deposit/withdraw history in the WhiteBIT interface.

Example:

"54bffeb7-7a8f-43f8-bcd8-f14ec10fee85"

address
string
required

Destination wallet address for the refund. The address must support the same network and asset as the original deposit. Cannot be a WhiteBIT address. Does not have to match the original deposit address.

Example:

"0x1234567890abcdef1234567890abcdef12345678"

request
string
required

Base64-encoded request body. See the authentication guide for signature generation details.

Example:

"{{request}}"

nonce
integer
required

A unique identifier for the request. Use a monotonically increasing value such as a Unix timestamp in milliseconds.

Example:

1594297865000

memo
string

Destination memo for the refund address. Optional — without it, the refund goes to the address with no memo.

For a currency that uses memos, the system validates the value; an invalid memo fails the request with a validation error. For other currencies, the value is not validated. It is stored on the refund and returned in the refund history and in the refund webhooks.

Maximum string length: 255
Example:

"1234567890"

Response

System accepts refund request

id
string<uuid>
required

Transaction UUID of the deposit, echoed from the request. This is not a refund identifier — the refund's own refundId is returned by Get refund history.