How actions work
From the case file you ask your client for documents, up to twenty files at a time and at most 10 MB per file. You have a contract from the contract builder or your own PDF signed. Your client fills in a form, such as the UBO declaration. When you send a procedure through the API, you pass along the data you already hold. A questionnaire, such as the risk questionnaire, gives you a risk profile.
Your client receives an email from your firm with a login code and completes the action in the client portal. Whatever they supply, fill in or sign lands in the case file with a date, as does the outcome of the identity verification. Afterwards they receive a confirmation of receipt.
Several actions in a row you bundle into a procedure. An action can also be a step in a workflow, for example as soon as a case file is created. Whether you send it yourself or a workflow does, the outcome lands in the same place in the case file.
Remote identification and the Wwft
Article 3(2)(a) Wwft requires you to identify the client and verify their identity. For a natural person, Article 11(1) Wwft requires verification on the basis of documents, data or information from a reliable and independent source.
The identity verification in the portal compares the identity document with a selfie. In your policy you set when that method is enough, under your supervisor’s guidance.
Frequently asked questions
Can't find your question? Get in touch. Response within one business day.