Welcome to the Yoti NodeJS SDK. This repo contains the tools and step by step instructions you need to quickly integrate your NodeJS back-end with Yoti so that your users can share their identity details with your application in a secure and trusted way.
-
An Architectural View - High level overview of integration
-
References - Guides before you start
-
Requirements - Check you have what you need
-
Installing the SDK - How to install our SDK
-
Configuration - How to initialise your configuration
-
Profile Retrieval - How to retrieve a Yoti profile using the token
-
Handling Users - How to manage users
-
AML Integration - How to integrate with Yoti's AML (Anti Money Laundering) service
-
API Coverage - Attributes defined
-
Support - Please feel free to reach out
To integrate your application with Yoti, your back-end must expose a GET endpoint that Yoti will use to forward tokens. The endpoint can be configured in Yoti Dashboard when you create/update your application.
The image below shows how your application back-end and Yoti integrate in the context of a Login flow. Yoti SDK carries out for you steps 6, 7 ,8 and the profile decryption in step 9.
Yoti also allows you to enable user details verification from your mobile app by means of the Android (TBA) and iOS (TBA) SDKs. In that scenario, your Yoti-enabled mobile app is playing both the role of the browser and the Yoti app. By the way, your back-end doesn't need to handle these cases in a significantly different way. You might just decide to handle the User-Agent
header in order to provide different responses for web and mobile clients.
If you're planning on using the Node SDK on Windows, you'll need to install a few dependencies first:
-
OpenSSL (normal version, not light) in the same bitness as your Node.js installation.
- OpenSSL must be installed in its specific directory (
C:\OpenSSL-Win32
orC:\OpenSSL-Win64
) - The latest version of OpenSSL (v1.1.x) does not have the
libeay32.dll
file. Install v1.0.2 instead. - If you get
Error: The specified module could not be found.
, copylibeay32.dll
from the OpenSSL bin directory to this module's bin directory, or toWindows\System32
.
- OpenSSL must be installed in its specific directory (
-
node-gyp (
npm install -g node-gyp
)- Either install Microsoft's windows-build-tools using
npm install --global --production windows-build-tools
- Or manually install Python 2.7 and Visual Studio (or modify an existing installation) and select Common Tools for Visual C++ during setup.
- Either install Microsoft's windows-build-tools using
To import the Yoti SDK inside your project, you can use your favourite dependency management system. If you are using NPM, you can use the following command to set the Yoti SDK as a dependency:
npm install -S -E yoti
Your package.json file will then be updated to include:
"dependencies": {
"yoti" : "x.x.x"
}
The YotiClient is the SDK entry point. To initialise it you need include the following snippet inside your endpoint initialisation section:
const yoti = require('yoti')
const CLIENT_SDK_ID = 'your sdk id'
const PEM = fs.readFileSync(__dirname + "/keys/your-application-pem-file.pem");
let yotiClient = new yoti.Client(CLIENT_SDK_ID, PEM)
Where:
-
APPLICATION_ID
is the identifier generated by Yoti Dashboard when you create your app. -
CLIENT_SDK_ID
is the SDK identifier generated by Yoti Dashboard in the Key tab when you create your app. Note this is not your Application Identifier which is needed by your client-side code. -
path/to/your-application-pem-file.pem
is the path to the application pem file. It can be downloaded only once from the Keys tab in your Yoti Dashboard.
Please do not open the pem file as this might corrupt the key and you will need to create a new application.
The way the Yoti SDK client is initialised got changed in version 3. Please make sure you update your code if you're upgrading the npm package.
// SDK version < 3
const Yoti = require('yoti')
const yotiClient = new Yoti(CLIENT_SDK_ID, PEM)
// SDK version >= 3
const yoti = require('yoti')
const yotiClient = new yoti.Client(CLIENT_SDK_ID, PEM)
When your application receives a token via the exposed endpoint (it will be assigned to a query string parameter named token
), you can easily retrieve the user profile by adding the following to your endpoint handler:
yotiClient.getActivityDetails(token).then((activityDetails) => {
//handle response here
})
Before you inspect the user profile, you might want to check whether the user validation was successful. This is done as follows:
yotiClient.getActivityDetails(token).then((activityDetails) => {
if(activityDetails.getOutcome() == 'SUCCESS') {
const profile = activityDetails.getProfile();
} else {
// handle unhappy path
}
})
When you retrieve the user profile, you receive a user ID generated by Yoti exclusively for your application. This means that if the same individual logs into another app, Yoti will assign her/him a different ID. You can use this ID to verify whether (for your application) the retrieved profile identifies a new or an existing user. Here is an example of how this works:
yotiClient.getActivityDetails(token).then((activityDetails) => {
if(activityDetails.getOutcome() == 'SUCCESS') {
const userProfile = activityDetails.getUserProfile(); // deprecated
const profile = activityDetails.getProfile();
const user = yourUserSearchFunction(activityDetails.getUserId());
if(user) {
// handle login
} else {
// handle registration
const givenNames = profile.getGivenNames().getValue();
const familyName = profile.getFamilyName().getValue();
}
} else {
// handle unhappy path
}
})
Where yourUserSearchFunction
is a piece of logic in your app that is supposed to find a user, given a userId.
No matter if the user is a new or an existing one, Yoti will always provide her/his profile, so you don't necessarily need to store it.
The profile
object provides a set of attributes corresponding to user attributes. Whether the attributes are present or not depends on the settings you have applied to your app on Yoti Dashboard.
You can retrieve the sources and verifiers for each attribute as follows:
const givenNamesSources = givenNames.getSources(); // list/array of anchors
const givenNamesVerifiers = givenNames.getVerifiers(); // list/array of anchors
You can also retrieve further properties from these respective anchors in the following way:
// Retrieving properties of the first anchor
const value = givenNamesSources[0].getValue(); // string
const subtype = givenNamesSources[0].getSubType(); // string
const timestamp = givenNamesSources[0].getSignedTimeStamp().getTimestamp(); // Date object
const originServerCerts = givenNamesSources[0].getOriginServerCerts(); // list of X509 certificates
Yoti provides an AML (Anti Money Laundering) check service to allow a deeper KYC process to prevent fraud. This is a chargeable service, so please contact [email protected] for more information.
Yoti will provide a boolean result on the following checks:
- PEP list - Verify against Politically Exposed Persons list
- Fraud list - Verify against US Social Security Administration Fraud (SSN Fraud) list
- Watch list - Verify against watch lists from the Office of Foreign Assets Control
To use this functionality you must ensure your application is assigned to your organisation in the Yoti Dashboard - please see here for further information.
For the AML check you will need to provide the following:
- Data provided by Yoti (please ensure you have selected the Given name(s) and Family name attributes from the Data tab in the Yoti Dashboard)
- Given name(s)
- Family name
- Data that must be collected from the user:
- Country of residence (must be an ISO 3166 3-letter code)
- Social Security Number (US citizens only)
- Postcode/Zip code (US citizens only)
Performing an AML check on a person requires their consent. You must ensure you have user consent before using this service.
Given a YotiClient initialised with your SDK ID and KeyPair (see Configuration) performing an AML check is a straightforward case of providing basic profile data.
// Initiate user profile data.
const amlAddress = new Yoti.AmlAddress('GBR');
const amlProfile = new Yoti.AmlProfile('Edward Richard George', 'Heath', amlAddress);
yotiClient.performAmlCheck(amlProfile).then((amlResult) => {
console.log(amlResult.isOnPepList);
console.log(amlResult.isOnFraudList);
console.log(amlResult.isOnWatchList);
// Or
console.log(amlResult);
}).catch((err) => {
console.error(err);
})
The example can be found here.
- From the Yoti Dashboard set the application domain of your app to
localhost:9443
- Set the scenario callback URL to
/profile
- Rename the .env.example file to
.env
and fill in the required configuration values - Install the dependencies with
npm install
- Start the server
node index.js
Visiting the https://localhost:9443
should show a Yoti Connect button
The example can be found here.
- rename the .env.example file to
.env
and fill in the required configuration values - install the dependencies with
npm install
- run the script with
node aml.js
ornode aml-usa.js
In order to get the users information, the Node SDK will decrypt the token in the callback URL. Use the following code to do this:
yotiClient.getActivityDetails(token).then((activityDetails) => {
const userProfile = activityDetails.getUserProfile(); // deprecated
// Use the table below to retrieve specific attributes from the profile object
})
- Activity Details
- User ID
.getUserId()
- Base64 Selfie Uri
getBase64SelfieUri()
- Profile
.getProfile()
- Full Name
getFullName().getValue()
- Full Name
- userProfile
.getUserProfile()
- Photo
selfie
- Full Name
fullName
- Given Names
givenNames
- Family Name
familyName
- Mobile Number
phoneNumber
- Email address
emailAddress
- Age / Date of Birth
dateOfBirth
- Age / Verify Condition
isAgeVerified
- Address
postalAddress
- Gender
gender
- Nationality
nationality
- Photo
- User ID
For any questions or support please email [email protected]. Please provide the following to get you up and working as quickly as possible:
- Computer type
- OS version
- Version of Node being used
- Screenshot
Once we have answered your question we may contact you again to discuss Yoti products and services. If you’d prefer us not to do this, please let us know when you e-mail.