<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/bed6edb57b6144ca9a53efc63f26a511&quot; frameborder=&quot;0&quot; width=&quot;1662&quot; height=&quot;1246&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1246</height><width>1662</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1246</thumbnail_height><thumbnail_width>1662</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/bed6edb57b6144ca9a53efc63f26a511-c462c9caf20df355.gif</thumbnail_url><duration>358.209</duration><title>End to End Encryption Recipes Walkthrough</title><description>Hi everyone, I am Masha, and today I walk you through three end to end encryption recipes in NotoBene. First, make sure you disable the NotoBene PII Managed Encryption toggle in your dashboard, then update your DitDoc document with your generated encryption keys, for both production and sandbox, and store private keys in an HSM for production. Next, create a travel rule message, take the transaction ID, and run the second recipe to encrypt IVMS 101 properties value by value. Finally, get counterparties public keys via the presentation webhook or from their DitDoc, or use the public key endpoint, then run the third step.</description></oembed>