Communicate Forms Localisation Phase 1: Hardcoded Text

For the first phase of delivering localised PassFort forms, you can now configure the language of the set PassFort text to be one of the following:

  • English (en)
  • French (fr)
  • German (de)
  • Italian (it)
  • Japanese (ja)
  • Simplified Chinese (zh_CN)

This includes all the hardcoded PassFort text that isn’t the set question text. For example, help text, upload instructions, buttons etc.

The Portal has also been updated to show a form’s configured language in the Request from Customer feature.

This means the PassFort set text can be configured to match the text the questions are written in, allowing forms to be completely in an end user’s native language. Previously, the PassFort text was only available in English.

If you want to make use of this feature, you need to submit a change request to our team in order to update your forms.

Additional information

Overview Page

The Overview page (initial landing page) that lists all the forms in the request is not part of a form, so doesn’t have a direct point to configure its language. As a result, it uses the language from the first form. Therefore, if a request contains forms in different languages, the Overview page will change language as the end user works through the forms.

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

Future plans

  • We plan to expand the list of available languages that we support in future.
  • In the next phase of this project, we plan to enable forms to have multiple languages. Enabling customers to provide different translations of their question text that the end-user can select from. You can follow progress in our product portal here

Updated user interface for verification lists and the authorized persons task

Users can now remove and re-add authorized persons to a verification list using the PassFort portal. We have also updated the design of PassFort’s company associate verification list user interface. This new design is now in use for all tasks that use verification lists.

You don’t need to take any action, but you may notice that the layout of verification lists has changed. We have updated the PassFort help site to reflect the new UI design. Please refer to the help documentation on copying information from imported associates, removing or re-adding company associates from the verification list, and manually adding associates.

If you have any questions, contact Support.

Automated follow up reminders

You can now automatically send reminder emails to applicants with outstanding requests for information. This means that you can request information from customers without having to manually track applications’ statuses, outstanding actions, and contact information.

You can configure universal settings for all incomplete requests to automatically send up to 3 reminders and set day intervals between them.

Getting started

To find out more about how to use follow up reminders, please visit our new help page.

To enable this feature in your account, our team can help set up follow up reminders for you. If you’d like us to set this up for you, just get in touch and let us know:

  • The number of reminders to send (maximum of 3)
  • The number of days between reminders
  • Your preferred email subject
  • The email message to display to your customer

If you've upgraded to the new policy versioning, you'll be able to access the settings in your institution in the Policy Builder.

Rate limiting of collected data updates

PassFort is introducing a rate limit to collected data updates. The endpoint POST /4.0/profiles/{profile_id}/collected_data will be rate limited at 10, 000 requests per hour. 

We’re making this change as we continue gathering 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 additional features.

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.

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.

Show Previous EntriesShow Previous Entries