> 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-google-transit/account-based-ticketing-abt/lifecycle-management/park-from-device.md).

# Park from Device

User initiates parking of his transit card from his device.

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

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

Below are the high level steps of the suspension workflow:

1. **Card Removal**: The user selects the card to be deleted.
2. **Unlink result**: Since it's triggered from device, it is guaranteed that the digital card instance is removed from the device.

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

The user initiates the park workflow from his wallet. Google will attempt to delete the token on the device. Additionally, Google notifies D1 Transit platform of the deletion by sending a deleteToken request.

D1 Transit then notifies the Transit Issuer so it can mark the card as parked and not to be used for transit.

<figure><img src="/files/NWWuOzIgvvl6mwgwytIA" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The user may restore his card on same or different device, as long as he's connected with same Google account.
{% endhint %}


---

# 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-google-transit/account-based-ticketing-abt/lifecycle-management/park-from-device.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.