OpenID Connect · RS256

Beyond Passwords:
Verified Identity
as a Service

ProntoID functions as a fully standards-compliant OIDC identity provider. Partner platforms integrate once via OAuth 2.0 and receive cryptographically signed ID tokens containing real, document-verified claims — not just a username and password.

Start Integration View Documentation
OIDC / OAuth 2.0
Standard Protocol
RS256
Token Signing
<2s
Token Delivery
ProntoID ID Token
RS256-signed · OpenID Connect
Verified
// JWT Payload — decoded claims

{
  "iss": "https://prontoid.com",
  "sub": "usr_a7f3c9e1b2d4",
  "aud": "your-client-id",
  "iat": 1749600000,
  "exp": 1749686400,

  // Standard identity claims
  "given_name": "Maria",
  "family_name": "Rossi",
  "birthdate": "1990-04-12",
  "nationality": "Italian",

  // ProntoID verified claims
  "https://prontoid.com/age_verified": true,
  "https://prontoid.com/identity_verified": true,
  "https://prontoid.com/document_type": "passport",
  "https://prontoid.com/liveness_passed": true
}
Document Verified Liveness Checked Privacy Preserved GDPR Compliant
The Problem

Usernames are
not identities

Traditional authentication tells you someone knows a password. It tells you nothing about who they actually are. Platforms that need to know a user is who they claim to be — a real person, of legal age, with a verified identity — have historically had no standard way to get that guarantee.

Custom verification pipelines are expensive to build, hard to maintain, and create friction for users. ProntoID solves this with a standard OIDC integration that any platform can adopt in hours.

No Proof of Identity

Standard login systems verify a credential, not a person. Self-declared identity is trivially faked, exposing platforms to fraud and regulatory risk.

Build-Your-Own Is Broken

Custom verification flows fragment the user experience, duplicate expensive infrastructure, and create bespoke security surfaces that are hard to audit.

Compliance Is Multiplying

Age verification mandates, KYC requirements, and data residency laws are expanding globally. Keeping a homegrown solution current is a full-time job.

How It Works

Standard OAuth 2.0 flow,
extraordinary claims

If your platform already supports "Login with Google" or "Login with Apple", you can integrate ProntoID in the same way — with the addition of real-world identity claims in every token.

1
Redirect

Your platform redirects the user to ProntoID's authorization endpoint with your client_id and requested scopes.

2
Verify

The user completes document verification and liveness check on ProntoID's secure, privacy-isolated flow.

3
Exchange

Your server exchanges the one-time authorisation code for an access token and RS256-signed ID token at the token endpoint.

4
Consume

Validate the JWT signature with ProntoID's public JWKS, then read the verified claims directly from the payload.

RS256 Token Anatomy

What Your Platform Receives

Every claim is document-verified, not self-declared

Standard Claims
iss · sub · aud · iat · exp
Identity Claims
given_name · family_name · birthdate · nationality
Verified Claims
age_verified · identity_verified · document_type · liveness_passed
Signature verified via JWKS endpoint
Cryptographic Trust

RS256: Trust You
Can Verify

Every ID token is signed with ProntoID's RSA private key and verifiable against our public JWKS endpoint. No shared secrets, no back-channel calls required — your platform independently validates every token it receives.

No Shared Secrets
Asymmetric signing means your platform never holds a ProntoID secret key. Rotate keys at any time without coordinating with partners.
Offline Verification
Cache the public JWKS and verify tokens entirely client-side — no round-trip to ProntoID required on every authenticated request.
Tamper-Evident Claims
Any modification to the token payload after signing immediately invalidates the signature. Verified claims are guaranteed unaltered.
Why ProntoID OIDC

The identity layer your
platform has been missing

Standards-Based

Full OpenID Connect 1.0 and OAuth 2.0 compliance. Works with any library or SDK that supports OIDC — no proprietary SDKs required.

Document-Backed Claims

Claims are sourced from government-issued identity documents, not self-declaration. Real names, real birthdates, real nationalities.

Liveness-Confirmed

Every identity is matched to a live person via biometric liveness detection. Protect against synthetic identities and account takeover.

Privacy by Design

You receive verified claims, not raw document data. ProntoID never discloses the underlying documents to your platform.

190+ Countries

Document verification covers passports, national IDs, and driving licences from over 190 countries — one integration, global reach.

Hours, Not Months

Integrate via our developer portal with a complete OIDC discovery document, JWKS endpoint, and example code in multiple languages.

Use Cases

Who integrates
ProntoID OIDC?

Dating & Social Platforms

Verify that users are real adults with government-issued identity documents before they can connect with others. Reduce catfishing, fraud, and minor access in a single integration.

Age Verification Real Identity Liveness Check
Content & Media Platforms

Meet age verification mandates from ARCOM, AGCOM, and Visa/Mastercard scheme rules without building verification infrastructure. Receive a signed token; serve the content.

ARCOM Compliant AGCOM Compliant Card Scheme Ready
Regulated Industries

Financial services, legal platforms, healthcare portals, and marketplaces that require KYC-equivalent onboarding can delegate identity verification to ProntoID and receive claims via OIDC.

KYC-Grade Claims Audit Trail GDPR Compliant
Marketplaces & Gig Platforms

Establish trust between participants by offering a "ProntoID Verified" badge. Verified sellers, drivers, hosts, and service providers carry document-backed identity that builds confidence across both sides of the market.

Seller Verification Buyer Trust Fraud Reduction
Quick Start

Live in hours,
not weeks

ProntoID publishes a standard OIDC discovery document at /.well-known/openid-configuration. Any standards-compliant OIDC library will auto-configure from that endpoint.

1
Register

Create a developer account, add your platform, and collect your client_id and client_secret from the portal.

2
Configure

Point your OIDC library at https://prontoid.com and set your redirect URI. Discovery handles the rest.

3
Go Live

Initiate the auth flow, exchange the code, and validate the RS256 ID token. Your verified claims are ready.

Open Developer Portal
Discovery Endpoints
// Auto-configure any OIDC library
issuer: https://prontoid.com

// Discovery document
GET https://prontoid.com/.well-known/
     openid-configuration

// Token endpoint
POST https://prontoid.com/oauth/token

// Public signing keys
GET https://prontoid.com/.well-known/jwks.json
Token Validation (PHP)
// Fetch JWKS and validate RS256 token
$jwks = fetch('https://prontoid.com/.well-known/jwks.json');
$claims = JWT::decode($idToken, $jwks);

// Read verified claims
$isAdult = $claims->'https://prontoid.com/age_verified';
$name = $claims->given_name . ' ' . $claims->family_name;

// No PII stored — just trust the claim

Ready to add verified
identity to your platform?

Register on the developer portal, pick up your OIDC credentials, and start receiving RS256-signed identity tokens today.

Schedule a Demo View Documentation

No credit card required  ·  Free developer account  ·  Live in hours