Third-party e-commerce / loyalty / marketplace apps embed a Sign-in-with-Fidaty button. Consumer consents, partner receives an access_token, calls /connect/userinfo and sees which of THEIR products the user owns. Cross-brand privacy guaranteed.
2 scopes
Today
profile:read · own:read
1h
Token TTL
Refresh tokens = follow-up
10min
Authorization code TTL
One-shot redemption
0%
Cross-brand data leak
Partner only sees own producer_id
Google gives you "Sign in with Google" for identity. Fidaty gives you "Sign in with Fidaty" for physical product ownership. A loyalty app, a marketplace, an extended-warranty provider can now ask the user "which of our products do you own?" and get the answer via OAuth — with cryptographic proof backing it.
Partner redirects to /connect/authorize → consumer consents on a branded page → back to partner with code → partner exchanges at /connect/token → calls /connect/userinfo with bearer.
Consent screen with per-scope explanation.
One-shot code redemption; PKCE optional.
Returns sub + name + products (partner-scoped).
/wallet/connected-apps → disconnect any time.
Shoe brand loyalty app: user signs in with Fidaty, app sees their Fidaty-certified purchases, auto-enrolls them.
User wants an extended warranty; provider verifies ownership via Connect before issuing.
Vestiaire user signs in; Vestiaire sees which of their listings match verified-owned Fidaty certs.
Two brands pool benefits for users with ≥ 3 certs from either. Connect exposes the crossover safely.
Every service in the Fidaty platform is integrated with the rest: identity, compliance, analytics and consumer engagement flow seamlessly. No data silos, no duplicate work.
Book a demoClient credentials issued via super-admin.