Run ID verification checks with GetID

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

You can use GetID to verify documents by submitting them to PassFort through the Portal or our API.

In order to run these checks, you need to have a direct agreement with GetID.

Contact us to get started or learn more about our GetID integration here.

Integration with Charity Commission of England and Wales to be discontinued

The Charity Commission of England and Wales is a data provider used to run the Charities registry check in PassFort.

The Charity Commission of England and Wales has decommissioned their “Search Charities API” today. As the provider will not be migrating accounts using the legacy API to their new API and we are not able to prioritise rebuilding our integration in the short term, our integration with Charity Commission of England and Wales is no longer available.

We will consider rebuilding our integration against the Charity Commission’s replacement API based on demand. If you believe this will impact you, please contact us to discuss alternatives or register your interest in the integration on our roadmap here.

We now automatically cancel or reject applications for associates you remove from a verification list

We will now automatically cancel/reject an associate’s product application if you remove that associate from a task verification list, either manually or via API.


This means that you won’t need to take further action on an associate you’ve just removed from a verification list. Previously, you needed to manually cancel/reject the associate’s product application. The application status change will be automated but will still follow the standard PassFort application status flow outlined here.

This will only impact product applications for associates removed from a verification list going forwards. This means that the product applications of pre-existing associates that have already been removed from a verification list will not be retroactively cancelled/rejected.

You can read more about this new behaviour here.

Changes to onboarding company associates via the API

We are making a small behind-the-scenes change to the Profiles API to improve PassFort's performance when onboarding companies. The change reduces the time it takes for PassFort's automated onboarding tasks to complete by approximately 40% for company profiles with many associates.

The change enforces the rule that an associate profile can never be moved from one company application to another.

For example, if you are onboarding "Company A" with an associate, "Associate Inc", you cannot modify the associate profile "Associate Inc" so that it is instead linked to "Company B" that you are onboarding separately.

PassFort's portal is not affected by this change because this workflow has never been possible in the portal. If you think this will affect your use of the API, or have any questions about this, get in touch with PassFort Support.

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

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

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

This can be used with our document verification form and works with request from customer and flows.

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

Smaller webhook payloads for collected data

We have created a version of our collected data updated webhook that returns less information in the message body. Switching to the new version of this webhook improves performance and reduces processing times, particularly when onboarding companies.

The webhook acts as a prompt to call the collected data API, where you can retrieve the new collected data for the profile. As well as improving performance, the new format reduces the risk that the webhook size will violate any firewall message size limits you may have in place. It also reduces the risk that the webhook is larger than the maximum message limit of your messaging queue and reduces network load.

Although we won't be asking existing PassFort customers to move to the new version of the webhook at this stage, the old webhook will be deprecated. This means that you should avoid undertaking new development against the old webhook, and future PassFort features might not be supported in that version.

The changes to the webhook, as well as updated guidance on its usage, can be found in the API reference and help documents.

If you would like to find out more about the benefits of the new webhook or begin making use of it please contact your customer success manager.

Integration with Charity Commission of England and Wales to be discontinued

The Charity Commission of England and Wales is a data provider used to run the Charities registry check in PassFort.

The Charity Commission of England and Wales are due to decommission their “Search Charities API” on Monday, 16th May 2022. As the provider will not be migrating accounts using the legacy API to their new API and we are not able to prioritise rebuilding our integration in the short term, our integration with Charity Commission of England and Wales will no longer be available after this date.

We will consider rebuilding our integration against the Charity Commission’s replacement API based on demand. If you believe this will impact you, please contact us to discuss alternatives or register your interest in the integration on our roadmap here.

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.

Show Previous EntriesShow Previous Entries