Odds are you’re one of the 8-million people who has been using SecureKey’s services for years without even knowing it. Since 2012, their digital identity service has provided Canadians the ability to access their Canada Revenue Agency accounts (and a number of other federal services) using their bank login. It’s a perfect use case to illustrate the digital identity problem.
“The challenge they had,” says SecureKey’s Andre Boysen, “is when you and I and everyone else want to access services online at government, we haven’t been there for a year. So every single time we come to the CRA, we forgotten our password.”
Not unlike SSO login options that allow you to sign in using your Google or Facebook account, SecureKey’s web-based Concierge platform allows you to log in to government sites using your bank ID – a password that you already use regularly and (hopefully) treat with high degree of security. The difference is, unlike Facebook or Google, Secure Key never sees your information, nor does your bank know which service you’ve logged in to, nor does the government know which bank (or other identity provider) you used to authenticate your identity.
“This has been transformational for the government,” Boysen says. “The number of people doing transactions online has increased dramatically, and, more importantly, their costs have come down, and their business confidence that Andre is actually Andre has gone way up.”
Early in 2019 SecureKey will be rolling out Verified.Me, a native mobile app that allows users to provide and manage verified identity profiles from a network of Tier 1 banks, telcos, governments, credit agencies and more (full disclosure: TWG is one of several authorized Verified.Me implementation partners). As a mobile-first identity product, SecureKey envisions a wide range of practical and effective real-world applications.
“What this means as Canadians, you can choose your favorite bank and telco and I can choose my favorite back my favorite telco to assemble a digital identity that allows you to prove your identity and a trustworthy way. Perhaps you’ve got an apartment listed for sale that I want to rent. Today we find each other on Kijiji, and you as a landlord and me as a tenant both have a problem. I want to make sure that you actually own this place and you’re not trying to trick me out of first and last month’s rent. And you want to know that I’ve got good credit, that I’m trustworthy.”
“This service is designed to give both parties in this transaction trust that they can do this deal, two people who have never met. So when I can provide my income details from my bank, and proof of my cell phone and my credit score to you, as a landlord, you’re gonna have good confidence that I’m a good credit risk, I can close the deal with you right there in the apartment.”
Verified.Me already has all major Canadian banks and telcos integrated into the platform, and over 80 government services — both federal and provincial — will be available at launch. The core value of the platform is its ability to provide a digital verified identity, and the assurance that the 3rd-party information provided by the customer can be trusted.
“In order for me to get a bank loan today, if I’m a small business operator in Canada, I won’t have a typical T4 from a large company, so when I go to the bank, they don’t always believe my income. With this new service that’s emerging if I can prove who I am to CRA, and they can have confidence Andre is Andre, CRA now can give me a digitally-signed claim back proving my income from last year, I can now give this over to the bank and an electronic format.”
“This does several things for the bank — it takes their costs down, their business confidence in the information is higher, because it can’t be altered. It’s been signed by the government, and the number of people that successfully complete the process is actually going to be much, much higher. That’s not (just) about identity, that’s about taking taken transaction friction away, so consumers can do the things they want to do online that they can’t do today.”
Feb 2 • 3 min read
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checbox-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-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-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-advertisement | 1 year | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Advertisement". |
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-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". |
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 |
---|---|---|
bcookie | 2 years | This cookie is set by linkedIn. The purpose of the cookie is to enable LinkedIn functionalities on the page. |
lang | session | This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website. |
lidc | 1 day | This cookie is set by LinkedIn and used for routing. |
Cookie | Duration | Description |
---|---|---|
YSC | session | This cookies is set by Youtube and is used to track the views of embedded videos. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
_gid | 1 day | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form. |
_hjFirstSeen | 30 minutes | This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. |
pardot | past | The cookie is set when the visitor is logged in as a Pardot user. |
Cookie | Duration | Description |
---|---|---|
bscookie | 2 years | This cookie is a browser ID cookie set by Linked share Buttons and ad tags. |
IDE | 1 year 24 days | Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile. |
personalization_id | 2 years | This cookie is set by twitter.com. It is used integrate the sharing features of this social media. It also stores information about how the user uses the website for tracking and targeting. |
test_cookie | 15 minutes | This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website. |
Cookie | Duration | Description |
---|---|---|
_gat_UA-78951495-1 | 1 minute | No description |
_hjAbsoluteSessionInProgress | 30 minutes | No description |
_hjid | 1 year | This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
_hjIncludedInPageviewSample | 2 minutes | No description |
AnalyticsSyncHistory | 1 month | No description |
CONSENT | 16 years 9 months 2 days 8 hours 3 minutes | No description |
UserMatchHistory | 1 month | Linkedin - Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences. |