> 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/home/card-creation-and-management/implement-card-creation-and-management/manage-card/physical-card-and-personalization/pull-and-change.md).

# Pull and change

Use pull and change to request updates to a physical card order that D1 has received but not shipped.

### Flow

<figure><img src="/spaces/ol7FqojHqm5it3effNc4/files/tOKJrbng18rv6i1A8icL" alt=""><figcaption><p>Pull and change flow for physical card orders.</p></figcaption></figure>

### Sequence diagram

<figure><img src="/spaces/ol7FqojHqm5it3effNc4/files/weM2kjS1N5c5uS3my1B8" alt=""><figcaption></figcaption></figure>

### Change types

Common change types:

* `CANCEL`: Cancel the card order and destroy the card.
* `ACCELERATE`: Produce the card as soon as possible.
* `REDIRECT`: Change the shipment delivery address.
* `ACCELERATE_AND_REDIRECT`: Expedite production and change the shipment delivery address.

{% hint style="info" %}
Enum casing can vary by integration. Use the exact values defined in your API schema.
{% endhint %}

### How it works

1. The issuer backend submits a pull and change request.
2. D1 forwards the request to the personalization center producing the card.
3. The personalization center accepts or rejects the request based on the production stage.
4. D1 returns the outcome asynchronously via notifications.

### Request inputs

#### Required

* `type`: Type of change to apply to the card order.

#### Conditional

Provide `newDeliveryAddress` when `type` is `redirect` or `expediteAndRedirect`.

`newDeliveryAddress` fields:

* `title`: Name prefix (for example, `Mr`).
* `firstName`: First name.
* `lastName`: Last name.
* `companyName`: Company name.
* `line1`: Address line 1.
* `line2`: Address line 2.
* `line3`: Address line 3.
* `city`: City.
* `state`: State or region.
* `zipCode`: Postal code.
* `countryCode`: Country code (ISO 3166-1 alpha-2, for example `US`).
* `mobilePhoneNumber`: International phone number used for shipment contact.

#### Example (redirect)

```json
{
  "type": "REDIRECT",
  "newDeliveryAddress": {
    "title": "Ms",
    "firstName": "Alex",
    "lastName": "Chen",
    "companyName": "Example Co",
    "line1": "10 Main St",
    "line2": "Apt 3B",
    "city": "New York",
    "state": "NY",
    "zipCode": "10001",
    "countryCode": "US",
    "mobilePhoneNumber": "+12125550123"
  }
}
```

### Track the result

* Consume notifications to get the accepted or rejected outcome.
* For end-to-end production and shipment tracking, see [Card order tracking](https://app.gitbook.com/o/fwy1mtbRONGA2YDKDBr0/s/ol7FqojHqm5it3effNc4/physical-issuance/card-order-tracking).


---

# 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/home/card-creation-and-management/implement-card-creation-and-management/manage-card/physical-card-and-personalization/pull-and-change.md?ask=<question>&goal=<endgoal>
```

`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.