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.

Select card order services

Select D1 API fields that control how a physical card is produced and shipped.

Use these D1 API fields to control how a physical card is produced and shipped.

Field names and nesting can vary by endpoint. This page uses the naming from the Physical Issuance API.

Required parameters

  • cardProductId (string): Card product identifier.

  • services.issuance (string): Issuance type.

    • CREATION: Create a new card for a new end user.

    • RENEWAL: Renew a card before expiry.

    • REPLACEMENT: Replace a card (for example, lost or stolen).

Optional parameters

  • distributionChannel (string): Where the card is personalized. Default: THALES.

    • THALES: Personalize in a Thales personalization center.

    • INSTANT: Personalize instantly in a branch.

    • CENTRAL: Personalize in issuer premises or a partner center.

  • services.priority (string): Priority level used to refine services.issuance.

  • services.delivery (string): Shipment method. Default: NO_SHIPMENT. See Shipment.

  • services.cardCarrier (string): Card carrier identifier. Default: NO_CARRIER. See Card carrier.

  • services.packaging (string): Packaging identifier. Default: NO_PACK. See Packaging.

  • services.pinMailer (boolean): When true, produce and ship a PIN mailer. Default: false. PIN mailers are typically sent about 2 business days after card shipment.

  • services.alphaCard (boolean): When true, produce a sample card in the Production Environment. Default: false.

Example

Last updated

Was this helpful?