Identity Proofing App 

Implement your identity solution simply and faster with QR Code Integration or SMS-based campaigns.

IPA - Overview 

IPA (Identity Proofing Application) is an application that allows you to verify that the identity claimed by the user corresponds to the identity supported by the provided documents.

Why IPA? 

IPA - Identity Proofing App

• Able to deploy quicker
• Integrated with IDEMIA Identity Proofing platform to immediately begin verification process
• Customizable to include branding

Full Integration

• More flexibility
• Documentation and sample code provided
• Ability to launch your own app

How it works 

First and foremost, IPA works as a web application and does not require any installation processes for end user - this innovative solution allows user to use it on the go, without any additional support from engineers or programmers. All you have to do is to scan QR code or open a link from SMS and start your proofing experience.

IPA allows for quick and straightforward data and identity verification, comparing to its ancestor - Identity Proofing and Verification demo, requiring integration of ~70 endpoints and 2 SDKs. Thanks to integration withing Identity Proofing platform you can even customize user experience by specific colors and graphics. IPA supports multiple languages translations, so it can be easily accessible not only in English-speaking countries, but also for Spanish, Portugese, Polish and French users.

During proofing experience IPA analyses given ID (personal ID, driving license, passport) and liveness face identification (in either active or passive form). Both documents and face pictures are throrughly verified to omit potential frauds - system checks their authencity and credibility. Those data are verified and stored in Partner Managers account:

• Transactions in Identity Proofing (for QR code integration)

• SMS campaign details (for SMS campaign integration)

IPA can be integrated for end users in two forms: QR code and SMS campaign integration.

QR Code or SMS Campaign Integration? 

QR Code Integration 

In order to use QR Code Integration, user has to generate an integration endpoint, which will be used to communicate with servers. QR Code Integration is the fastest way to run and collect proofing information from receivers' group. Click here to find more details.

Request QR code/link

A customer calls IDEMIA to request QR code/link. They are then immediately sent a one-time QR code/link and a Transaction ID.

Customer displays QR code

The end user scans QR code with smartphone and is redirected to Identity Proofing App (IPA) with customer's customization.

Scan ID

User uses IPA to scan their identification document and to capture a selfie using their mobile browser. Verification begins automatically.

Receive results

A customer calls IDEMIUA to request QR code/link. They are then immediately sent a one-time QR code/link and a Transaction ID.

SMS Campaign Integration 

SMS campaigns are more complex comparing to QR code integration, however it does not mean that they are more difficult to maintain. Moreover - SMS campaigns enable user not only to create proofing experience and collect data, but also verify them in the form of charts and intuitive tables. Click here to read more.

Create campaign

Customer defines and selects proofing criteria. They upload contact information and create a desired SMS message and landing page.

Launch campaign

An immediate or scheduled SMS text message is sent with a link to the customer's landing page. The landing page contains a link to IPA that launches IPA with customer's customization.

Scan ID

User uses IPA to scan their identification document and to capture a selfie using their mobile browser. Verification begins automatically.

View results

The transaction results can then be viewed in the campaign dashboard.

IPA - QR Code Integration 

QR Code - Configure your App 

In order to use IPA, you must generate an integration endpoint, which will be used to communicate with our servers. Integration endpoint is a secret and should not be shared with anyone. Detailed instruction how to create and use QR code endpoint is described in How to use it page.

Simple configuration page enables for quick creation of endpoint and immediate collection of users' proofing experiences.

All integrator has to do is to complete 4 steps:

1. Selection of proofing environment

2. Selection of country

3. Choosing document type for proofing

4. Choosing facial recognition type

Generate endpoint 

“Generate endpoint” button redirects to endpoint page. From this point user can either preview endpoint in a form of QR code or configure new proofing experience. To test endpoint’s correctness, user can preview QR code once clicking on “Generate test QR code”, as on screens below.

IPA - SMS Campaign Integration 

Campaign configuration 

SMS campaigns are more complex comparing to QR code integration, however it does not mean that they are more difficult to maintain. Moreover - SMS campaigns enable user not only to create proofing experience and collect data, but also verify them in the form of charts and intuitive tables.

Welcome page

To access IPA with SMS campaign user needs to click on ‘SMS Campaigns’ button (left screen below). IPA opens in a new tab (right screen below). IPA Homepage informs about campaign process described in four quick steps. In the left navigation column user can start creation of new campaign , edit scheduled or drafted ones as well as see launched and expired campaigns. Clicking on launched or expired campaigns redirect to campaign overview, which will be described soon in this documentation.

