IVMS101 Message Format Guide
Overview
IVMS101 is an open specification developed by the interVASP Messaging Standard working group, defining the data format on how to input the different types of personal information.
However, there are known limitations and VASPs sometimes struggle to input or interpret data for exchanging information.
In lieu of this, we augment the IVMS101 standard with the following guideline on how to input and interpret information in each case in order for seamless data exchange within the VerifyVASP alliance.
It is important that this guideline is followed comprehensively so that data between alliance members can be seamlessly exchanged. For cases not shown in the guide, please raise an issue or if you are already a member, engage us in your dedicated slack channel.
How to Input Information in Each Case
Reminder
A verification is performed for every transaction, you cannot enter information on multiple transactions into one verification.
How to Input Personal or Corporate Information
If there are multiple originators
Enter only one originator in IVMS101 format.
Multiple individuals or corporates cannot be input as originators of the same verification request.
If there are multiple originators, you have to make a verification request per originator.
Exception: For a corporate body, multiple inputs are allowed in originatorPersons because both the corporate information and the representative information are necessary.
In this case, both originators indicate one corporate body. Therefore, there is only one originator.
If there are multiple beneficiaries
Enter one beneficiary in IVMS101 format.
Two or more different individuals or corporates cannot be input as beneficiaries of the same verification.
If there are multiple beneficiaries, you have to make a verification request per each beneficiary.
Exception: For a corporate body, multiple inputs are allowed in beneficiaryPersons because both the corporate information and the representative information are necessary.
In this case, both beneficiaries indicate one corporate body. Therefore, there is only one originator.
If the beneficiary or the originator is a corporate body (legal person)
If a corporate body is legally acknowledged by Korean law, both the information of the corporate body and a representative must be entered both for originator and beneficiary.
Since there is no factor to enter the representative information in LegalPerson type of IVMS101, the representative information will be entered as below.
originatorPersons or beneficiaryPersons is a deployment of a Person type, so the first element of the deployment must be the corporate body (legal person) information.
Starting the second element, the individual (natural person) information of the representative is entered.
If there are multiple representatives, keep entering personal information of each representative after the deployment.
How to Enter Wallet Addresses
common
AccountNumber is case-sensitive text string.
If the address have a secondary address, such as a "note" or "destination tag" in XRP or EOS, write the address in the following format
"Parent Address:Memo" or "Parent Address:Destination Tag"
For more information about wallet address formats, please refer to Wallet address and transaction ID standards.
accountNumber of the originator
For originator's accountNumber, enter the sender's deposit address.
The sender's deposit address must be an address that uniquely identifies the originator.
If your VASP haven't issued a deposit address for the sender, then create a deposit address for the sender and enter it before making the withdrawal.
For assets that do not support a deposit address, enter a unique identification number assigned by your VASP that uniquely identifies the customer.
accountNumber of the beneficiary
In the accountNumber of the beneficiary, enter the actual blockchain address entered by the originator.
If there are multiple addresses, enter all of them.
How to Enter Names
Common
The names of NaturalPerson and LegalPerson are not deployments but single objects
Although the specification notes them as both deployments and single objects, it is more valid to interpret them as single objects.
The nameIdentifier factor of the name is a deployment.
If you would like to input multiple names, you can input them in nameIdentifier deployment.
At least one element in the nameIdentifier deployment must be a legal name. (LEGL type)
Trading with VASPs which supports non-English character names.
Name in local characters
If the official name is English (Foreigners or a corporate body), use the English name.
Trading with VASPs which supports English character names only
Name in English
If there is no English name in the member information, we suggest using the link below or similar official translation site for translation.
You can enter a local character name in localNameIdentifier. However, an English name must be entered in a nameIdentifier element.
When the last name and the first name can be separated
Enter the last name in the primaryIdentifier.
Enter the first name in the secondaryIdentifier.
When the last name and the first name cannot be separated
Enter the full name in the primaryIdentifier.
Do not enter anything in the secondaryIdentifier.
How to Enter a Geographical Address
Common
geographicAddress element is a deployment. Thus, you can enter multiple addresses.
One of the addresses must be GEOG, HOME, or BIZZ type address.
All addresses must be at least one of the following combinations below
At least one addressLine
streetName + buildingName
stressName + buildingNumber
country element is required, and you must enter a two-letter country code defined in ISO-3166-1 alpha-2.
For example KR, JP, US, SG etc
If the address information is divided into elements such as cities, do, states, street, and buildings.
In countrySubDivision element, enter cities and do (for Korean addresses).
For example Seoul, Gwangju, Gyeonggi-do, Jeju-do
In districtName element, enter cities, gun/gu (for Korean addresses).
In townName element, enter the town or up/myun/dong (for Korean addresses).
In streetName element, enter the name of the street.
In either buildingName element or buildingNumber element, enter the building name or number.
In the floor element or room element, enter a floor or room number.
If the address information is not saved into elements.
Since you can enter up to seven addresses as a deployment in addressLine, enter the address as an element of deployment if you have a divided one.
If you only know the full address, enter the full address as the first element of the addressLine deployment.
When entering the legal person's address
When entering the address of a legal person, both the address of the head office and the place of business must be entered.
The head office address is put as the first element in the geographic address array.
Put the business address as the second element in the geographic address array.
If you have multiple businesses, you can add them starting from the third element of the geographic address array.
Even if the address of the head office and the place of business are the same, duplicate them in the first and second elements respectively.
How to Enter Birth Date
Common
Do not enter birth date for a corporate body (legal person)
In dateOfBirth element, enter birth date in “YYYY-MM-DD” format.
In placeOfBirth element, place of birth must be entered
If you do not know the place of birth, enter the geographical address (current residence).
However, for a customer from a country which does not allocate a national identification number, then the place of birth is required.
Place of birth is important for countries without a national identification number.
How to Enter a Nationality
Common
Do not enter nationality for a legal person.
There is a format with a place of residence in IVMS101, but there is no format with a nationality.
In order to exchange nationality information, we added nationality in the NaturalPerson type by modifying the IVMS101 format.
Therefore, enter a country code in the nationality element.
Last updated