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 as a Google Form here.

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.

This data can be attested to by third party verifiers and other trust anchors (VASPs) on the network.

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

Data "key" Description

Trust Anchor Account Address (e.g. 0xB3f40Ea260d4616eAB7CfE546FeB52C38bC85660)

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.

LEGAL_ENTITY_NAME

…​

LEGAL_ENTITY_IDENTIFIER_LEI

…​

INCORPORATION_DATE

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

INCORPORATION_JURISDICTION

…​

INCORPORATION_NUMBER

…​

WEB_DOMAIN

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

OPERATING_NAME

…​

REGULATED

Is the VASP regulated? (Y/N)

LICENSE_OR_REGISTRATION_NUMBER

…​

REGULATION_BODY

…​

REGULATION_BODY_URL

URL to regulation body

CONTACT_COMPLIANCE

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

CONTACT_TECHNICAL

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

CONTACT_SUPPORT

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

CONTACT_LEGAL

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

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.

TR_PROTOCOL_CIPHERTRACE

Does the VASP support the CipherTrace (Traveller) protocol

TR_PROTOCOL_TRISA

Does the VASP support the TRISA protocol

TR_PROTOCOL_TRP

Does the VASP support the TRP protocol

TR_PROTOCOL_TRUST

Does the VASP support the TRUST protocol

TR_PROTOCOL_SYGNA

Does the VASP support the Sygna protocol

TR_PROTOCOL_VERIFY_VASP

Does the VASP support the VerifyVASP protocol

TR_PROTOCOL_VERISCOPE

Does the VASP support the Veriscope protocol

Example

Data "key" Description

Trust Anchor Account Address

0xB3f40Ea260d4616eAB7CfE546FeB52C38bC85660

LEGAL_ENTITY_NAME

Acme

LEGAL_ENTITY_IDENTIFIER_LEI

OKSQ00JBSYMOYAFHZN90

INCORPORATION_DATE

2014-04-01

INCORPORATION_JURISDICTION

SG

INCORPORATION_NUMBER

123456789

WEB_DOMAIN

https://acme.com

OPERATING_NAME

ExchangeNow

REGULATED

Y

LICENSE_OR_REGISTRATION_NUMBER

<inset license or registration number>

REGULATION_BODY

MAS

REGULATION_BODY_URL

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

CONTACT_COMPLIANCE

[email protected]

CONTACT_TECHNICAL

[email protected]

CONTACT_SUPPORT

[email protected]

CONTACT_LEGAL

[email protected]

API_URL

https://veriscope.acme.com

TR_PROTOCOL_CIPHERTRACE

Y

TR_PROTOCOL_TRISA

Y

TR_PROTOCOL_TRP

N

TR_PROTOCOL_TRUST

N

TR_PROTOCOL_SYGNA

Y

TR_PROTOCOL_VERIFY_VASP

N

TR_PROTOCOL_VERISCOPE

Y

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.