> 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/get-started/concepts/card-account-and-digital-card-models.md).

# Card Account and Digital Card Models

The following diagram represents the data model within D1 Transit solution.

<figure><img src="https://1928701359-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZoFRCpZeaDWwcHYhJY7B%2Fuploads%2FC2n0eRsUQH67h0rGlSeP%2FKey%20Concepts.svg?alt=media&amp;token=1681c49c-0253-4d0e-987d-ddf4c9f130e3" alt=""><figcaption></figcaption></figure>

#### Transit Issuer <a href="#transit-issuer" id="transit-issuer"></a>

The Transit Issuer represents the customer D1 Transit is connected to.

It can be either the PTO directly or a Transit Hub (or Transit aggregator)

#### &#x20;<a href="#fare-products" id="fare-products"></a>

#### Fare Products <a href="#fare-products" id="fare-products"></a>

The fare products represent the different types of products commuters can purchase and use.

It can be stored value product (e.g. purse), count based products (e.g. carnet of tickets) or time based products (e.g. monthly pass)

See [Fare Products](/transit-digitization/get-started/concepts/fare-products.md) section for more details.

#### Card Account <a href="#card-account" id="card-account"></a>

Card Account is the elementary unit binding end users to fare products.

A card account can have several fare products and belongs to an end user. In case of ABT, the card account is usually bound to a funding source.

{% hint style="info" %}
Within D1 Transit solution, a Card Account has a unique identifier (generated by Thales) with the following format:\
\
**F + WalletProviderId + ShortIssuerId + UUID**\
where:

* '+' denotes the concatenation
* WalletProviderId is '**APL**' for Apple, '**GGL**' for Google or '**SSG**' for Samsung
* ShortIssuerId is a unique ID assigned to Transit Issuer during onboarding time (**Note: This is not the issuerId**)
* UUID is without hyphens ('-')

**Example:**`FAPLSW8D8AC610566D4EF09C22186B2A5ED793`
{% endhint %}

#### User <a href="#user" id="user"></a>

The Users are the persons (physically speaking) using the service. Depending on the digital wallet being used, User entity can either be represented by the wallet account (i.e. iCloud account identifier for Apple) or an instance of the wallet account on a particular device (e.g. walletId for Google)

In any case, these identifiers are anonymized.

#### Wallet Provider <a href="#wallet-provider" id="wallet-provider"></a>

Wallet Provider is the entity providing the Digital Wallet to end users.

At this time, D1 Transit supports Apple Wallet. Google and Samsung to come...

#### Wallet App <a href="#wallet-app" id="wallet-app"></a>

This is the Digital Wallet. This represents (in a high level manner) the container for the fare products stored into the devices (for CBT) or the transit account identifier linked to the fare products in the Transit Issuer Back Office (for ABT)

#### Digital Card <a href="#digital-card" id="digital-card"></a>

The Digital Card is an instance of the card account within the Wallet App.

{% hint style="info" %}
Within D1 Transit solution, a Digital Card has a unique identifier (generated by Thales) with the following format:\
\
**D + WalletProviderId + ShortIssuerId + UUID**\
where:

* '+' denotes the concatenation
* WalletProviderId is '**APL**' for Apple, '**GGL**' for Google or '**SSG**' for Samsung
* ShortIssuerId is a unique ID assigned to Transit Issuer during onboarding time (**Note: This is not the issuerId**)
* UUID is without hyphens ('-')

**Example:**`DGGLSW8D8AC610566D4EF09C22186B2A5ED756`
{% 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 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/get-started/concepts/card-account-and-digital-card-models.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.