{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/5e2f810647d84a13b7d3731a8a092772\" frameborder=\"0\" width=\"1440\" height=\"1080\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1080,"width":1440,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1080,"thumbnail_width":1440,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/5e2f810647d84a13b7d3731a8a092772-00001.gif","duration":262.652,"title":"Nested VASP Deposit Option 3","description":"In this video, I will demonstrate how to handle incoming travel rule messages in a nested VASP setup. I will explain the concept of VASPs with entities in multiple jurisdictions and the role of a gateway VASP. I will show you how to implement a webhook on the gateway VASP to receive notifications for incoming travel rule messages. Using the information in the message, we will look up the blockchain address and redirect the message to the appropriate subsidiary VASP. No action is requested from the viewers."}