> 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-transit-issuer.md).

# Park from Transit Issuer

Issuer-initiated park is an action triggered by the Transit Issuer or, in some cases, by the user via the transit operator's 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>

Below are the high level steps of the suspension/resumption workflow:

1. **State change initiation**: The Transit Issuer or, in some cases the user (via the transit operator's app) notifies D1 Transit that a card park should be performed. D1 Transit platform then informs Google by sending handleTspEvent.
2. **State change execution**: Once event is delivered to Google, D1 Transit updates the digital card state change. Google, will later on, sends a getTokenStatus in order to fetch and apply the state change from D1 Transit.

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

{% hint style="info" %}
Transit Issuer should primarily add 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 parked immediately.
{% endhint %}

Transit Issuer sends a manageDigitalCard to D1 Transit platform, which itself, sends handleTspEvent to Google.

Upon receiving this request, Google will fetch the state change to apply and attempt to apply it to the digital card on the device, though this is on a best-effort basis since the device could be offline.

D1 Transit notifies the Transit Issuer that the state change order was submitted to Google.

**Error Scenarios**

**Device is offline**

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

<figure><img src="/files/h71G3MG6kvT9pvgQYw7B" 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-google-transit/account-based-ticketing-abt/lifecycle-management/park-from-transit-issuer.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.