Welcome to our new developer portal! Use the "Ask" button to chat with our AI Agent.
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Pull and change

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

Flow

Pull and change flow for physical card orders.

Sequence diagram

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.

Enum casing can vary by integration. Use the exact values defined in your API schema.

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)

Track the result

  • Consume notifications to get the accepted or rejected outcome.

  • For end-to-end production and shipment tracking, see Card order tracking.

Last updated

Was this helpful?