Issue a card
POST/v1/cards
Issues a virtual or a physical card for an account.
A virtual card needs no more than the cardholder and the account. A
physical card also needs embossed_name, the name printed on it, and a
delivery_address. To have plastic made for a card you already hold, use
POST /v1/cards/{card_id}/request-physical instead.
The response only includes last_four. The full card number and CVV are
never returned here. Getting them is a separate, separately scoped and
audited operation.
A card is never usable straight away. It goes through the same statuses on every program:
- It starts as
pendingwhile the processor issues it. On a program that issues at once, the response already saysinactive. - It becomes
inactivewhen the processor has the card, and you getcard.issued. - It becomes
activewhen you callPOST /v1/cards/{card_id}/activate, and you getcard.activated. Until then every authorization is declined.
Request
Responses
- 201
- 400
- 422
Card accepted. pending while the processor issues it, or
inactive on a program that issues at once.
The request is malformed or contains an unrecognized parameter.
Well-formed but fails a business rule.