<?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/9b614cde123f4b908f57455568c2d993&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/9b614cde123f4b908f57455568c2d993-283d0d0e2454499a.gif</thumbnail_url><duration>77.557</duration><title>How MIPECE Stops Fraudulent Payments Before Execution</title><description>This Loom explains how MIPS stops bad or fraudulent payments before money moves using independent, verifiable proof. It notes that duplicate, fraudulent, and incorrect payments cost companies billions of dollars each year, and many systems detect fraud only after funds are transferred. The risk increases further as AI agents initiate training and payment actions. The presenter shows a case where an unverified $50,000 payment request from an unknown vendor is submitted, but authorization conditions are not satisfied due to a null mutation proof ID, so no mutation occurs.</description></oembed>