Adopting innovative technology – Digital ID Systems- Consultation Outcome
In August we wrote about the challenges of confirming your identification. We also discussed the consultation process underway in Jersey regarding the adoption of Digital ID Systems. As a reminder, the paper told us there were three main barriers to adoption:
The consultation proposed three options to address some of these barriers:
Our position regarding the consultation was:
As neither a Digital ID Systems Provider, nor a Supervised Person, we stuck our head above the parapet. Option 1, in our view, must happen. But there also needs to be consistent application of the regime amongst the Supervisors, and an open dialogue between Supervisors and Supervised Persons on the use of technology and how it supports regulatory requirements within a Supervised Persons’ Risk Framework.
Option 2 is a good idea and one we fully support. The Digital ID Systems Providers we know would be willing to get accredited to help clients be comfortable with using the technology as part of their overall process. Unfortunately, it’s not a quick solution to work out an accreditation regime, get accreditors and start the process, but we’ve got an opportunity to push for clarity and make it easier for digital adoption by Supervised Persons.
Option 3 is unlikely to work. While Jersey-based Digital ID Solution Providers might consider it, those based outside Jersey are unlikely to want to become subject to its regulatory regimes, nor are they being asked to in most other jurisdictions. Requiring this would likely reduce the number of options available to Supervised Persons, defeating the global nature of our industry in Jersey, and the purpose of this consultation.
The response was published at the end of November, making for interesting reading. While there was a high degree of engagement across the industry, the reactions to the individual proposals were, unsurprisingly to us, highly polarised. Concerns tended to focus on the practical realities of implementation but often gave suggestions which have shaped the next steps, so kudos to those who responded as it seems to have resonated.
Respondents confirmed that the barriers to adoption noted above were correct. Other barriers were also noted, including:
Before this consultation, two prior consultations into a “Shared KYC Utility” (a centralised platform where customer identification and verification could be undertaken once for a customer rather than several times by different Supervised Persons) were conducted. The unwillingness to adopt this previously stemmed from issues with Jersey-based subsidiaries and branches adopting a Jersey-specific process that might not be interoperable with cross-border standards. This consultation also considered whether the sentiment has changed in 2022. While there was more support for it, there were still barriers raised, making it difficult to implement:
Outcomes:
Option 1 More Clarity in Handbooks
The feedback unanimously supports further clarity within the AML/CFT handbook regarding the use of Digital ID Systems and will be progressed. In addition, the Money Laundering Order will also need to be updated to include more clarity regarding Digital ID Systems.
Option 2 – Accredited Framework
Feedback on this option supported some accreditation framework or other minimum technical standards to which Digital ID Systems should adhere, although there were a number of concerns, including the cost of accreditation, risk that a Jersey-based Framework would prove a barrier to entry for RegTech starts up and that it could not conflict with international standards to ensure it would be accepted for equivalence in other jurisdictions.
Further exploration will be undertaken, drawing on resources and experiences of other jurisdictions, on the introduction of guidance on how IDPS’s should operate, including reference to international standards.
Option 3 – Create a new class of Supervised Person where Digital ID Providers would become Supervised Persons
While there was a mixed view about the effectiveness of this option, significant challenges were raised, including IDSP’s not wanting to become regulated, it being the most expensive option, and it might end up being limited to Jersey-based businesses, eliminating non-Jersey-based providers and reducing competition. Most respondents felt this option would be prohibitively expensive. The result is that this option does not appear viable for Jersey at this time and will not be pursed at present.
Next Steps
Option one – will proceed as planned, with changes to Section 4 of the AML/CFT Handbook and updating of the MLO. Early, quick technical amendments are being made before the end of 2022 to update Section 4 of the AML/CFT Handbook, while Amendment to the MLO will start during Q1 2023.
Option Two – will proceed with modifications. For this option, Government will continue to monitor emergent international technical standards with a focus on the UK and other Crown Dependencies, to determine best practices and to assess how it can appropriately articulate technical standards.
Option Three – will not proceed at present
Domestic Inter-Agency Co-operation
Respondents identified that in addition to implementing Option 1 and aspects of Option 2, further cooperation between the JFSC, Government, Jersey Finance and Digital Jersey is required to ensure a shared understanding of the approach to Digital ID systems and their use cases.
Digital Jersey and Jersey Finance will develop educational events and materials further to support the adoption of Digital ID Systems under Fintech.je banner, such work to start early in 2023.
An outreach and engagement programme related to Digital ID Adoption systems in Jersey will launch in Q1 2023
During Q3 2023, relevant global standards for IDSP’s will be considered, guidance notes prepared, and more substantial amendments to Section 4 of the AML/CFT Handbook will be provided.
It’s great to see that respondent feedback has shaped the outcome. While it’s not the perfect solution for everyone, it’s certainly a step in the right direction.
For the full Consultation Paper Result, please see Digital ID Adoption Consultation Outcome Report
Please click on the button below to download the full article.
You can find more articles on our website, at Phundex Knowledge Hub, on LinkedIn at Phundex LinkedIn, or for other questions, please email us at: hello@phundex.com.
Not already a member of the Phundex LinkedIn Group? Join now for early updates and news Phundex LinkedIn Group
To book a demo or do a trial, you can either use the link on our website or email support@phundex.com, and they will be happy to set it up for you.
Get a one-to-one demo
Discover how Phundex can streamline your transactions and processes
Copyright Phundex 2024
PHUNDEX UK LIMITED
Registered Office :
128 City Road, London, UK, EC1V 2NX
Trading Office :
68 Summers Road, Godalming, Surrey, UK, GU7 3BE
Phundex Limited is registered in Jersey, Channel Islands, No 131447, Registered with the Information Commissioner’s Office in the UK in compliance with the Data Protection (Charges and Information) Regulations 2018 under registration ZA839762 and in Jersey in compliance with Regulation 4(1) of the Data Protection (Registration and Charges) (Jersey) Regulations 2018 under registration 68186
Phundex UK Ltd is registered in England & Wales No. 12207772, Registered with the Information Commissioner’s Office in the UK in compliance with the Data Protection (Charges and Information) Regulations 2018 under registration ZB285669
Cookie | Duration | Description |
---|---|---|
_GRECAPTCHA | 5 months 27 days | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
cookielawinfo-checkbox-advertisement | 1 year | 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 | 1 year | 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. |
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. |
Cookie | Duration | Description |
---|---|---|
ajs_anonymous_id | 1 year | This cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before. |
ajs_user_id | never | This cookie is set by Segment to help track visitor usage, events, target marketing, and also measure application performance and stability. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
Cookie | Duration | Description |
---|---|---|
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. |
Cookie | Duration | Description |
---|---|---|
__tld__ | session | No description |