Tracking hub
Use tracking hub to receive production, shipment, or return updates for a physical card produced outside Thales D1.
Flow

Issuer back-end request to track the card
D1 Connects to carriers to retrieve shipment information
Carriers sends regular shipment statuses
D1 formats and sends the statuses to Issuer back-end
Sequence diagram

How it works
Use
trackingType = PRODUCTIONto receive a production completion update.Thales D1 sends one notification with
status = SUCCESSFUL.The notification includes
details.status = CARD_SHIPPED.
Use
trackingType = SHIPMENTto receive shipment progress updates.Thales D1 first sends a notification with
status = PENDING.Thales D1 then sends one or more notifications with
status = SUCCESSFULas shipment data changes.When available, the notification includes
details.shipment. See Track shipment.
Use
trackingType = RETURNto receive a returned-card update.Thales D1 sends one notification with
status = SUCCESSFUL.The notification includes
details.status = CARD_RETURNED.
Required APIs
Issuer -> Thales D1
Request production, shipment, or return tracking for a physical card.
API Inputs
Required D1 API inputs:
issuerId: Unique identifier of the issuer.cardId: Unique identifier of the card.trackingType: Type of tracking to perform. Supported values arePRODUCTION,SHIPMENT, andRETURN.
Examples
Tracking type = PRODUCTION
Tracking type = SHIPMENT
Tracking type = RETURN
Track the result
Consume notifications on the STANDALONE_TRACKING operation.
Key fields:
operation: AlwaysSTANDALONE_TRACKING.status: Operation status. Values arePENDING,SUCCESSFUL, orFAILED.cardId: Card identifier used in the request.details.trackingType:PRODUCTION,SHIPMENT, orRETURN.details.productionSite: Production site identifier, when available.details.status: Tracking result, such asCARD_SHIPPEDorCARD_RETURNED.details.shipment: Shipment tracking details forSHIPMENTupdates. See Track shipment.
Top-level status is the operation status.
details.status is the business tracking status.
Notifications can arrive more than once, and they can arrive out of order. Use operationId to de-duplicate events.
Notification sequence by tracking type:
PRODUCTION
One notification with status = SUCCESSFUL and details.status = CARD_SHIPPED.
RETURN
One notification with status = SUCCESSFUL and details.status = CARD_RETURNED.
SHIPMENT
One notification with status = PENDING, then one or more notifications with status = SUCCESSFUL as shipment updates become available.
Notification examples
Tracking type = PRODUCTION
Tracking type = SHIPMENT — first notification
Tracking type = SHIPMENT — subsequent notification (with shipment details)
Tracking type = RETURN
Last updated
Was this helpful?