End-to-end walkthough using the Postman Collection

The following demonstrates an end-to-end walkthrough of the flow from attestation through to decrypting IVMS data and accepting/rejecting a transfer.

Initial set-up

Two active testnet Nodes were used:

If you are conducting a similar test, check that your Nodes are running at fedstats.veriscope.network and refreshed with all blockchain data before getting started.

Two users were created before getting started (covered in the next page):

And the destination (bUser) wallet address was taken to be:

  • coin_blockchain: ETH

  • coin_token: USDC

  • coin_address: 0x5481fabc980af705c556517426c81a963af5657d

Overview of the end-to-end flow

end-to-end flow example
Step VASP Task

1

oVASP

Post attestion. The attestation is posted to all nodes as a webhook event.

2

bVASP

Receive attestation

3

bVASP

Create and send initial KYC template with signature data

4

oVASP

Receive initial KYC template

5

oVASP

Encrypt KYC/IVMS data with bUser’s public key

6

oVASP

Send updated KYC template with signature data and encrypted KYC/IVMS data

7

bVASP

Receive updated KYC template with encrypted KYC/IVMS data

8

bVASP

Encrypt KYC/IVMS data with oUser’s public key

9

bVASP

Send updated KYC template with encrypted KYC/IVMS data. The encrypted KYC/IVMS data must be before a status code can be sent.

10

oVASP

Receive updated KYC template

11

oVASP

Decrypt bVASP KYC/IVMS and perform checks (e.g. name screening) and decide whether to proceed (accept/reject the transfer)

12

oVASP

Send updated KYC template with accept/reject status code

13

bVASP

Decrypt oVASP KYC/IVMS and initiate additional checks (e.g. name screening)

14

bVASP

Send updated KYC template with accept/reject status code

15

oVASP

Process the withdrawal / broadcast on-chain