Case 1: Originator and Beneficiary are Different

A case where the Travel Rule triggers.

The receiving entity is a VASP, not Juno, and the funds recipient is not the sender.

The following objects show the general structure of the request body and exemplify its use. The request body includes the same key-value pairs of transactions under 1,000 euros providing the beneficiary’s address, but it adds a compliance object that contains the data of the recipient VASP and the beneficiary.

{
   "compliance": {
      "travel_rule": {
         "vasp": {
            "did": "did:ethr:0x4cd9136034d9a63d855391fce6dba64021530b01"
         },
         "beneficiary": {
            "name": "First name Last name | Business legal name",
            "type": "NATURAL | LEGAL"
         }
      }
   }
   
   #  … same transaction data as withdrawals under 1,000 euros
}