Creation of SMS campaign 

Clicking on “Start New Campaign” button redirects to campaign creator, that is divided into 5 steps necessary for complete campaign experience. Once providing required information in each step - action should be confirmed by clicking ‘Previous’ or ‘Next’ buttons. Otherwise your changes won’t be saved and progress will be lost. Steps that are already completed are marked with green icon in left navigation.

Step 1: Campaign name 

At first, user has to define name for the campaign. Naming must be unique, coherent and meaningful, so campaign can be easily found among others on the list. Moreover, campaign name is limited to 40 signs.

Step 2: Proofing Criteria 

Secondly user defines proofing criteria, such as:

• proofing tenant

• country of documents' origin

• type of document - what documents user sees depends on the chosen country

• type of facial recogition - as for simplified QR code integration, user can choose either to perform active or passive liveness, or to resign from it and scan document only.

Step 3: Prepare Communication 

In 3rd step user configures SMS content as well as landing page that is about to display on mobile device after clicking on link from SMS.

SMS content needs to be meaningful and coherent, as it is limited to max. 100 signs. Remaining 60 signs are reserved for shortened url that will be attached to given message and then send to desired recipients.

In Landing Page section user can define a page that will display on recipient’s device after clicking on the link and redirection to the browser. User can determine styling of elements, such as text, graphics and links in WYSIWYG creator. Additionally, user can force end users to accept Terms & Conditions, add T&C .pdf file, decide about constent copy, file name and button. Result of those stylings display on the preview next to configuration panel, as on the screen below.

Step 4: Upload Contacts 

In this step user defines a list of recipients that will take part in this campaign by completing proofing experience. List can be either uploaded from .csv/.xlsx file or recipients' numbers might be added manually. Contacts imported from files are validated and only correct ones (with country prefix, without letters, etc.) are displaying as proper ones. Rejected contacts will appear on the top of the list marked in red. User can use filters to either show all contacts on the list or just invalid ones. Invalid contacts need to be removed from the list to proceed.

In manual upload user can change country prefix depending on recipients' contact origin.

Important note: even if recipient has foreign contact number, the document type for proofing must be aligned with the country and document chosen while defining Proofing Criteria in step 2 - e.g. for campaign defined for Poland & polish ID user has to scan polish ID even if his contact number if from another country (France, Spain, etc.).

Step 5: Schedule 

User can decide whether to send campaign immediately and start collecting data process or to schedule send for any point in the future.

Important note: Campaign that is sent immediately loses the chance of further edition. The only element that can be edited is a Landing Page in ‘Prepare Communication’ (Step 3).

Scheduled campaign are editable until chosen schedule date.

Delete campaign 

User can delete campaign at any possible stage - when it is a draft, scheduled or launched campaign. In all cases the process is irreversible and data will be lost with the moment of deletion.

Campaign results 

If campaign is configured properly and sent to recipients, user can check campaign statistics in ‘Overview’, 'Progress' and 'Results' pages.

Campaign overview 

Campaign overview page is divided into 4 sections presented on the screen below. Left navigation bar indicate basic data about campaign: its current state (scheduled/launched), number of recipients, form of communication and proofing criteria. Funnel chart represents recipients' flow through proofing process and indicates how many people completed every step. Charts below represent distribution of recipients with respect to Level of Assurance they achieved during proofing experience and user’s decision showing how many proofing experiences are accepted, rejected or still pending.

Campaign progress 

Campaign progress page is a table presenting recipients and their timestamps of every step they performed during proofing experience.

Campaign edition possibility 

Important note: All steps of drafted and scheduled campaigns might be edited. Launched campaigns only have the possibility of Landing Page Edition (in ‘Prepare Communication’ step). Expired campaigns cannot be edited.

What's next 

After choosing your IPA integration type you can verify collected data in Transactions (QR Code Integration) or Campaign Results (SMS Campaign Integration). Below you can see how do results verification work for SMS campaigns.

Campaign results 

Campaign progress page is a table presenting recipients' data collected during proofing experience. User can download all of the results in the form of a .zip file (.zip with .zips inside, one zip per recipient).

Campaign results - recipient's details 

Clicking on contact number on campaign progress and campaign result page redirects to given recipient’s details.

This page gives user detailed information about each step of proofing experience, summary of recipient’s data, document photos, document and liveness indicators metrics, as well as LOA and timestamps.