> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/transit-digitization/implement-apple-transit/account-based-ticketing-abt/lifecycle-management/suspend-resume-from-transit-issuer.md).

# Suspend/Resume from Transit Issuer

Issuer-initiated suspension and resumption are actions triggered by the Transit Issuer or, in some cases, by the user via the transit operator's iOS app.

This section provides an overview of the workflow, including detailed steps, sequence diagrams, and potential error scenarios.

### Workflow <a href="#workflow" id="workflow"></a>

#### Suspension <a href="#suspension" id="suspension"></a>

Below are the high level steps of the suspension workflow:

1. **Suspension initiation**: The Transit Issuer or, in some cases the user (via the transit operator's iOS app) notifies D1 Transit that a card should be suspended. D1 Transit platform then informs Apple by sending a managePass request with the suspend action.
2. **Suspension notification**: Once D1 Transit has successfully notified Apple of the suspension to perform, it sends a notification to Transit Issuer.

#### Resumption <a href="#resumption" id="resumption"></a>

Below are the high level steps of the resumption workflow:

1. **Resumption initiation**: The Transit Issuer or, in some cases the user (via the transit operator's iOS app) notifies D1 Transit that a card should be resumed. D1 Transit platform then informs Apple by sending a managePass request with the resume action.
2. **Resumption notification**: Once D1 Transit has successfully notified Apple of the resumption to perform, it sends a notification to Transit Issuer.

### Sequence Diagram <a href="#sequence-diagram" id="sequence-diagram"></a>

#### Suspension <a href="#suspension-1" id="suspension-1"></a>

Suspension is initiated by the Transit Issuer, or in some cases, by the user via the transit operator's iOS app.

Transit Issuer adds the card to the deny list. Adding the card to the deny list is crucial if the device is offline, as the card may not be suspended immediately. Then it sends a suspend request to D1 Transit platform, which itself, sends a managePass request to Apple with the action parameter set to suspend.

D1 Transit sets the digital card state to suspended and notifies Transit Issuer the outcome of the lifecycle operation.

Upon receiving the request to suspend the card, Apple will attempt to suspend the pass on the device, though this is on a best-effort basis since the device could be offline.

**Error Scenarios**

**Suspension failure**

If D1 Transit receives a failure when instructing Apple to suspend the card, D1 Transit sends a notification to Transit Issuer indicating that the request has failed. Transit Issuer can retry suspending the card.

**Device is offline**

If the device is offline, the request to suspend the card is queued and will be sent to the device as soon as it reconnects.

#### Resumption <a href="#resumption-1" id="resumption-1"></a>

Resumption is initiated by the Transit Issuer, or in some cases, by the user via the transit operator's iOS app.

Transit Issuer sends a resumption request to D1 Transit and removes the card from the deny list if it's present. D1 Transit then sends a managePass request to Apple with the action parameter set to resume.

D1 Transit sets the digital card state to active and notifies Transit Issuer the outcome of the lifecycle operation.

Upon receiving the request to resume the card, Apple will attempt to resume the pass on the device, though this is on a best-effort basis since the device could be offline.

**Error Scenarios**

**Resumption failure**

If D1 Transit receives a failure when instructing Apple to resume the card, D1 Transit sends a notification to Transit Issuer indicating that the request has failed. Transit Issuer can retry resuming the card.

**Device is offline**

If the device is offline, the request to resume the card is queued and will be sent to the device as soon as it reconnects.

<figure><img src="broken://spaces/SokLBgfEhZisVFcUdPiW/files/9jS52p3DnF54sRhD9RtH" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.payments.thalescloud.io/transit-digitization/implement-apple-transit/account-based-ticketing-abt/lifecycle-management/suspend-resume-from-transit-issuer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.