Getting started with the Self Service Portal

The MATTR Self Service Portal (SSP) is built on top of MATTR VII APIs and provides an easy-to-use interface to effectively manage and oversee tenant management and configuration.

Getting started

When you log into the portal the Tenant management screen is displayed by default:

• Use the drop-down list in the top-left corner to switch between tenants.
• Use the navigation panel on the left-hand side to access different functionalities:

• Platform management: Manage your MATTR VII tenants:

  • Tenant management: Create, view and delete tenants. This capability is based on our Management APIs.
  • Users, clients & roles: Manage users and clients for your tenants. These capabilities are based on the Clients and Members endpoints in the Management API.
  • Custom domain: Configure a Custom domain for the selected tenant. This capability is based on configuring a Custom domain using an API request and verifying the Custom domain using an API request.
  • Monitoring: Query and inspect Analytic events from your tenant. This capability is based on querying Analytic events using an API request.
  • Webhooks: Create a Webhook to subscribe to events. Available options are similar to those described for creating a Webhook using an API request.
  • DIDs: View DIDs available on your tenant. Note that the Self Service Portal does not allow you to create DIDs.
  • Certificates: Create new IACAs and view any existing IACAs available on your tenant.

• Ecosystem operations:

  • Configuration & publish: Manage your Ecosystem:
    • Create a participant.
    • Configure credential types.
    • Publish the Ecosystem’s policy.

• Credential issuance: Manage OID4VCI workflow components and configuration:

  • Authentication provider: Configure an Authentication provider to be used in OID4VCI workflows. Available options are similar to those described for configuring an Authentication provider using an API request.
  • Interaction hook: Configure an Interaction hook to redirect a user to a custom component during the credential issuance journey. Available options are similar to those described for configuring an Interaction hook using an API request.
  • Claims sources: Configure a Claims source to fetch claims directly from an identity provider, interaction hook or external claims source and use them when issuing credentials. Available options are similar to those described for configuring a Claims source using an API request.
  • Web credential: Create a JSON credentials configuration that can be used to issue JSON credentials using the OpenID4VCI protocol. Available options are similar to those described for creating a JSON credentials configuration using an API request.
  • Mobile Credential: Create an mDocs credentials configuration that can be used to issue mDocs using the OpenID4VCI protocol. Available options are similar to those described for creating an mDocs credentials configuration using an API request.
  • Compact credential: Create a CWT or Semantic CWT credentials Configuration that can be used to issue CWT or Semantic CWT credentials using the OpenID4VCI protocol. Available options are similar to those described for creating a CWT or Semantic CWT credentials configuration using an API request for either CWT or Semantic CWT credentials.
  • Credential offer: Create a Credential offer by specifying credential configurations and request parameters. This capability is based on creating a Credential offer using an API request, with some additional capabilities to share the offer with the intended holder.

• Credential verification: Configure mDocs online verification workflows:

  • Trusted issuers: Configure and manage mDocs issuers that can be trusted when verifying mDocs presented online. Available options are similar to those described for creating a trusted issuer using an API request.
  • Supported wallets: Configure and manage digital wallet applications that can present mDocs online for verification, and how to interact with these wallets. Available options are similar to those described for creating a wallet provider using an API request.
  • Applications: Configure and manage applications that can create mDocs online verification sessions, and how to interact with these applications. Available options are similar to those described for creating a verifier application using an API request.

• Use the Contact us button at the bottom-left corner to fill a contact form.

• Use the Slack community button at the bottom-left corner to sign up to our Slack community channel.