We are very excited to present you the biggest upgrade in our system of the last few months, and one we are sure you'll absolutely love!

This upgrade addresses some of the most common issues our customers were experiencing, and we are sure it will greatly improve your experience, as well as open up many new use-cases.

Let's start with the simplest one:

UUID on payments

Applicable to: all supported coins

A new field has been added to the sent callbacks and logs, called uuid. This is an unique identifier to each payment your clients have made, so you can easily track any duplicate callbacks sent, in the case our system doesn't mark the callback as successful.

Multi-chain addresses

Applicable to: ETH and BSC chains
Options: 0 or 1
Default: 0

A new optional parameter for ETH/ERC20 and BSC/BEP20 address creation requests has been added, called multi_chain. This parameter creates the same address_in on both chains, allowing you to receive payments on both.

Unless used together with multi_token, this address will only be valid for the token specified (eg. USDT). If our system doesn't support the token on the "extra" chain, it will only be created on the main chain (the one you requested). For instance, our service doesn't support DOGE over ERC20, so creating an address on /bep20/doge/ with multi_chain=1 (without multi_token also set) will not create the address on ERC20.

Attention:

When setting this parameter you should make sure your wallet address (address_out) supports payments also on both chains, as the funds will be forwarded to the same address (or addresses). CryptAPI cannot reverse any payment sent through a chain unsupported by your wallet.

Multi-token addresses

Applicable to: ERC20, BEP20 and TRC20
Options: 0 or 1
Default: 0

A new options parameter for ERC20, BEP20 and TRC20 address creation requests has been added, called multi_token. This parameter allows the same same address_in to receive payments in any token supported by our system.

Unless used together with multi_chain, this will only accept payments on the tokens of the chain it was created on. If used together with multi_chain on ERC20 or BEP20, means you will be able to accept payments on any token supported by our system on both chains.

Attention:

When setting this parameter you should make sure your wallet address (address_out) supports the tokens you expect your clients to pay with. CryptAPI cannot reverse any transaction any payment of a token unsupported by your wallet.
When setting this parameter means your clients can pay on any token supported by our system, even tokens with very different prices, so your system should check the coin field and make the appropriate price conversions. If you wish to receive 1000 USDT (or equivalent) and your client sends 1000 DOGE, your system should be able to handle that scenario.

We are certain that these changes will benefit you by giving more options to your clients and make it easier for you to handle the issues of when your clients send different tokens or on different chains (which up until now had to be forwarded manually by our team).

If you have any feedback regarding these changes or any suggestion, please let us know!

CryptAPI Team