Get started

  • Issuers begin the process by completing and submitting an onboarding sheet to Google.

  • Google will contact the issuer to discuss the next steps and exchange mTLS certificates.

  • An Issuer ID will be provided, which is necessary for requests to Google-hosted endpoints.

  • Issuers are responsible for conducting end-to-end testing before launching.

Choose an onboarding flow

Before beginning, choose which onboarding flow to support from the following options:

  • Wallet-initiated: The provisioning flow is initiated by a user directly from within the Google Wallet app. This can be one of two proofing types:
    • Wallet proofed: The user's identity information is collected by Google and sent to the issuer for verification.
    • Issuer proofed: The user is redirected to the issuer and their identity is verified by the issuer.
  • Issuer-initiated: The provisioning flow starts directly from issuer's own app or website.

Request onboarding

To get started, email your use case to us. Include answers to the following questions in your request:

  • Type of credential: What is the credential type (such as a driving license, age credential)?
  • Attributes: What attributes are contained in the credential (such as name, last name, or date of birth)?
  • Doctype: What is the doctype (such as eu.europa.ec.av.1)?
  • Credential format: What is the credential format (such as mdoc or SD-JWT)?
  • Expected use case: What are the expected use cases or relying parties (RPs) interested in the credential?
  • Expected volume: What is the expected volume of credentials issued?
  • Country: Which country or countries will the credential be issued in?

Google will review your request and, if suitable, discuss next steps. Upon mutual confirmation, technical integration begins. This includes exchanging mTLS certificates and submitting an onboarding sheet.

Once certificates have been exchanged and Google has onboarded the issuer, your Google representative will provide you with the following.

Information Description
Issuer ID (or Vendor ID) This will be used in requests to Google-hosted endpoints.

During testing and before going live, issuers are responsible for end-to-end testing of the flows.