You can now create a standardised list of decision reasons that can be applied to your products. These lists can then be selected from when deciding the outcome of an application.

This means that you can have standardised reasons for the outcome of applications, in addition to the existing free text notes.

These reasons are available for exporting in reports, so you'll have more accurate information on the trends and patterns of your application decisions. Make sure you have the Export data permission to be able to access them.

You are able to add additional or disable existing reasons for selection so you can react to changes in trends or new data points that need to be captured in future application decisions.

Get started

To find out more about how to use decision reasons, please visit our new help section.

To be able to access this feature, you will need to ensure that your demo institution has been upgraded to support the new policy versioning. If you’d like us to set this up for you, just get in touch.

You can now run ID verification (PassFort collects documents) checks using Mitek as the data provider.

You can use Mitek to verify documents and run biometrics checks, by submitting documents to PassFort through our portal or our API. You can run checks with Mitek using a direct agreement, or make use of our reseller agreement.

This is also compatible with Mitek’s SDK. You can implement the Mitek SDK into your website or app, and upload the documents collected by the SDK into PassFort and instruct the check.

Please note that Mitek’s SDK is not currently supported in our forms.

Contact us to get started or read more about our Mitek integration here.

We've added new exportable fields to reports to help monitor applications, gather insights and take action.

The new fields are available in Applications report types (unless otherwise specified) and have been added as options in the ‘Standard profile data’ section when you click the Export .CSV button

New fields

Profile fields (Individual):

• First name(s)
• Surname
• Gender
• Phone
• Email address (also available in Task and Checks reports)

Profile fields (Company):

• Email address (also available in Task and Checks reports)
• Website
• Entity type
• Shares
• Liability
• Legal Entity Identifier (LEI)

Assignee:

• Assignee type
• Assignee user
• Assignee ID

Flags:

• Application flag (current)

Get started

The new fields are available now. Make sure you have the Export data permission to be able to access them. You can also learn more in our help article.

If you're new to reports, check out this video to help you learn the basics of reporting.

In mid January, we'll release task expiry on demand, and you'll be able to edit and save a custom expiry date on a task through both the portal and the API.

At the moment, the date at which a task expires is determined by your task's expiry configuration and cannot be changed.

Custom task expiry dates will give you full control over task expiry. For example, if you need to migrate legacy profiles and maintain pre-existing expiry dates, you'll be able to set that through the API. Alternatively, your compliance team might want to expire a Verify Identity task in line with a customer's document expiry date. 

Custom task expiry dates will be available to all institutions without any need for configuration changes. Any user with permissions to action a task will be able to edit and save a new expiry date.

If you have any questions, please get in touch with your customer success manager for more details.

Later this month, we will release decision reasons, and you will be able to create a standardised list of decision reasons that can be applied to products. These lists can then be selected from when deciding the outcome of an application.

To be able to access this feature, you will need to ensure that your institution has been upgraded to support the new policy versioning.

If you’d like us to set this up for you, just get in touch.

We've now released a new layout for the tax codes component in company profile data. We also introduced a new type called Other TIN which will allow us to store localised tax identification numbers for Turkey, Greece, and Taiwan.

Old layout

New layout

Localised tax identification numbers are available for companies incorporated in the relevant country. For example, the Greek AFM number will be selectable on profile data for companies with Greece as their country of incorporation.

If you have any questions, please get in touch with Support.

You are now able to run ID verification (PassFort collects documents) checks with Onfido using the latest version of Onfido's API (v3).

As with the previous integration, you can use Onfido to verify documents and selfies. All configuration options supported in the v2 version are supported.

You can now also see the granular reasons why Onfido checks pass or fail without leaving the PassFort Portal in the Full Results modal.

To take advantage of these new features, contact our support team about migrating to Onfido v3.

Next week, we'll be releasing a new layout for the tax codes component in company profile data. We're introducing a new type called Other TIN which will allow us to store localised tax identification numbers for Turkey, Greece, and Taiwan.

Existing layout:

Upcoming layout:

The new layout and structure change will allow us to easily expand and support further localised tax identification numbers, and provide you with more granularity about the data you collect on company profiles.

Localised tax identification numbers will be available for companies incorporated in the relevant country. For example, the Greek AFM number will be selectable on profile data for companies with Greece as their country of incorporation.

If you have any questions, please get in touch with Support.

We have made improvements to our MRZ validation for ID verification checks using Onfido v3, GBG IDScan and Jumio. The improvements allow for better validation to be used on passports that have a varied name order, where single separators are used between given names and surname.

Previously, ID verification checks didn't consider country-specific logic for given names and surnames. It validated against a pattern that used a double separator between surname and first name. The check might fail when the passport was from countries such as Malaysia, Singapore and Vietnam because our validation did not recognise the case where only single separators are used.

The MRZ validation now passes in cases where the passport doesn't use a double separator between names.

If you have any questions, please contact us at support@passfort.com.

We've now released the updated layout for the identity numbers component in the Edit Identity dialog that is used to capture profile data.

Old layout

New layout

This allows us to support more document-related fields in individual profiles, including a new field for issuing state. Issuing state is available for driving licences issued in India, Australia, and the United States.