POST /v1/issuing/cards

Default value: "application/x-www-form-urlencoded"

The desired 4-digit expiration year for this card if specifying a custom expiration date.

The Cardholder object with which the card will be associated.

If replacement_for is specified, this should indicate why that card is being replaced.

Valid values:

• "lost"
• "expired"
• "stolen"
• "damaged"

The desired expiration month (1-12) for this card if specifying a custom expiration date.

The personalization design object belonging to this card.

Specifies which fields in the response should be expanded.

Set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format. Individual keys can be unset by posting an empty value to them. All keys can be unset by posting an empty value to metadata.

Whether authorizations can be approved on this card. May be blocked from activating cards depending on past-due Cardholder requirements. Defaults to inactive.

Valid values:

• "inactive"
• "active"

The desired PIN for this card.

The currency for the card.

Rules that control spending for this card. Refer to our documentation for more details.

Valid values:

• "monthly"
• "per_authorization"
• "weekly"
• "yearly"
• "all_time"
• "daily"

The card this is meant to be a replacement for (if any).

The address where the card will be shipped.

Valid values:

• "disabled"
• "normalization_only"
• "validation_and_normalization"

Valid values:

• "standard"
• "express"
• "priority"

Valid values:

• "individual"
• "bulk"

The type of card to issue. Possible values are physical or virtual.

Valid values:

• "physical"
• "virtual"

The new financial account ID the card will be associated with. This field allows a card to be reassigned to a different financial account.

The second line to print on the card. Max length: 24 characters.

Rules that control the lifecycle of this card, such as automatic cancellation. Refer to our documentation for more details.