Changelog
Last updated
Was this helpful?
Last updated
Was this helpful?
Businesses can now choose which specific network they want to allow for any of the deposit currencies. This applies to currencies where multiple deposit networks are supported.
Added the ability to configure which party is responsible for covering the on-chain fees when sending out a settlement. This can be configured once for all withdrawals created from a given business on each individual withdrawal.
Added the ability to require an approval from a second user before sending out a withdrawal. This configuration is made once for each organisation and applies to all subsequently sent withdrawals.
Solana
has been added as supported network for crypto withdrawals and deposit for USDC.
Furthermore we also added SOL
as deposit and withdrawal currency.
Added the withdrawal approvals feature allowing admin users to have additional control over crypto withdrawals by manually approving or rejecting them.
Adding statuses to deposits in payments. Changes to the response are visible under .
List of currencies and their supported deposit networks
USDC
Ethereum chain (ETH), Binance Smart Chain (BSC) and Tron Chain (TRX)
ETH
Ethereum chain (ETH) and Binance Smart Chain (BSC)
USDT
Ethereum chain (ETH), Binance Smart Chain (BSC) and Tron Chain (TRX)
BTC
BTC
BCH
BCH
LTC
LTC
XRP
XRP
XLM
XLM
LINK
ETH
MAIN
is no longer a valid value for the network field instead, use one of the values described on the Request crypto withdrawal page.
Added a new field maxAmount
to the response. It will hold the maximum amount that can be withdrawn in the respective cryptocurrency.
BTC
BTC
MAIN
BCH
BCH
MAIN
ETH
ETH, BSC
MAIN, BSC
LINK
ETH
MAIN, BSC
LTC
LTC
MAIN
USDC
ETH, BSC, TRX
not supported
USDT
ETH, BSC, TRX
MAIN, BSC, TRX
XLM
XLM
MAIN
XRP
XRP
MAIN
B2BPay will cease processing (deposits and withdrawals) of the following currencies as of 2022-07-15:
Reason for delisting is low processing volumes and low liquidity on the markets.
New supported network - TRX
New optional field for the request body - network
New field in the response body - network
New endpoint that provides metadata for all supported cryptocurrencies
We are deprecating the old endpoint and introducing a new one:
POST /api/v1/addresses/validate
is being Deprecated
GET /api/v1/currency/:withdrawalCurrency/network/:network/address/:address/valid
- New
New endpoint that provides rates for currencies(fiat and crypto) and supports comma-separated values.
New status -BLOCKED
New field - txAddressOwner
New status - BLOCKED
New fields - addressOwner
, sourceRiskEntities
, destinationRiskEntities
Adding a network field as a mandatory one to the post request for whitelisted address creation. Currencies and networks pairs available are the same as for our .
Introducing deposits through side chains. To take advantage of this new feature changes should be made to either the or the payload.
Changes to the accepted values for the network field for
Added a maximum amount the can be withdrawaln depending on the network and the respective cryptocurrency. Information can be found in the .
Different response fields when sending . For payments with LTC
as their depositCurrency
the response will only include a walletAddress
field. We are removing the ltc3Address
field and changing the address type that is returned in the walletAddress
.
Changes to our .
The changes to network names that are described on the page will also take affect here (see table below and ).
Changes to the network field in the endpoint
request body and response body
request body and response body
for any currency
request body
response