Cryptocurrency Reference Guide

When integrating our API for handling payments with cryptocurrencies, it's crucial to provide accurate details to ensure smooth transactions. This guide will help you understand how to use the provided table of supported cryptocurrencies and how to include the necessary information in your API requests.

Supported Cryptocurrencies Table

The table below lists all the cryptocurrencies supported by our API along with their specific attributes:

crypto_currency_code	blockchain	cryptoTokenStandard	native	decimal_places
BTC	Bitcoin	-	true	8
BNB	BNB Chain	-	true	18
DOGE	Dogecoin	-	true	9
ETH	Ethereum	-	true	18
LTC	Litecoin	-	true	8
MATIC	Polygon	-	true	18
TRX	TRON	-	true	6
USDC	Ethereum	ERC20	false	6
USDT	TRON	TRC20	false	6
USDT	Ethereum	ERC20	false	6
USDT	BNB Chain	BEP20	false	6
XRP	XRP Ledger	-	true	18
TON	TON	-	true	9
USDT	Solana	SPL	false	6

Column Descriptions

• crypto_currency_code: The symbol or abbreviation of the cryptocurrency (e.g., BTC for Bitcoin).
• blockchain: The blockchain network on which the cryptocurrency operates (e.g., Ethereum, TRON).
• cryptoTokenStandard: The standard protocol for tokens on the blockchain (e.g., ERC20, TRC20). A dash (-) indicates that the cryptocurrency is native to the blockchain and does not use a token standard.
• native: Indicates whether the cryptocurrency is native to its blockchain (true) or a token (false).
• decimal_places: The number of decimal places used by the cryptocurrency. This defines the precision required when specifying amounts.

How to Use This Information in API Requests

When making API requests involving cryptocurrencies, you need to provide specific details based on the cryptocurrency you're using. Here's how to map the table data to your API request parameters:

1. Specify the Currency Code:

   • Use the crypto_currency_code in the currency field of your API request.
   • Example:

     {
       "cost": {
         "amount": "0.005",
         "currency": "BTC"
       }
     }

2. Include the Crypto Token Standard:

   • If the cryptocurrency is a token (native is false), you must include the cryptoTokenStandard field in your request.
   • Use the value from the cryptoTokenStandard column.
   • Example for USDT on TRON:

     {
       "cost": {
         "amount": "100.00",
         "currency": "USDT"
       },
       "cryptoTokenStandard": "TRC20"
     }
   • If the cryptocurrency is native (native is true), you do not need to include the cryptoTokenStandard field.
   • Example for ETH:

     {
       "cost": {
         "amount": "1.25",
         "currency": "ETH"
       }
     }

3. Set the Amount with Correct Precision:

   • Use the decimal_places value to format the amount field with the correct number of decimal places.
   • Example:
     • For BTC (decimal_places: 8), valid amounts could be "0.00012345" or "1.00000000".
     • For TRX (decimal_places: 6), valid amounts could be "100.123456" or "0.000001".

4. Avoid Ambiguity with Tokens on Multiple Blockchains:
   • Some tokens exist on multiple blockchains (e.g., USDT). Use the cryptoTokenStandard to specify which blockchain you're using.
   • Example:
     • For USDT on Ethereum:

       {
         "cost": {
           "amount": "75.00",
           "currency": "USDT"
         },
         "cryptoTokenStandard": "ERC20"
       }
     • For USDT on BNB Chain:

       {
         "cost": {
           "amount": "75.00",
           "currency": "USDT"
         },
         "cryptoTokenStandard": "BEP20"
       }

Sample API Request Structure

Here's how a complete API request might look when including cryptocurrency details:

• For a Native Cryptocurrency (e.g., BTC):

  {
    "cost": {
      "amount": "0.0025",
      "currency": "BTC"
    }
    // No cryptoTokenStandard field needed
  }

• For a Token Cryptocurrency (e.g., USDT on TRON):

  {
    "cost": {
      "amount": "100.00",
      "currency": "USDT"
    },
    "cryptoTokenStandard": "TRC20"
  }