Welcome to our new developer portal! Use the "Ask" button to chat with our AI Agent.
For the complete documentation index, see llms.txt. This page is also available as Markdown.

D1 API summary

This section provides a summary of the APIs used in the Push Provisioning service.

The APIs are grouped into:

  • Mandatory: must be implemented by the issuer for a proper integration in D1 and compliance with the schemes.

  • Conditional: to be implemented according to the integration model chosen by the issuer.

  • Optional: to be implemented according to the issuer business needs.

Mandatory APIs

API
Inbound/Outbound
Description

Issuer -> Thales D1

Get an OAuth 2.0 access token to call the D1 backend.

Issuer <- Thales D1

Get an OAuth 2.0 access token to call the issuer backend.

Issuer -> Thales D1

To register or create a card.

Issuer -> Thales D1

To register a consumer.

Issuer -> Thales D1

Renew the card on D1 and request the TSP to link the existing digital cards. Replace the card on D1 and request the TSP to link the existing digital cards

Issuer -> Thales D1

Allow to terminate, definitely, the related asset. The request is cascaded to the children resources.

Conditional APIs

API
Inbound/Outbound
Description

Issuer -> Thales D1

To control the state of the card in D1. Conditional to the issuer needs.

Issuer -> Thales D1

In case the consumer details are registered, the issuer should update it accordingly. Otherwise, D1 calls Get Consumer Information.

Issuer <- Thales D1

Allows D1 to get the latest consumer details. Not required if the issuer updates regularly the consumer details.

Optional APIs

API
Inbound/Outbound
Description

Issuer -> Thales D1

To retrieve the consumer details stored.

Issuer -> Thales D1

To retrieve all the cards of a given consumer.

Last updated

Was this helpful?