Whitepaper Appendix A: TRISA Interoperability Messaging Matrix
Travel Rule Protocol Message Matrix
TRISA | OpenVASP TRP | PayString | BIP75 |
IVMS101 | IVMS101 | ISO 20022 | IVMS101 |
Wrapper | Transport layer | SignatureWrapper | EncryptedProtocolMessage |
Connect | Transport layer | InvoiceRequest | InvoiceRequest |
Verify Originating Cert | See Extensions | InvoiceRequest Verification | Validate InvoiceRequest |
Return | Transfer Inquiry | InvoiceResponse | PaymentRequest |
Verify Beneficiary Cert | See Extensions | InvoiceResponse Verification | Validate PaymentRequest |
Transaction Data | Transfer Inquiry Resolution | ComplianceData | EncryptedProtocolMessage |
Transaction Confirmation | Transfer Confirmation | PaymentProof/PaymentReceipt | PaymentACK |
Errors and Exceptions | HTTP Error Codes | Error | HTTP Error Codes |
Travel Rule Protocol Message Descriptions
Entity | Source Message Type | Purpose |
OpenVASP TRP 1 | Transfer Inquiry | Seeking approval from the beneficiary VASP for a virtual asset transfer by specifying transfer details including originator and beneficiary information, asset identifier, amount and a callback URL |
OpenVASP TRP | Transfer Inquiry Resolution | The callback URL from the transfer inquiry is used to post back an approved message with payment address and callback URL, OR a rejected message |
OpenVASP TRP | Transfer Confirmation | The callback URL from the transfer inquiry resolution is used to post back a txid, OR a canceled message. |
PayString 2 | Signature Wrapper | Encapsulating wrapper for signing PayString protocol messages |
PayString | Payment Information | Payment information for transaction/transfer |
PayString | Invoice Request | Message sent by Sending End point, message contains the required information for Receiving Endpoint to return the payment setup details |
PayString | Invoice Response | Message sent by Receiving Endpoint in response to the
InvoiceRequest message sent by the Sending Endpoint |
PayString | Compliance Data – Invoice Response | An upgraded invoice request message sent by the Originating Institution to transmit required Compliance Data corresponding to the required information mentioned in complianceData |
PayString | Payment Proof | Optionally sent by the Sending Endpoint as a proof of payment on the payment address sent in the InvoiceResponse message by the Beneficiary Institution |
PayString | Payment Receipt | Optionally send by the Beneficiary Institution to the Originating
Institution as a receipt of payment |
PayString | Error | Message used to communicate PayString protocol level errors |
BIP75 | Invoice Request | The InvoiceRequest message allows a Sender to send information to the Receiver such that the Receiver can create and return a PaymentRequest. |
BIP75 | Protocol Message | The ProtocolMessage message is an encapsulating wrapper for any Payment Protocol message. It allows two-way, non- encrypted communication of Payment Protocol messages. The message also includes a status code and a status message that is used for error communication such that the protocol does not rely on transport-layer error handling. |
BIP75 | EncryptedProtocolMessage | The EncryptedProtocolMessage message is an encapsulating wrapper for any Payment Protocol message. It allows two-way, authenticated and encrypted communication of Payment Protocol messages in order to keep their contents secret. The message also includes a status code and status message that is used for error communication such that the protocol does not rely on transport-layer error handling. |
Footnotes
1 TRP Advanced Workflow. At the end of 2021 the Travel Rule Protocol Working Group merged with the OpenVASP Association. Both protocols have been unified so that there will now be only one – the OpenVASP Travel Rule Protocol. Current draft release is OpenVASP Travel Rule Protocol 3.0 (based on TRP V2.1 with signing extension, and aspects of the earlier OpenVASP protocol). The OpenVASP Directory continues to be offered. See https://gitlab.com/OpenVASP/travel-rule-protocol
2 PayID was renamed to PayString on 15th December 2020. https://github.com/PayString/paystring