To ensure a smooth integration process, please review the following key requirements. They are essential to ensure your integration functions smoothly and meets our system standards. If you have any questions, please feel free to contact us via api@thirdfort.com
All integrations
Transaction ID
Each check generates a unique Transaction ID. If you are building an integration with UI elements, you should display this ID to users (i.e individual initiating the check) and allow users to search by it. This ensures that when we reference a check in communications via the Transaction ID, you can quickly locate it within your platform. It also removes the need to reference Personally Identifiable Information which facilitates maintaining a high level of security.
Optional documents
App users have the ability to upload optional documentation where needed once their check has been completed. Your users will need to be able to obtain these files and review them, as they will not be embedded within the PDF report.
Multiple checks
Your integration must support the ability to initiate and display multiple checks and their statuses for the same phone number. This is important for cases where more than one check is required for the same individual.
Source of Funds - single task
For checks that require Source of Funds (SoF), your integration should allow for the initiation of singular Banking or Source of Funds Questionnaire tasks for an app user. Sometimes app users may need to re-do these tasks, and this prevents them from having to complete another full ID check.
Aborting
Your integration must support the ability to abort checks that are no longer required. Once a check is aborted, it should be clearly marked as such. Aborting a check will also prevent any reminder texts from being sent to the app user.
Partner integrations
In addition to the above, if you are a building a partner integration please factor in the below requirements too.
File ref prefix
Check file references must include a unique prefix to distinguish your transactions from others. For example, if your company is called 'Acme Law' your file reference might look like: Acme Law - Case 1234
Stub users impersonation
Your integration should factor in the creation and impersonating of stub users. Stub users are a representation within our platform of the user that undertook the action (e.g initiating or aborting a check) within your system.
Terms of Use acceptance
In order for your users to access and use any Thirdfort Services within your platform, they must agree to our Terms of Use. The Terms of Use must be agreed by one user on behalf of the entire organisation.
Sign-up notifications
We recommend setting up two automated emails when businesses (like law firms, estate agents, etc.) start using Thirdfort for the first time or are onboarded through your platform. These emails are best triggered when the user accepts Thirdfort’s terms as detailed above.