SLA management

Understand how D1 calculates production due dates for physical card orders.

SLA definition

The SLA

• starts when Thales receives your D1 API request

• ends when the physical card is shipped

• does not include carrier transit time

Business days and cut-off

SLA working days follow the personalization center’s local calendar. By default, working days are Monday to Friday.

The daily cut-off time is local to the personalization center. Requests received after cut-off start on the next calendar day.

In "D+N", D is the production request date after time zone conversion and cut-off handling.

Standard SLAs

Standard SLAs depend on your contract and configuration.

Common examples:

• CREATION or REPLACEMENT: D+1 (ready for carrier pickup at 17:00 local time).

• RENEWAL: D+10.

• URGENT: 4 hours if the urgent request is received before 12:00 local time.

D1 calculates the production due date for each physical card order based on the personalization center’s time zone, daily cut‑off, and the applicable SLA in working days.

Sequence

SLA calculation sequence (cut-off and working days).

Inputs for due date calculation

D1 API inputs:

• services.issuance: Issuance type.

• services.priority: Priority level agreed for card production.

• shipment.type: BULK or INDIVIDUAL. May impact the SLA

• Request timestamp (from the API call).

D1 configuration:

• Cut-off time: local time after which the base date moves to the next day.

• SLA: number of working days to produce the physical card.

Derived by D1:

• Personalization center and its time zone.

If your program maps services.priority to different SLAs, that mapping is configured in D1.

Calculation

The due date is calculated as follows:

1. Capture the production request timestamp in UTC.

2. Convert the timestamp to the personalization center’s local time zone to get the local request time.

3. Determine the production request date:

   • If the local request time is strictly after the daily cut‑off, set the production request date to the next calendar day.

   • Otherwise, use the local calendar day of the request.

4. Add the SLA (in working days) to the production request date to obtain the due date.

5. If configured, skip non‑working days (weekends and local holidays) in step 4.

Working days and holiday calendars are based on the personalization center’s local configuration. If your program uses multiple personalization centers, the applicable calendar may vary per order.

Decide and document whether “exactly at cut‑off” is considered before or after cut‑off. The examples below assume “strictly after” the cut‑off moves to the next day.

Examples

After cut‑off (same week)

• Inputs

  • Request timestamp (UTC): 2025‑03‑18 17:30

  • Personalization center time zone: UTC+1

  • Daily cut‑off: 18:00 (local)

  • SLA: 2 working days

• Computation

  • Local request time: 18:30 (after cut‑off) → production request date = 2025‑03‑19

  • Add 2 working days → due date = 2025‑03‑21

Before cut‑off (crossing a weekend)

• Inputs

  • Request timestamp (UTC): 2025‑03‑14 13:00

  • Personalization center time zone: UTC+1

  • Daily cut‑off: 18:00 (local)

  • SLA: 2 working days

• Computation

  • Local request time: 14:00 (before cut‑off) → production request date = 2025‑03‑14 (Friday)

  • Add 2 working days (Mon, Tue) → due date = 2025‑03‑18