Skip to main content
Create fiat deposit

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
ticker
string
required

Base currency ticker of the fiat currency. Use EUR.

Example:

"EUR"

provider
string
required

Fiat provider for the deposit: SEPA_BCB_GROUP, SEPA_CLEAR_JUNCTION, FINCI, or SEPA_FINSEI. Confirm the providers enabled for the account with the Asset Status endpoint.

Example:

"SEPA_BCB_GROUP"

amount
string
required

Deposit amount in ticker units. The amount must be within the minimum and maximum deposit amounts of the provider and the deposit limits of the account.

Example:

"100"

uniqueId
string
required

Unique deposit identifier on the client side. Any string up to 255 characters; must be unique for the account. Use the value to find the deposit in the deposit/withdraw history.

Maximum string length: 255
Example:

"a7d3c9e2-6f14-4b8e-9d21-3c5e7f9a1b04"

request
string
required

Request path. 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

Response

Deposit request created

depositId
string
required

Deposit identifier assigned by WhiteBIT.

uniqueId
string
required

The uniqueId from the request.

paymentDetails
object
required

Bank details for the transfer. The set of keys depends on the provider: SEPA_BCB_GROUP and SEPA_CLEAR_JUNCTION return beneficiary, iban, and bic. Other providers return provider-specific keys.