VASP Information Form (VIF)

Before moving to mainnet or requesting your VASP profile data to be verified/attested to, the Veriscope team will request you to complete a "VASP Information Form (VIF)." The VIF includes the same fields listed above and is used to check that the data posted to the discovery layer is accurate and correctly formatted. The VIF is available on request.

VASP Information Form

VASP profile data enables other VASPs to discover more information about a particular VASP, e.g.

  • Is the VASP verified?

  • In what jurisdiction is the VASP registered/licensed?

  • What’s the VASP endpoint for p2p data transfer?

  • How can I contact the VASP?

  • Etc.

VASP profile data fields (aka "key-value" pairs)

Data "key" Description

Trust Anchor Account Address

This is generated when a VASP installs Veriscope and is the address that needs to be funded with SHFT tokens to facilitate posting data to the discovery layer.

VASP Legal Entity Name

…​

Incorporation Date

Before moving to mainnet, Veriscope will request incorporation documents. Format: YYYY-MM-DD

VASP Operating Name

…​

Domain

Before moving to mainnet, Veriscope will request domain name registration documents.

API_URL

This is the endpoint at which a VASP will receive KYC templates and webhook events related to same. The API_URL must be set in order to receive data from other VASPs. The API_URL takes the format https://subdomain.domain.com/kyc-template where https://subdomain.domain.com/ is the VERISCOPE_SERVICE_HOST a VASP sets during the Veriscope installation phase.

Compliance Contact

Compliance contact for travel rule related queries. It is recommended to use a distribution list.

Technology Contact

Technology contact for travel rule related queries. It is recommended to use a distribution list.

Support Contact

Support contact for travel rule related queries. It is recommended to use a distribution list.

VASP Home Jurisdiction

…​

Regulated, Licensed, or Under Exemption in home jurisdiction

Choose one. Before moving to mainnet, Veriscope will request license/registration or exemption-evidencing documents, if applicable.

Regulatory or Licensing Body in home jurisdiction

…​

Public License or Registration URL on Regulator’s Website (if applicable)

URL to public registration

Exchange/OTC/Custodian

…​

Virtual Asset to FIAT Exchange Capabilities

Yes or No

Travel Rule Collection Requirements Policy

A document detailing the Originator and Beneficiary fields the VASP is required to collect, and any minimum transaction threshold over which travel rule data will be collected and/or exchanged.

Example

Data "key" Example "value"

Trust Anchor Account Address

0xb794f5ea0ba39494ce839613fffba74279579268

VASP Legal Entity Name

Acme Inc.

Incorporation Date

Format: YYYY-MM-DD

VASP Operating Name

ExchangeNow

Domain

https://acme.com

API URL

https://fatf.acme.com/kyc-template

Compliance Contact

[email protected]

Technology Contact

[email protected]

Support Contact

[email protected]

VASP Home Jurisdiction

Singapore

Regulated, Licensed, or Under Exemption in the home jurisdiction

Licensed

Regulatory or Licensing Body in the home jurisdiction

https://www.mas.gov.sg/

Public License or Registration URL on Regulator’s Website (if applicable)

<URL to public registration>

Exchange/OTC/Custodian

Exchange

Virtual Asset to FIAT Exchange Capabilities

Yes

Travel Rule Collection Requirements Policy

https://acme.com/fatf

Adding VASP profile data

VASP profile data can be added & updated via the Veriscope web application, as illustrated below. Each data point is referred to as a key-value pair, the key being the name of the field and the value being the VASP input.

Alt text
After posting data, you can check the Shyft block explorer to make sure it was added to the network as expected. See Veriscope Chains and Smart Contracts for links to the various block explorers.