Menu
Frequently asked questions
Only the authorized signatory is authorized to sign the Terms and Conditions.
In CoorpID 4 user roles are defined with different permissions: Administrator, Manager, User and Observer. For more information see User management article or check the tab Roles & Permissions in the Access Management menu.
You need the administrator role to be able to invite new users. As an administrator this is easily done in the Access Management menu. See for more information the User management article.
Within CoorpID two types of partners exist: subscribed partners and unsubscribed partners. Subscribed partners can ask questions and request specific documents via so-called Partner Requests in CoorpID. You will see these requests as Tasks on your overview page. Unsubscribed partners can only receive documents via a Winzip file or an encrypted link with SMS-verification. See for more information this article.
Yes, you can use the tool with other banks or partners than ING. Even if another bank is not subscribed to the CoorpID platform, you can still share your documents using CoorpID with that bank. See for more information Sharing of documents article and Relationships article.
You are fully in control over what you share and with whom. A partner only has access to the documents that are shared by you. Moreover, you can always revoke access for one or more partners.
Yes, a partner can download the documents you have shared. The documents will always be downloaded in PDF format.
You can track the status of each document in CoorpID via the audit log, which you can also download. Besides that, the status of a document can be updated by the partner. See for more information this article.
Make sure the time on your phone matches the time on your laptop. Since the code is only valid for 30 seconds, it doesn’t work if the times are not synchronized. Another reason could be if you have multiple (CoorpID) accounts in your authenticator app. Make sure to select the corresponding account.
You want to use a new phone for the two-factor authentication to sign in to CoorpID. This requires additional verification. Please contact the CoorpID team for support.
The link to activate your user account expires after 5 days. This is a security measure, to prevent potential misuse. If your link is expired, please ask the person who invited you to resend the invite.
You expect an email with an invite to activate your CoorpID user account, and can’t find it. Sometimes, these emails are inadvertently marked as spam, junk or unwanted email. Have a look at the corresponding folder to locate the email from CoorpID.
When approving, the user of CoorpID agrees to the Terms of Use. The Terms of Use can be found on https://www.coorpid.com/terms
Like ING, CoorpID uses servers of Microsoft Azure. These servers are located in Western Europe.
CoorpID follows the data regulation standards and client information (including documents) will be deleted from the platform after a period of 7 years. Clients are also able to retract the documents they have uploaded. CoorpID does not have control over the documents that were downloaded by partners.
ING and CoorpID don’t have access to the data in CoorpID. Only when clients explicitly request to share documents, these specific documents will be shared with ING and/or other partners.
All information in the CoorpID environment is encrypted. CoorpID’s security measures are governed by ING risk and control policies. An example is two-factor-authentication for login.
Currently, the CoorpID platform is only available in English.
CoorpID doesn’t provide dummy environments, however there is a demo available at the CoorpID website. Check the link in the navigation bar in the top of your browser.
You cannot digitally sign documents in CoorpID. We are working on features that will make this available in the future.
The client is and always will be owner of the data. The client is also responsible for the information he/she shares.
CoorpID is an initiative of ING Bank N.V. and is fully owned by ING Bank N.V.
All communication regarding your KYC review goes via your bank’s contact person and/or KYC analyst. CoorpID is not involved in the content of the KYC review.
CoorpID needs to be filled by clients themselves with their company information. ING or any other partner is not able to pre-fill CoorpID with available information.
Like ING, CoorpID uses servers of Microsoft Azure. These servers are located in Western Europe.
All information in the CoorpID environment is encrypted. CoorpID’s security measures are governed by ING risk and control policies. An example is two-factor-authentication for login.
The client is and always will be owner of the data. The client is also responsible for the information he/she shares.
The admin and team managers, manage the access to client information. Please contact your admin or team manager for more information.
On the page where the client has uploaded the documents, there is a panel on the righthand side. The person who shared the package can be found under the tab ‘Info’.
Corporates can use the CoorpID functionality to help them create the ownership structure (org chart). They can also attach a PDF of their already available structure. The CoorpID chart is identified as “System generated” whereas the user uploaded org chart has the name of the authorized person who has uploaded the org chart.
This is correct, only when the client has accepted the invitation, the package will become visible in the Corporates overview.
Copyright © 2022 CoorpID. All rights reserved.
Cookie | Duration | Description |
---|---|---|
ARRAffinity | session | ARRAffinity cookie is set by Azure app service, and allows the service to choose the right instance established by a user to deliver subsequent requests made by that user. |
ARRAffinitySameSite | session | This cookie is set by Windows Azure cloud, and is used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session. |
cookielawinfo-checkbox-advertisement | session | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | session | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
gtm_internal_user | 1 year | This cookie is set to identify internal users and to exclude them in analytics and campaigns. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
Cookie | Duration | Description |
---|---|---|
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
Google Analytics | 2 years | Cookies that start with _ga, _gid en _utm are placed by Google and are used to keep anonymised visitor statistics. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
Cookie | Duration | Description |
---|---|---|
This cookie is used so you can share information from our website with others via LinkedIn. Cookies starting with li are used by LinkedIn for tracking the use of embedded services | ||
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |