Robot VASP

It is essential to keep all the members in the same information format as an information transfer service. We created a Robot VASP ( VASP Code ROBOTWAA) to examine data formats in each transfer is perfectly aligned in the test environment before members pushing their services onto the production level.

The Goal of the Robot VASP testing

• Check if the personal data is encrypted correctly before sending it out.
• Check if the personal data format is compatible with the IVMS101 data standard.
• Check if the beneficiary name provided by the originator VASP matches the beneficiary VASP database. (As User-code is entered correctly on the originator VASP interface)
• Check if the originator VASP stops sending the transaction if the beneficiary VASP rejected the transfer.
• Checking if there is any network issue.

Test Cases

As an originator VASP

1. Send a BTC transfer request to a natural person beneficiary Samuels Brenden registered in Robot VASP. Once approved by the beneficiary VASP, send a random transaction ID to finish the test case.
   wallet address: 1KFHE7w8BhaENAswwryaoccDb6qcT6DbYY
   name primary identifier: Smith
   name secondary identifier: John

2. Send a USDT - ERC20 transfer request to a legal person beneficiary VASP-com registered in Robot VASP. Once approved by the beneficiary VASP, send a random transaction ID to finish the test case.
   wallet address: 0xb42a0E88F7Ccb0fa119E9d3AD79Cbb0630da9C2B
   name primary identifier: VASP-com

3. Send an XRP transfer request to a natural person beneficiary Alice Andrew registered in Robot VASP. Once approved by the beneficiary VASP, send a random transaction ID to finish the test case.
   wallet address: rhhh49pFH96roGyuC4E5P4CHaNjS1k8gzM
   tag: 1440
   name primary identifier: Andrews
   name secondary identifier: Alice

🚧

The Naming Format in Primary Identifier and Secondary Identifier

In the definition of IVMS101, there are two ways to format a natural person's name. The first is to put the last name into PrimaryIdentifier and first name into SecondaryIdentifier like test case no.1. The second way is to put the full name into PrimaryIdentifier like test case no.3. It is required to be compatible with both approaches because each beneficiary VASP could have a different design.

As a beneficiary VASP

📘

Robot VASP Switches Role

Robot VASP will switch its role to originator VASP to initiate new test cases when finished the test case as a beneficiary VASP.

4. Accept the BTC transfer request from Robot VASP if the beneficiary name and wallet address information are matched within your database.

5. Reject the USDT - ERC20 transfer request from Robot VASP when the beneficiary name is not matched within your database.

6. Reject the XRP transfer request from Robot VASP when the wallet address is not matched within your database.

Notes

This is a test robot, but, the information will still be kept inside our database. Thus, for security measures, please do not send real user data to Robot VASP.