> 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/get-started/central-issuance-overview.md).

# Central issuance overview

Central issuance lets your issuer backend request physical card production and shipment from a Thales personalization center.

Use Central issuance when you want a centralized, factory-style issuance flow. D1 manages dispatch to the correct site based on your program configuration.

### What you can do

* [Order physical cards](/central-issuance/implement-central-issuance/card-order.md): Submit a physical card production request with personalization and shipment options.
* [Card order tracking](/central-issuance/implement-central-issuance/card-order-tracking.md): Track production and shipment status from request to dispatch.
* [Pull & Change](/central-issuance/implement-central-issuance/pull-and-change.md): Update an existing order (for example, accelerate, redirect, or cancel) when supported by your configuration and current status.

### Prerequisites

You typically need:

* D1 onboarding completed for physical card issuance
* At least one `cardProductId` configured for your program/BIN
* Shipment, packaging, and card carrier options configured (if applicable)


---

# 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/central-issuance/get-started/central-issuance-overview.md?ask=<question>
```

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.