POST /v1/issuing/cards

Creates an Issuing Card object.

Servers

https://api.stripe.com/

Request headers

Name	Type	Required	Description
`Content-Type`	String	Yes	The media type of the request body. Default value: "application/x-www-form-urlencoded"

Request body fields

Name	Type	Required	Description
`cardholder`	String	No	The Cardholder object with which the card will be associated.
`replacement_reason`	String	No	If `replacement_for` is specified, this should indicate why that card is being replaced. Possible values: `"lost"` `"expired"` `"stolen"` `"damaged"`
`personalization_design`	String	No	The personalization design object belonging to this card.
`expand[]`	Array	No	Specifies which fields in the response should be expanded.
`metadata`	Object	No	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`.
`status`	String	No	Whether authorizations can be approved on this card. May be blocked from activating cards depending on past-due Cardholder requirements. Defaults to `inactive`. Possible values: `"inactive"` `"active"`
`pin`	Object	No	The desired PIN for this card.
`pin.encrypted_number`	String	No
`currency`	String	Yes	The currency for the card.
`spending_controls`	Object	No	Rules that control spending for this card. Refer to our documentation for more details.
`spending_controls.blocked_merchant_countries[]`	Array	No
`spending_controls.spending_limits[]`	Array	No
`spending_controls.spending_limits[].interval`	String	Yes	Possible values: `"monthly"` `"per_authorization"` `"weekly"` `"yearly"` `"all_time"` `"daily"`
`spending_controls.spending_limits[].categories[]`	Array	No
`spending_controls.spending_limits[].amount`	Integer	Yes
`spending_controls.allowed_merchant_countries[]`	Array	No
`spending_controls.allowed_categories[]`	Array	No
`spending_controls.blocked_categories[]`	Array	No
`replacement_for`	String	No	The card this is meant to be a replacement for (if any).
`shipping`	Object	No	The address where the card will be shipped.
`shipping.name`	String	Yes
`shipping.address_validation`	Object	No
`shipping.address_validation.mode`	String	Yes	Possible values: `"disabled"` `"normalization_only"` `"validation_and_normalization"`
`shipping.require_signature`	Boolean	No
`shipping.service`	String	No	Possible values: `"standard"` `"express"` `"priority"`
`shipping.type`	String	No	Possible values: `"individual"` `"bulk"`
`shipping.customs`	Object	No
`shipping.customs.eori_number`	String	No
`shipping.address`	Object	Yes
`shipping.address.line2`	String	No
`shipping.address.line1`	String	Yes
`shipping.address.postal_code`	String	Yes
`shipping.address.country`	String	Yes
`shipping.address.state`	String	No
`shipping.address.city`	String	Yes
`shipping.phone_number`	String	No
`type`	String	Yes	The type of card to issue. Possible values are `physical` or `virtual`. Possible values: `"physical"` `"virtual"`
`financial_account`	String	No	The new financial account ID the card will be associated with. This field allows a card to be reassigned to a different financial account.
`second_line`		No	The second line to print on the card. Max length: 24 characters.

How to start integrating

Add HTTP Task to your workflow definition.
Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
Click Test request to test run your request to the API and see the API's response.