SANDBOX - v2.1.2 - 2024-05-06
Summary
Groovy news! 💣
Say hello to the newest chain, BASE, which is available from now on!
The BASE is EVM L2 chain and supports the USDc token. 🎉🎉🎉
What is more, now we are supporting smart contract logins on sandbox environment for all chains! ⛓️⛓️⛓️
👀 Current release also incorporates a feature that allows to create more than one account with the same email for a user and corporate.
We've implemented modification for a splitting the users' signing_address
and target_address
, so the users have the ability to set up new signing address. For backwards compatibility by default all signing_address
if left blank are filled with target_address
. ❗ Moreover as part of migration signing_address
has been populated with existing target_address
❗🐱💻
One of the changes is the adjustment for the scenario when the crypto transfer fails. The webhook's subtype: FAILED
is replaced by ➡️ subType: PENDING
Along with this release, we worked on a few improvements for endpoint schema and responses.
Upgrade was implemented for User - Management and Informative. 🚀
This release will go into the production environment in one week's time (Monday, 13th May 2024).
Added
N/A
Changed
- [SANDBOX] PATCH / KYC verification status We've added to the endpoint rejections reasons, so is possible to set them up and test according to your needs
- GET / KYC application details We've adjusted 200 status code message, so now you will be informed about specific type of the document that is missing
- PATCH / Update a user Given the scenario, when the user provides an on-ramp wallet address which matches with the off-ramp wallet address, as a response you will get the 400 status code with message
target_address must not be equal to the withdrawal address
. On top of that we added a sign_in_crypto_address as an extra input field - GET / The token preferences and GET / The token preferences of a corporate - 200 status code response adjusted with base
- POST / Create a user - Added base as possible chain then selecting token preferences and sign_in_crypto_address as an extra input field
- PATCH / Update corporate token preferences POST / Create a user and PATCH / Update user token preferences - Added base as possible chain then selecting token preferences
- GET / Corporate Unblock Bank Account GET / User Unblock Bank Account GET / All user unblock bank accountsGET / All Corporate Unblock Bank Account - updated documentation with bank_country in response instead of country to align with the existing code response
Deprecated
N/A