Verify Via Email

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 second method.

1. What is the 3rd Party Verification?

When talking about the transfer of virtual assets, what becomes obstacles to the service providers is that when user wants transfer to the unhosted wallets owned by someone else. This is because the 'Travel Rule' requires ID verification of recipient, but as the nature of non-custodial unhosted wallets, the owner of the wallet stays anonymous.

As mentioned above, the 3rd party verification is checking the identity of the other person(3rd party) when trying to transact or interact with them.

ARGOS ID supports identity authentication by sending emails to third parties in such cases. Be reconnected with your users with ARGOS ID!

2. Example of UX Process

The 3rd party verication is also a process to whitelist wallets for virtual asset transfer and it will be combined to client(VASP)'s service.

If a user wishes to transfer assets to non-custodial wallet owned by someone else, the someone else who will recieve the asset have to identify his id and wallet address.

STEP 1 is a process for the VASP and user where the VASP should gain the 3rd party(counterpart of the transfre)'s email address and send a 'request' to ARGOS ID through POST/idverify API.

STEP 2 is for ARGOS ID and the 3rd party user to perform where ARGOS ID sends an email with a button and user verifies.

STEP 3 is where the VASP clarifies the verified 3rd party information and builds own transfer processes. At this point, multiple 'request' can be created for single 3rd party's email, so what we recommend is use 'rid(request id)'. VASP should build own numbering system of the request id, each 'REQUEST' should have unique value.

3. Flow Architecture

Now, let's see what actions need to be taken by VASP, ARGOS ID and user at each phase - adding whitelist, withdrawal and deposit process when using email method.

Phase 1. Add a Whitelist Address

1. First, service provider(VASP) should obtain the counterpart's email (and name) from user

2. VASP sends a API request containing data aquired from No. 1

3. ARGOS ID sends an email with ARGOS ID button to the counterpart

4. The counterpart user(3rd party user) who received the email verifies id, wallets and make consent.

5. When verification is completed, ARGOS ID will send a webhook to VASP

6. VASP who received a webhook will request ARGOS ID for verified data

7. ARGOS ID will transfer the requested data

8. VASP whitelists the wallet addresses

Phase 2-a. Withdrawal

1. User applies for transfer of virtual assets to the whitelisted wallet.

2. VASP makes transfer and reflect the transaction on their system.

Phase 2-b. Deposit

1. User transfers virtual asset from one's personal wallet to custodial wallet.

2. VASP checks if the personal wallet address is on the whitelist.

3. When NO: Return the asset or let the user proceed the phase 1.

4. When YES: Reflect the transaction on VASP's system.