POST
/
v2
/
issuing
/
card
/
{card_id}
/
replace

Headers

api-key
string
required

API key is required to call Solid APIs. You can view and manage your API keys in the Solid dashboard.

Path Parameters

card_id
string
required

Body

application/json
reason
enum<string>

card reissue reason

Available options:
lost,
stolen,
damaged,
expired
card_fulfilment
object

Response

200 - application/json
id
string

unique id of the card

client_id
string

unique id of the client that created the card

master_account_holder_id
string

unique id of the master account holder

master_account_id
string

unique id of the master account

sub_account_holder_id
string

unique id of the sub account holder

sub_account_id
string

unique id of the sub account under which the card was created

cardholder_id
string

unique id of the card holder

label
string

label of the card

product
enum<string>

type of card product configured based on the client's use case

Available options:
business_spend,
consumer_debit,
business_debit,
consumer_gpr,
consumer_gpnr,
consumer_payroll,
consumer_hsa,
consumer_fsa,
consumer_govt_benefits
theme
string

theme of the card configured as part of the client use case

type
enum<string>

type of card

Available options:
physical,
virtual
expiry_month
string

expiration month of the card

expiry_year
string

expiration year of the card

last4
string

last 4 digits of the card number

card_fulfilment
object
controls
object
external_reference_id
string

unique id to cross-reference records with external systems

attachments
object[]
metadata
object

Metadata takes free-form key-value pairs. You may send metadata when you create an object (POST) and when updating the object (PATCH). If you would like to remove metadata that is already on an object, you can unset it by passing in the key-value pair with an empty string, like this: {"key": ""}

status
enum<string>

status of the card

Available options:
open,
closed,
blocked,
locked
timestamps
object