Integrate TrustMe with OpenID Connect
Let your users share verified identity data and documents with your service, while staying in control of their information.
TrustMe is a digital identity that lets users share verified data with the services of their choice. With OpenID Connect (OIDC), your service can plug into this journey, receive the information the user authorizes and retrieve the documents they shared.
This documentation is for technical teams who want to integrate TrustMe into their service as a Relying Party (RP). It describes the sandbox environment; production uses the same interface, with its own configuration.
What TrustMe lets you do
- Sign a user in with a verified identity: you start a TrustMe journey and receive identity information checked by TrustMe, not merely declared by the user.
- Receive verified data: civil status, email, phone, address, bank account, social security number, depending on the scopes you request and the user accepts.
- Retrieve documents: identity document, address or bank proofs, through the document API.
- Complete a share later: with delayed sharing, you access information whose validation was not finished at sign-in time.
How does the integration work?
TrustMe uses the OpenID Connect Authorization Code flow. In practice:
- your service redirects the user to TrustMe, stating the information requested (the scopes);
- the user authenticates and gives consent in the TrustMe mobile app, by entering an identifier or scanning a QR code;
- they come back to your site with a single-use code;
- your server exchanges this code for an
id_token, which contains the shared information (the claims), and anaccess_token, which lets you download documents.
The integration relies on standard OIDC mechanisms, complemented by TrustMe-specific features: document sharing, delayed sharing and webhooks.
Vocabulary
| Term | Meaning |
|---|---|
| Identity Provider (IdP) | The service that knows the user and exposes the OIDC interface. Here: TrustMe. |
| Relying Party (RP) | Your service, which wants access to the user’s information. |
| Claim | A piece of identity information (given_name, email…). |
| Scope | A set of claims you request, or a journey option. |
| Token | A proof issued by TrustMe: id_token (shared information) or access_token (access to documents). |
| Document | A file the user can share (image or PDF). |
Before you start
TrustMe runs on the A3BC platform. The OIDC interface is shared, but each issuing entity (tenant) is segregated: you need a client_id and a client_secret specific to each entity you connect to.
- Understand OIDC: read the key concepts.
- Prepare and request access: decide your scopes, register your redirect URI, then follow the prerequisites and onboarding.
- Make a first call: play the quickstart or read the end-to-end example.