An overview of the adopted standards in the API

Conventions & Standards

Fiat amounts

In alignment with international standards, we utilize the ISO 80000-1 for representing amounts and the ISO 4217 for denoting currency codes in our API.

For deposits, payments, or transfers made in EUR, the amount is represented using a period as the decimal separator in accordance with ISO 80000-1. For instance, an amount of 100.50€ is represented as 100.50.

Simultaneously, the currency code is represented following the ISO 4217 standard, denoting EUR for Euro. The corresponding JSON response would be:

  "amount": "100.50",
  "currency": "EUR",

Please note that the amount field is a string to accommodate the point as a decimal separator. This approach ensures a consistent and internationally standardized representation of currency amounts and codes."

Cryptocurrencies amounts

Unlike traditional currencies that often use fixed decimal precision (e.g., two decimal places for cents), cryptocurrencies may have different decimal precision requirements. To accommodate this variability, our API employs a variable resolution approach. The resolution determines the number of decimal places used to represent cryptocurrency amounts accurately.

We provide an API endpoint that enables users to retrieve the current resolutions for each supported cryptocurrency. By accessing this endpoint, you can obtain the necessary information to handle cryptocurrency amounts accurately within your application. The current resolutions are subject to change over time due to factors such as protocol upgrades or community consensus. Therefore, it is essential to regularly update your resolution settings using the provided endpoint.

Example response:

  "BTC": 18,
  "ETH": 8,
  "LTC": 4,

In the example above, the response indicates that Bitcoin (BTC) requires 18 decimal places for accurate representation, Ethereum (ETH) requires 8 decimal places, and Litecoin (LTC) requires 4 decimal places. It is crucial to note that these resolutions are subject to change, and your application should dynamically adjust to reflect the current resolutions obtained from the endpoint.


Time representation in this API uses the Unix time format.

This format, also known as POSIX time or Epoch time, counts the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC) on Thursday, 1 January 1970, excluding leap seconds. This globally recognized standard is widely used in computing and data storage systems due to its universality and precision.

For example, September 20th 2022 13:36:25 GMT+0200 would be represented as:

  "created_at": 1663673785