Developer Introduction

Welcome to the Trustbind developer documentation (please note that our Single Sign On (SSO), ADFS and RADIUS/OTP documentation is found here).

Trustbind is a user authentication service which completely replaces the typical password-based authentication which is normally used when accessing online services, so removes your largest cyber-security risk, and streamlines your user experience to increase customer satisfaction.

Once your website/application is configured, when your users click to login they are presented with our simple PIN interface (the 'M-Pad') to register and authenticate themselves:


Here you will find all you need to integrate the Trustbind secure login system into your own website/application and deliver the highest level of security for users logging in to your services.

How to use this documentation

To gain a full understanding of how our basic authentication works it is recommended that you read through the introductory explanations given in 'Register / Create a new app' (explains how to register and obtain keys for a new service/app in the administration portal), 'Authorization Flow Explained' and 'Intro to the Login Button'.

You can then learn:

  1. In Web SDK instructions, how to use any of our basic web SDKs (based on the OpenID Connect authentication protocol). This section expands on the 'Authorization Flow Explained' page and appropriates it to the language of each SDK. Here you will find the basic SDK installation process with sample apps for each SDK, and a breakdown of the code involved in creating apps.

  2. In Mobile SDK instructions, how to make a custom app which can be used as a mobile PIN pad for logging into websites (as an alternative to our own Trustbind authenticator app found in the app stores), or a self-contained app which logs in to itself.

  3. Back in Web SDK instructions, how to use our web SDKs to make use of our Pluggable Verification feature. PV can be used to add an extra layer of security by allowing use of other factors to verify a user for their one-off initial registration (activation codes, account numbers, scanned id documents, etc. can be used instead of a standard ‘click on an email verification link’). Currently only the .NET and .NET Core (documentation coming soon) SDKs support this.

  4. In both Web SDK instructions and Mobile SDK Instructions, how to make use of our Digital Verified Signature (DVS) feature. Our DVS scheme can be used to sign in-app transactions for documents and verification of payments. Of the web SDKs, currently only .NET and .NET Core (documentation coming soon) support this. DVS is supported by both our Android and iOS SDKs.

Again, please note that our Single Sign On (SSO), ADFS and RADIUS/OTP documentation is found here

Developer note: For developers wishing to implement their own OIDC code without the assistance of our SDKs, the issuerURL is

Finally, there is an Admin Portal Guide, which gives instructions on how to make use of the Trustbind authentication portal dashboard to manage your apps, as well as access statistical overviews and reports.