> 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/overview.md).
# Overview
The Perso Design Services platform is the default solution at Thales for dynamic payment card artwork management where artwork is applied to the payment card during card personalization.
Our products AllAboutMe, SketchMyCard & BrandMyCard enable Issuers and their Cardholders to create innovative and dynamic card designs, for both consumer and business use cases:
* **AllAboutMe (B2C)**: A platform that enables photo-based card designs and printing onto base white plastic during personalization using full-color edge-to-edge print technology.
* **SketchMyCard (B2C)**: A platform that enables sketch-based card designs and printing onto existing offset cards during personalization using single-color flat print technology.
* **BrandMyCard (B2B)**: Our offer that enables Issuers and their partners to collaboratively create, design and issue small series of co-branded cards in a matter of days.
## How it Works
Images are stored by the Perso Design Services platform on behalf of the Issuer as layered card image files, enabling later access during initial card personalization and card re-issue, or later edits to be made, for example as a result of a card rebranding or re-draft.
{% hint style="info" %}
Perso Design Services products are compatible with both **Thales** and **third-party personalization bureaus**.
{% endhint %}
**Card images can be designed and captured in one of three ways:**
### 1) Our Designer Tool
Perso Design Services offers an industry-leading fully-responsive designer tool that can be integrated directly into the issuer's web or mobile app, enable cardholders to design their card seamlessly within the issuer's brand experience.
The Designer Tool is easy to integrate via a JavaScript plugin into the card issuance workflow, both for new-to-bank end users and existing end users that want to create their own card design.
Product features, from image upload, to card templates and additional options such as doodles and filters can be configured at the product level from our Administration Dashboard.
### 2) Our APIs
For Issuers that would prefer to develop their own solution for capturing the Cardholders' card design, we offer our Image Upload API that enables compliant AllAboutMe or SketchMyCard images to be uploaded into the Perso Design Services platform without requiring our Designer Tool to be integrated.
### 3) Our BrandMyCard Platform
The BrandMyCard platform requires no technical integration. The Issuer will be provided with support to configure the required user logins and card body plastics in the platform. Training is provided on how to easily design B2B cards via the platform's built-in Designer Tool in collaboration with co-brand partners.
### Other Prerequisites
* The Issuer CMS must support an Image ID per card.
* The card products in the personalization bureau, whether Thales or third-party, must specify the correct card body plastic to support print‑on‑demand services.
* Note: Applying images to cards is an additional step in the Thales personalization process.
---
# 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/perso-design-services/get-started/overview.md?ask=&goal=
```
`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.