package trisa.data.generic.v1beta1

Get desktop application:
View/edit binary Protocol Buffers messages

Identifier identifier = 1
the identifier being used, e.g. "DTI" or "SLIP0044"
string symbol = 2
the symbol of the asset used for the identifier

DEPRECATED: the ConfirmationReceipt message was deemed to cause confusion as it could signal that the confirmation payload was received and the transfer is concluded. Use the Pending message instead to signal that this is a control flow message.

string envelope_id = 1
the TRISA envelope ID for reference
string received_by = 2
name of the recipient or recipient VASP
string received_at = 3
RFC 3339 timestamp of the receipt of request
string message = 4
A generic message to respond with
bool response_required = 5
If the message requires an additional transfer message

Used in: Asset

SYMBOL = 0
the identifier is a coin/token symbol
DTI = 1
the Digital Token Identifier (DTI) for the asset
SLIP0044 = 2
the SLIP0044 identifier for the asset

A control flow message to support asynchronous TRISA transfers. Pending messages can be returned as an intermediate response during a compliance transfer if further processing is required before a response can be sent. The Pending message should provide information to the originator about when they can expect a response via the reply_not_before and reply_not_after timestamps. The Pending message should also provide collation information such as the envelope_id and original transaction so that the response message can be matched to the original request.

string envelope_id = 1
the TRISA envelope ID that refers to the compliance communication
string received_by = 2
the name of the recipient or recipient VASP
string received_at = 3
the RFC3339 formatted timestamp when the request was received
string message = 4
an optional message to respond with to the counterparty
string reply_not_after = 5
the RFC3339 formatted timestamp when the response will be returned by
string reply_not_before = 6
the RFC339 formatted timestamp that the response will not be sent before
string extra_json = 7
any extra data as a JSON formatted object
optional Transaction transaction = 15
the original transaction for reference

Sunrise is a control flow message to indicate that the message was sent over a side channel to the TRISA protocol such as via email or phone. The Sunrise message is only saved locally to indicate a record of an out-of-band communication and is not sent in a TRISA payload.

string envelope_id = 1
the TRISA envelope ID for reference
string counterparty = 2
the name of the counterparty or counterparty VASP the messages were sent to
repeated SunriseMessage messages = 3
the list of recipients that the message was sent to
string extra_json = 14
any extra data as a JSON formatted object
optional Transaction transaction = 15
the original transaction for reference

message SunriseMessage

transaction.proto:66

SunriseMessages may be sent to multiple contacts via different channels (e.g. via an email or phone call to the compliance officer and general contact).

Used in: Sunrise

string recipient = 1
the name of the recipient or recipient VASP
string email = 2
the email address of the recipient
string phone = 3
the phone number of the recipient
string channel = 4
the name of the method or channel the message was sent over (e.g. email or phone)
string sent_at = 5
the RFC3339 formatted timestamp when the message was sent
string reply_not_before = 6
the RFC339 formatted timestamp that the response is expected before message expiration

When a TRP message is received by a TRISA node the "pending reply" is implicit in the response. Therefore instead of storing a Pending message, the TRISA node will store a TRP transaction with additional metadata about the TRP/OpenVASP exchage.

string envelope_id = 1
The headers of the message
in TRP parlance, the "request identifier" (extracted from headers)
optional TRPInfo headers = 2
the TRP API metadata for the transaction
oneof message
The TRP Message sent in the body of the request or reply
- TRPInquiry inquiry = 3
- TRPApproved approved = 4
- TRPRejected rejected = 5
- TRPConfirmed confirmed = 6
- TRPCanceled canceled = 7
string extensions = 14
Extensions and parsed TRISA information
any extensions data as a JSON formatted string
optional Transaction transaction = 15
the TRISA reference transaction

TRPResolution contains the response to an approved/rejected TRP inquiry.

Used in: TRP

string address = 1
some payment address
string callback = 2
callback to send transaction ID to.

Used in: TRP

string canceled = 1
the human readable reason for cancellation or null

Used in: TRP

string txid = 1
the transaction ID of the confirmed transaction on the chain

TRPInfo stores the API metadata for the TRP transaction.

Used in: TRP

string version = 1
the TRP API version used in the message
string request_identifier = 2
the request identifier (envelope ID)
repeated string extensions = 3
The names of any extensions uses in the request

A TRPInquiry contains the asset, amount, and callback information.

Used in: TRP

map<string, string> asset = 1
the asset identifier(s) for the transaction
double amount = 2
the amount of the transaction
string callback = 3
the callback URL to respond to

Used in: TRP

string rejected = 1
the human readable reason for rejection or null

Generic Transaction message for TRISA transaction payloads. The goal of this payload is to provide enough information to link Travel Rule Compliance information in the identity payload with a transaction on the blockchain or network. All fields are optional, this message serves as a convenience for parsing transaction payloads.

Used in: Pending, Sunrise, TRP

string txid = 1
a transaction ID unique to the chain/network
string originator = 2
crypto address of the originator
string beneficiary = 3
crypto address of the beneficiary
double amount = 4
amount of the transaction
string network = 5
the chain/network of the transaction
string timestamp = 6
RFC 3339 timestamp of the transaction
string extra_json = 7
any extra data as a JSON formatted object
string asset_type = 8
the type of virtual asset for multi-asset chains
string tag = 9
optional memo/destination-tag required by some ledgers to identify transactions

package trisa.data.generic.v1beta1

message Asset

Identifier identifier = 1

string symbol = 2

message ConfirmationReceipt

string envelope_id = 1

string received_by = 2

string received_at = 3

string message = 4

bool response_required = 5

enum Identifier

SYMBOL = 0

DTI = 1

SLIP0044 = 2

message Pending

string envelope_id = 1

string received_by = 2

string received_at = 3

string message = 4

string reply_not_after = 5

string reply_not_before = 6

string extra_json = 7

optional Transaction transaction = 15

message Sunrise

string envelope_id = 1

string counterparty = 2

repeated SunriseMessage messages = 3

string extra_json = 14

optional Transaction transaction = 15

message SunriseMessage

string recipient = 1

string email = 2

string phone = 3

string channel = 4

string sent_at = 5

string reply_not_before = 6

message TRP

string envelope_id = 1

optional TRPInfo headers = 2

oneof message

TRPInquiry inquiry = 3

TRPApproved approved = 4

TRPRejected rejected = 5

TRPConfirmed confirmed = 6

TRPCanceled canceled = 7

string extensions = 14

optional Transaction transaction = 15

message TRPApproved

string address = 1

string callback = 2

message TRPCanceled

string canceled = 1

message TRPConfirmed

string txid = 1

message TRPInfo

string version = 1

string request_identifier = 2

repeated string extensions = 3

message TRPInquiry

map<string, string> asset = 1

double amount = 2

string callback = 3

message TRPRejected

string rejected = 1

message Transaction

string txid = 1

string originator = 2

string beneficiary = 3

double amount = 4

string network = 5

string timestamp = 6

string extra_json = 7

string asset_type = 8

string tag = 9