<?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/acce7eb33b7048c6aa58b2da9bbfd1b7&quot; frameborder=&quot;0&quot; width=&quot;3170&quot; height=&quot;2377&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>2377</height><width>3170</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>2377</thumbnail_height><thumbnail_width>3170</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/acce7eb33b7048c6aa58b2da9bbfd1b7-00001.jpg</thumbnail_url><duration>199.32</duration><title>Primer Automation: Demo use case end to end</title><description>A step by step demo of creating workflows surrounding a specific use case: Identity verification. 

Don&apos;t forget to add the &quot;Continue payment flow&quot; action at 00:15!

Use case requirements
* Every time a user has made a payment with a new payment method, send them a verification link via email.
* Capture the payment when the user is approved, and cancel if not. 
* Notify the team on Slack for specific verification outcomes, like &quot;fraud suspected&quot;, or &quot;well known fraudster&quot;.

For the sake of this demo, the following apps will be used to implement this use case:

* Payments
* Onfido for KYC
* Mandrill to send an email
* Slack to post a message</description></oembed>