What is Embedded EIV?
When First AML verifies the identity of an individual we complete this via our EIV (electronic identity verification) form. The url to this form is typically sent to the individual via email or SMS. Because of this there is typically some delay between the case creation and collection of all the information requireed to verify the identity of an individual.
The Embedded EIV feature allows customers with an intergration into the Public API to embed the EIV experience into their own web applications to seamlessly collect verification information and bring down times to successful onboarding.
A key component of using Emebdded EIV is a working integration from your own system into the First AML Public API
Below is a demonstration of an example customer using the embedded EIV experience in their end user sign up flow.
Embedded EIV Flow
The following is a rough order of operations expected when using Embedded EIV.
- The individual begins a sign up process on the Customer web application.
- The Customer web application processes the sign up and creates the End User account.
- The Customer web application calls the First AML Public API to create the case returning information such as the case and individual identifiers as well as the embedded verification url.
- The embedded verification url is used in the customer website via an iframe to collect the appropriate information required to verify the individual.
- The embedded verification iframe messages back to the customer website that the information has been collected and if possible the outcome of the verification.
- The Customer website resumes its own sign up flow.
