Get desktop application:
View/edit binary Protocol Buffers messages
The TRISADirectory service specifies how TRISA clients should interact with a directory service to facilitate P2P transfers.
Interactions with the Directory Service during a TRISA transfer These are the primary Directory Service interactions.
Lookup VASP certification information either by their unique ID or by the domain of the TRISA implementation endpoint, which should be the common name of the certificate. Note that if both id and common name are supplied, ID is prioritized.
Unique identifier generated by the directory service, most common lookup field.
The URL of the directory that registered the VASP. If ommitted, it is assumed that the directory being queried is the registering VASP.
The common name of the certificate, e.g. the domain name of the TRISA endpoint. To use other name fields such as the legal business name, you must use search.
Summary information is given in return for VASP lookups as lookups are primarily intended to facilitate P2P verification and public key exchange. NOTE: only verified VASPs are returned using the lookup RPC.
If no error is specified, the lookup was successful
The uniquely identifying components of the VASP in the directory service
The endpoint to connect to for the TRISA P2P protocol (addr:port)
Certificate information if the VASP is available and verified. The identity certificate is used to establish mTLS connections, the signing certificate is used on a per-transaction basis.
Other VASP information that faciliates P2P exchanges
Registration workflow and contact verification.
Registration requests are validated that they contain correct information and then are sent through the verification process, creating or updating a VASP as needed.
The legal entity IVMS 101 data for VASP KYC information exchange. This is the IVMS 101 data that should be exchanged in the TRISA P2P protocol as the Originator, Intermediate, or Beneficiary VASP fields. A complete and valid identity record with country of registration is required.
Technical, legal, billing, and administrative contacts for the VASP.
Travel Rule Implementation Endpoint - where other TRISA peers should connect. This should be an addr:port combination, e.g. trisa.vaspbot.net:443
Common name should be the VASP domain name to issue certificates for, which should match the domain in the trisa_endpoint. If this field is omitted, the common name is inferred from the trisa_endpoint.
Business Information
Should be a date in YYYY-MM-DD format
TRIXO Questionnaire
If the registration was successful, no error will be returned
Unique identifiers for the VASP created by the registration. Use these identifiers for status lookup requests and any follow-on interactions.
The verification status of the VASP entity.
Used to decrypt the emailed certificates in PKCS 12 format
Search requests allow a more flexibly field serach to identify a VASP, these requests are primarily used to locate a beneficiary VASP in order to begin the TRISA P2P protocol. NOTE: only verified VASPs are returned using the search RPC.
Case insensitive search fields that use OR to perform the lookup. The name field can be the legal, short, or DBA name of the VASP or the common name of certificate issued to that VASP (though in this case, it is better to use the Lookup RPC). The website must be a parseable URL to lookup the VASP with.
Search filters to condition the search on. Only VASPs that are in the country(ies) or category(ies) specified are returned.
If no error is specified, the search was successful, even if no results returned.
Health check and status request that mirrors the TRISAHealth service
The number of failed health checks that proceeded the current check.
The timestamp of the last health check, successful or otherwise.
Current service status as defined by the recieving system. The system is obliged to respond with the closest matching status in a best-effort fashion. Alerts will be triggered on service status changes if the system does not respond and the previous system state was not unknown.
Suggest to the directory service when to check the health status again.
Supplies the entity review and TRISA verification status of a VASP
Check on the status of a VASP including its verification status and the service status if the TRISA directory service performs health check monitoring. The same parameters as the Lookup RPC are sent, but note that a TRISA directory service may refuse to return all or part of the status request.
Unique identifier generated by the directory service, most common lookup field.
The URL of the directory that registered the VASP. If ommitted, it is assumed that the directory being queried is the registering VASP.
The common name of the certificate, e.g. the domain name of the TRISA endpoint. To use other name fields such as the legal business name, you must use search.
Status information
Should be an RFC 3339 Timestamp
Should be an RFC 3339 Timestamp
Should be an RFC 3339 Timestamp
Should be an RFC 3339 Timestamp
If no error is specified, the verification request was successful.
The verification status of the VASP entity.
Used in: , , ,
Used in:
The uniquely identifying components of the VASP in the directory service
Address to connect to the remote VASP on to perform a TRISA request
Used in: