Purse Identity OpenID Connect Provider
Purse Identity, formerly ReachFive, is a SaaS, API-first customer identity and access management (CIAM) platform now part of Purse alongside its payment orchestration products. It combines authentication (password, social login, passkeys and FIDO2, passwordless by email magic link or SMS code), MFA by email or SMS with step-up and risk-based authentication, SSO and cross-domain sessions, and a consent and preference center with double opt-in and full traceability for GDPR. Fraud protection covers bots, credential stuffing, breached credentials, rate limiting and account lockout. It acts as a partially implemented OpenID Connect provider (authorization code with PKCE, implicit, ROPC, refresh tokens with rotation) and can act as an OpenID provider for partner sites. Delivered through hosted pages, JavaScript, iOS and Android SDKs, and a Management API. Pricing is quote-based.
Features
If you want to compare OpenID Connect features of different providers, please check out the OpenID Connect Providers benchmark.
Looking for Purse Identity’s (C)IAM features like MFA, SSO, and user management? View Purse Identity on the (C)IAM Identity Providers benchmark.
Frequently Asked Questions
Does Purse Identity support the Authorization Code grant type?
Purse Identity supports Authorization Code grant type. The authorization code flow is supported through the /oauth/authorize endpoint. Read more
Does Purse Identity support the Refresh Token grant type?
Purse Identity supports Refresh Token grant type. Refresh tokens are available for first-party and third-party clients with the offline_access scope. Default lifetime is 90 days, configurable from 1 to 365 days. Read more
Does Purse Identity support the Implicit grant type?
Purse Identity supports Implicit grant type. The implicit flow can be configured for first-party clients only, and is ruled out when PKCE is enforced. Read more
Does Purse Identity support the Resource Owner Password Credentials grant type?
Purse Identity supports Resource Owner Password Credentials grant type. The ROPC flow is available for first-party clients, can be disabled, and the documentation advises against it, especially for public clients. Read more
Does Purse Identity support the PKCE extension?
Purse Identity supports PKCE extension. PKCE is supported, can be enforced per client, and is the only authorization code option for third-party clients besides refresh tokens. Read more
Does Purse Identity support the Authorization Endpoint endpoint?
Purse Identity supports Authorization Endpoint endpoint. The authorization endpoint is /oauth/authorize. Read more
Does Purse Identity support the Token Endpoint endpoint?
Purse Identity supports Token Endpoint endpoint. An OAuth 2.0 token endpoint is provided. Read more
Does Purse Identity support the UserInfo Endpoint endpoint?
Purse Identity supports UserInfo Endpoint endpoint. Authorized user data is available from /identity/v1/userinfo or by decoding the id_token. Read more
Does Purse Identity support the Token Revocation endpoint?
Purse Identity partially supports Token Revocation endpoint. Refresh tokens can be revoked through the Identity API revokeToken operation; a standard RFC 7009 endpoint is not documented. Read more
Does Purse Identity support the OpenID Connect Discovery Endpoint endpoint?
Purse Identity supports OpenID Connect Discovery Endpoint endpoint. The discovery document is served at /.well-known/openid-configuration, with signing keys at /jwks.json. Read more
Does Purse Identity support the Refresh Token Rotation feature?
Purse Identity supports Refresh Token Rotation feature. Refresh tokens are single-use. Reusing one invalidates the other tokens and the user session tied to that client_id. Read more
Compare with other providers
Note: The current data is based on provider documentation/experience and may not be 100% accurate.