Entity verification documents
Learn how to provide the documents that entities need for seamless payments onboarding.
Overview
Before an [entity](../../entitiesindex can make or receive payments via Monite, it needs to provide the verification documents that prove the business registration and the identity of the business owners and key persons. Document verification is an essential part of the payments onboarding process.
Providing the documents is a two-step process:
- Upload the documents to Monite.
- Connect the uploaded documents to the entity.
Document types
Acceptable verification documents vary by country and may include:
- passport or identity card scans,
- business registration certificates,
- extracts from the national business registry,
- tax and/or VAT registrations,
- proof of bank accounts,
- and others.
Some document types require scans of both the front and back of the document.
Entity verification documents
The following document types are needed to verify the business information.
* The types correspond to the field names in the POST /onboarding_documents
request.
Person verification documents
This information applies only to entities of type “organization”. It does not apply to entities of type “individual”.
Entities of type “organization” may be required to provide information about their key persons during the onboarding process. The key persons include the primary representative, business owners, directors, and executives.
The following document types are needed to verify the identity and address of those persons.
* The types correspond to the field names in the POST /persons/{person_id}/onboarding_documents
request.
Step 1. Upload the documents
Start by uploading the documents or their scans to Monite. The documents are uploaded one by one.
To upload a single file, call POST /files
and provide the data as a multipart/form-data
request. Use the file
field to pass the file, and set the file_type
field to one of the following values:
identity_documents
- use this value when uploading company registration documents or a person’s identity documents,additional_identity_documents
- use this value when uploading documents that verify a person’s address.
The response returns the id
assigned to the uploaded file. Note it down as you will need it later.
Repeat the requests to POST /files
to upload all necessary documents.
Step 2. Connect the uploaded documents to the entity
Roles and permissions
To call the */onboarding_documents
endpoints with an entity user token, this entity user must have a role with the create
and update
permissions for onboarding
.
If using a partner-level token, no special permissions are needed.
Entity documents
To connect the uploaded documents to a specific entity, call POST /onboarding_documents
and provide the document IDs in the corresponding fields in the request body. For a list of the field names, see Entity verification documents.
Person documents
To connect the uploaded documents to a specific person, call POST /persons/{person_id}/onboarding_documents
and provide the document IDs in the corresponding fields in the request body. For a list of the field names, see Person verification documents.