NotifyTxRequest

Schema

	Property	Type	Required	Description
	requestId	String	Yes	requestId is the unique id for all transaction, the same travelrule-request invoke process flow should be using same requestId, the recommend format is: "[YOUR_VASP_NAME]-[UUIDv4]"
	txId	String	Yes	*if the travel rule is after on chain, then the txId is required. the tx id format type can check the table.

Example

{
  "requestId": "testexchange-189e9948-64c7-4a6c-bb4f-859c173321c5",
  "txId": "d1029841dacb031098288b257b628a967eb963bbaccf954506ad0694219497a4"
}