Rate limiting

PassFort is introducing a rate limit to profile creation. This does not apply to users.

We’re making this change as we gather data about how we scale up to meet heavy usage in order to improve overall performance. Over time, this rate limit will be rolled out to more features.

Initially, the maximum profile creation rate will be set at 100,000 profiles per hour. Over time, this will be reduced  to an appropriate level of around 10,000 profiles per hour. If you think this may affect your environment, get in touch with support. 

For more information about rate limiting, you can read the article here.

Ad hoc request multiple forms from the same task

To streamline processes and improve customer experience, we have added the ability to select and send multiple forms per task to collect more data at once. Previously, the request from customer feature only allowed users to send one form per task.

This will support multiple instances of the same form. You will be notified of the multiple forms before sending, in case they were added in error.

You can still add forms from other tasks, allowing you to consolidate many more required forms in one request.

Getting started

No new configuration is required, any user with permissions to send requests can start using this feature right away.

To find out more, please read our updated documentation here.

Setting custom expiry dates on tasks

You can now edit and save a custom expiry date on a task both through the portal and the API. 

You can set a custom expiry date on tasks that are completed and have a default expiry date configured. The new custom expiry date will only apply to that task version, any subsequent task versions will be calculated based on the default expiry configuration. 

Getting started

Custom task expiry is available now to all institutions without any need for configuration changes. Any user with permissions to action a task can edit and save a new expiry date. 

Get notified if a task assigned to you or your team has a new custom expiry date by updating your notification preferences here.

To find out more, please read our updated documentation here.

Decision Reasons

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.

Verify documents with Mitek using our ID verification (PassFort collects documents) check

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.

Export Profile, Assignee and Flag fields in reports

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.

You'll soon be be able to set custom expiry dates on tasks

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.

Decision Reasons

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.

Changes to the tax codes component in profile data

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

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 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.

Show Previous EntriesShow Previous Entries