> 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/perso-design-services/get-started/pds-concepts.md).
# PDS Concepts
This page defines the core entities and identifiers used by Perso Design Services.
## End User
An **end user** is a person who owns one or more cards. The end user is the issuer’s customer.
## CardHolderID
In PDS, an end user is identified by a `CardHolderID` that:
* Is used across card products set up within the PDS Admin Dashboard.
* Is defined by the issuer and unique within PDS.
* Does not contain or link to the end user's identity or personal information.
PDS does not create end users. The issuer passes the `CardHolderID` as a parameter when establishing a design session with AllAboutMe or SketchMyCard. Passing the `CardHolderID` as a parameter enables more effective usage reporting as Thales can determine unique user sessions and designs without requiring any personally identifiable information about the end user.
## Card Design
A **card design** is an image that is either created using the PDS Designer Tool, or sent to PDS via our Image Upload API. Card designs are stored as layered files, comprised of the print template alongside the end user's uploaded image, gallery image or sketch.
## CardImageID
Each unique card design is associated to a specific `CardImageID` that represents that image and is used by Thales, the perso bureau and the Issuer to refer to a specific card design. The same `CardImageID` is used again where a card with the same card design is reissued.
## Administration Dashboard
The Administration Dashboard is the web-based portal for Perso Design Services products, accessible by both Thales and the issuer, where products available for card customization are set-up and the program is managed. Product features, such as card templates and available customization options are configured for each card product via the Administration Dashboard. Additional features such as reporting are available for the issuer to view.
## Designer Tool
The Perso Design Services Designer Tool is integrated into the issuer's web or mobile app, and enables the end users' card design to be captured seamlessly via a JavaScript plugin. The Designer Tool allows the end user to upload and position the image where they would like it, or to select from a gallery of images configured by the issuer.
Where the issuer is using the Perso Design Services image upload API, this replaces the Designer Tool.
## Image Checking
Thales offers an Image Checking service for Perso Design Services images, to check all uploaded end-user images for compliance against both issuer and scheme image requirements within a defined SLA. Our expert team of Image Checkers are trained on the latest popular culture and trends to enable them to check images with comprehensive knowledge.
## Core Steps:
### Capture
Capture and preview the cardholder’s design within the Issuer app, with gallery selection or image upload and manipulation using the Designer Tool.
Verify the card design for quality and against technical requirements for print.
### Validate
Validate the image against scheme rules and Issuer requirements for card imagery using Image Checking.
Push image status to Issuer/Cardholder for communication about approval or rejection and to order card.
### Prepare
Prepare the print-ready card image according to perso bureau requirements and technology.
Prepare multiple digital card simulations for use by the Issuer in mobile banking, digital wallets and communications.
### Deliver
Deliver the print image to perso bureau in real time, whether Thales (via **D1 API**) or third party, and deliver the digital simulation to the Issuer.
Long-term storage of layered card image file ensuring availability for regular reissuance.
### Support
Administer all card personalization program features and settings through the Perso Design Services Administration Dashboard.
Support and training provided by Thales for build and day-to-day running of the service.
---
# 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:
```
GET https://docs.payments.thalescloud.io/perso-design-services/get-started/pds-concepts.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.