Templates define the steps your end-users will take to verify their identity, and may be uniquely configured for different product paths and workflows.

Configurable template options include the types of verification to conduct (photo ID, selfie comparison, liveness) and settings for the verification flow (allowable ID types, consent collection, etc.).

Create New Template

1. Under "Configuration" in the menu, select Templates.
2. Click the Create Template button in the top right corner of the screen.
3. Add a name and select a template type, then click Save.

📘

Template Tip #1

If you will be creating multiple templates, name your templates to match the intended use case (e.g. New Registration, Returning Customer, Barcode Scanner, etc.).

📘

Template Tip #2

Hosted transactions can only be generated for Web type templates.

Once created, a Template Key will be generated that can be used when creating a transaction programmatically, and will be prefixed with tpk_.

Template Configuration

General Settings

Template Key

This value, prefixed with tpk_` is unique to this template and is required to create a transaction programmatically.

Theme

If your product paths require different branding, you can customize the look and feel of the end user experience per template by selecting the appropriate Theme.

Action Map

Templates can use different Action Maps for business logic to suit the use case. You may also tap the "Edit" icon for a shortcut to manage the selected action map.

Intro screen

You may choose to use our default introduction screen to set the end user's expectations for the identity verification process. For slight updates to the wording on your intro screen, you may reach out to [email protected], or you are welcome to develop your own custom UI for this purpose.

Reverification

Berbix supports a simplified re-verification flow for end-users that have been previously verified. If this setting is enabled, the template will require a selfie only, and will perform a check against the ID photo data collected during the original transaction.

This can be used to collect additional verification data from users or to re-verify existing users over time to ensure they are the same person.

To generate a reverification transaction, the original transaction associated with that user's Customer UID must be in an Accepted state.

Disable handoffs

If necessary for your use case, you may use this setting to restrict end users from handing off to their mobile device. If you are interested in disabling handoffs, we recommend checking in with our Solutions Engineering team at [email protected] to discuss potential risks and benefits.

Verifications

Allowable ID Types

Customize what types of photo IDs are permitted in your verification flow. You can select from the following options:

• ID card or driver license
• Passport
• ID card, driver license, or passport
• Custom

📘

Template Tip #3

In this context, 'ID card' refers to a government issued, non-driver photo ID.

The types of documents that fall into this category can vary by country, state, province, or region. For more details, check out our Supported ID Types.

Depending on the option you select, end users will be prompted to submit only the allowable ID types. If the end user submits an unacceptable ID type, we'll do our best to prompt the user by reminding them which document type is expected and providing hints like "We can't find the barcode on your drivers license."

🚧

Allowable ID Types Fallback

If you choose to only allow specific ID types, we strongly recommend incorporating this into the Action Map used with the template as a fallback.

For example, if your template does not permit passports, add a condition to your Action Map to reject the transaction if the id_type matches Passport.

Custom ID Types

If you select "Custom," you'll be presented with more granular filter options for the template.

For example, you could create a custom configuration to accept passports from any country, but allow drivers licenses issued in Canada or the U.S., as shown below.

The list of international ID documents we support is growing, but granular customizations for country-specific ID type restrictions are currently limited to the U.S. and Canada.

Collect Country

If you are using Custom allowable ID types, the "Collect Country" setting is required. When enabled, the end user will be prompted to select the country that issued their ID document.

We do still attempt to detect the issuing country when this setting is disabled, however we recommend using it if you have a global customer base for greater accuracy.

If you enable multiple ID types, the user will be prompted to select their document type for the issuing country from among the enabled options:

If a user completes the flow with a document you don’t permit or selects a country that does not match their actual issuer, we'll raise a flag and route the transaction according to your Action Maps.

Require mobile verification

When enabled, end users who initiate a transaction on a desktop or laptop computer will be required to handoff to a mobile device to complete the verification.

We highly recommend requiring mobile verification, as this provides additional security to ensure your end user is the same person that initiated the transaction, and it results in higher image quality than transactions completed via webcam.

Disable email handoff

Disabling email handoff limits handoff mechanisms to SMS text and QR code.

Allow capture with webcam

Allow users to upload photos of their ID with the webcam on their desktop or laptop computer.

As noted above, allowing webcam image capture will have a negative impact on accuracy, confidence, and fraud detection rate.

Default handoff mechanism

This selection determines how end users will be prompted to handoff to a mobile device.

Collect machine readable component

When this setting is enabled, we capture both human-readable and machine-readable content to compare the data across sources. We highly recommend keeping this setting enabled for increased accuracy, confidence, and fraud detection capabilities.

Selfie

Enabling this step allows Berbix to compare the face on the ID to the user's selfie and liveness check.

📘

What's a Liveness Check?

We capture a series of individual images to compare to the initial selfie, and to verify that the user is present and following the instructions on screen to look left and right.

Perform basic selfie only

If activated, Berbix will only collect a single photo of the user rather than the full liveness check.

While this may shorten the experience for the end user, it limits the data we are able to gather for comparison, and limits our ability to confidently determine that the user is present and live.

Always perform selfie consent collection

Some states (IL, WA, TX) legislatively require consent for automated facial recognition, which is required to perform biometric comparison. If we determine the user is in one of these locations, or if we cannot determine the user's location, we present the consent screen pictured below.

This setting allows you to require consent for all users.

Barcode scan

Enabling this setting configures the template to include a barcode scan only.

This workflow, which relies on the machine readable data in the barcode on the back of a US or Canadian driver license or ID card, is the template required for the Berbix Bouncer App.

© Berbix Inc. All rights reserved.