> 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/card-based-ticketing-cbt/lifecycle-management/suspend-resume-from-icloud.md).

# Suspend/Resume from iCloud

Apple initiated suspension and resumption are actions initiated by the user using iCloud, in particular the Find My service. To learn more, visit the respective pages for Suspension and Resumption.

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 user activates Lost Mode using the Find My service. This results in all cards on the users Wallet becoming suspended.
2. **Suspension notification**: Apple will notify D1 Transit that card(s) should be placed into a suspended state.

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

Below are the high level steps of the resumption workflow:

1. **Resumption initiation** : Once the user regains possession of his device, he can initiate the resumption workflow.
2. **Resumption notification**: Apple will notify D1 Transit that card(s) should be resumed for active use.

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

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

The user initiates the suspension workflow by activating Lost Mode via the Find My service. For each card in the user's Wallet, Apple will attempt to suspend the pass on the device, though this is on a best-effort basis since the device could be offline. Additionally, Apple notifies D1 Transit platform of the suspension by sending a managePass request, with the action parameter set to suspend.

D1 Transit then notifies the Transit Issuer so it can put the card to the deny list, ensuring it cannot be used for transit. This step is crucial if the device is offline, as the card may not be suspended immediately.

**Error Scenarios**

**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>

The user initiates the resumption process by authenticating to his device, which is currently in Lost Mode. For each card in the user's Wallet, Apple will attempt to resume the pass on the device, though this is on a best-effort basis since the device could be offline. Apple notifies D1 Transit platform of the resumption by sending a managePass request, with the action parameter set to resume.

D1 Transit then notifies the Transit Issuer. Transit Issuer, if the card is on the deny list, can remove it to allow transit use.

**Error Scenarios**

**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="/spaces/SokLBgfEhZisVFcUdPiW/files/LB6KosH6r8JSsYPz4Rtp" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.payments.thalescloud.io/transit-digitization/implement-apple-transit/card-based-ticketing-cbt/lifecycle-management/suspend-resume-from-icloud.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.