Verify Via Button
Last updated
Last updated
There are two ways to authenticate with ARGOS ID.
The first is to add ARGOS ID 'button' during the client's UX process, which can be used mainly when the user needs to verify his own wallets. The second is to send an email containing ARGOS ID 'button' to the counterpart of the transfer, this can be used for not only the verification of user's own wallets but also for the 3rd party user transactions.
At this page, we will take a look at the first method.
ARGOS ID is built with modal window and websocket to melt into clients' UX in seamless way. Our customers have flexibility on when and where to integrate ARGOS ID.
On this page, we'd like to take an example on 'How to integrate ARGOS ID' for you to understand better.
From a bic picture perspective ARGOS ID is a process to whitelist wallets for virtual asset transfer and it will be combined to client(VASP)'s service. You can add this process to transfer section or managing user account, but eventually the service provider(our client) shall provide seperate page and button to users and let them proceed the whitelisting.
STEP1 is the service providers(VASPs)' work to do, to create a button for users to add thier personall wallet address to whitelist. At this time, it is up to the VASPs to build seperate page or not but generating an ARGOS ID button is mandatory. If you have decided to go with only the button, you can simply add it on the transfer UI.
STEP2 is users' work to do. After clicking the button created from STEP1, ARGOS ID modal will show and the authentication process will begin. It includes verifying ID, wallet addresses and consenting on data provision to the 3rd party. When completed, users are all done.
SETP is for VASPs' again. Make use of the data acquired from step2 and build Travel Rule compliant process.
Let's take a look at the actions taken by VASPs(service providers), ARGOS ID and users respectively at stages of whitelisting, withdrawal and deposit.
First, VASP should integrate ARGOS ID with their system and UX, create a button to connect ARGSO ID and user.
When the modal window is called, ARGOS will request users on verification of ID and wallet addresses, consent on data provision.
Users allow for data transfer to the 3rd party(VASP).
ARGOS will send a webhook to VASP for notification.
VASP send request to ARGOS for user data through API.
ARGOS send requeted user data to VAS through API.(Including Id info & wallet addresses)
VASP add the wallet addresses on the whitelist.
User applies for transfer of virtual assets to the whitelisted wallet.
VASP makes transfer and reflect the transaction on their system.
User transfers virtual asset from one's personal wallet to custodial wallet.
VASP checks if the personal wallet address is on the whitelist.
When NO: Return the asset or let the user proceed the phase 1.
When YES: Reflect the transaction on VASP's system.
