SPID

Overview

Italy’s national digital identity framework provided by various certified issuers. SPID is widely adopted and used by nearly 90% of the online population for authentication across public and private online services.

  • ID: italy-spid
  • Type: eID (app)
  • Verification Type: Presentation
  • Regions: Europe
  • Countries: IT
  • Adoption: 41,000,000
  • URL: https://www.spid.gov.it/en/

Integration with Trinsic


User Flow

After clicking the SPID button, the user sees a list of SPID identity providers. They select their identity provider and then inputs their user name and password. Depending on the requested level of assurance, they user might also be prompted to enter a one time passcode, or a code confirmation in their identity provider's mobile app. Once authenticated, the user consents to sharing their data and the flow is complete. To see a demo, watch this video.


How to Test

  • While using a test mode App, select the spid provider.
  • Enter one of the following details:
    • Level 1: Nome utente cesare Password password123.
      • By default, this account will fail verification, as it does not meet the specified SPID Level of 2.
    • Level 2: Nome utente ada Password password123.
    • Level 3: Nome utente marcopolo Password password123.
  • Click Conferma

Direct API Requirements

📘

Direct is not a requirement.

You can integrate with this provider using the Widget or Hosted UI instead, with no additional integration requirements on your end.

What your integration must support in order to use this provider with the Direct Provider Sessions API.

  • Supports Direct Provider Sessions: ✅
  • Launch Method: LaunchBrowser — Send the user's browser (via redirect, popup, or new tab) to the given URL.
  • Collection Method: CaptureRedirect — The user is redirected back to your app with a resultsAccessKey upon completion.
  • Requires Input: This provider requires input before verification can proceed.
  • Trinsic-Hosted UI: A Trinsic-Hosted Fallback UI exists for this provider, which may be invoked to cover gaps in your integration's capabilities.

Outputs

ℹ️

Normalized Attributes

These attributes form part of our normalized model, a standardized set used across providers. Trinsic normalizes this for you and lets you know when a property is available for each provider.

FieldAvailabilityNotes
person.givenNameAlways-
person.familyNameAlways-
person.dateOfBirthAlways-
person.sexSometimesIf available
person.phoneNumberSometimesIf available
person.address.line1SometimesIf address is available
person.address.citySometimesIf address is available
person.address.subdivisionSometimesIf address is available
person.address.postalCodeSometimesIf address is available
person.address.countrySometimesIf address is available
document.typeAlways-
document.numberAlways-
document.issueDateAlways-
document.expirationDateSometimesIf available
document.issuingAuthorityAlways-

Frequently Asked Questions

Do we receive the image of the document used to onboard to SPID?

No, but you can receive the details of the identity document that was used to onboard to SPID in the IDcard attribute.

Can we get the place of issue and issuer for the document used to onboard to SPID?

SPID provides an attribute called issuingAuthority which is a combination the institution that issued the document, and the location where it was issued. For example, motorizzazioneCivileComo, prefetturaMilano or MinisteroInterno.