> 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/central-issuance/implement-central-issuance/card-order/packaging.md).

# Packaging

Choose the physical packaging used for physical card shipment.

<figure><img src="broken://spaces/ol7FqojHqm5it3effNc4/files/NKySPGecYvOYF0rgez9M" alt="" width="563"><figcaption><p>Packaging options for physical cards.</p></figcaption></figure>

After personalization, D1 inserts the physical card into the configured packaging. Packaging can be an envelope, sleeve, or box (depending on your setup).

### Select a packaging

D1 selects the packaging from your request fields. It applies the rules defined during D1 onboarding.

### Inputs used for personalization

Required D1 API inputs:

* `services.packaging`: Packaging identifier configured during D1 onboarding.

Optional D1 API inputs:

* `packagingConfig.inserts`: Insert identifiers to add to the package (for example, flyers or legal notices).

Each insert identifier must be configured and allowed for your program.

#### Example (request excerpt)

```json
{
  "services": {
    "packaging": "standard-envelope"
  },
  "packagingConfig": {
    "inserts": ["welcome-letter", "terms-and-conditions-v3"]
  }
}
```

### Configuration in D1

During D1 onboarding, Thales configures:

* Supported packaging identifiers.
* Rules to select packaging (when multiple options exist).
* Allowed insert identifiers and their handling rules.


---

# 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/central-issuance/implement-central-issuance/card-order/packaging.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.