D1 API summary
Mandatory APIs
API
Inbound/Outbound
Description
Conditional APIs
API
Inbound/Outbound
Description
Optional APIs
API
Inbound/Outbound
Description
Last updated
Was this helpful?
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.
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.
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.
Last updated
Was this helpful?
Was this helpful?