Request a physical card
POST/v1/cards/:card_id/request-physical
Orders plastic for a card issued without it. The response is the same
card, not a new one: same id, same number, same balance, with
form_factor now physical and fulfillment.status pending. It keeps
working while the plastic is made.
There is no request body. The name printed on the card and the address it is posted to were both fixed when the card was issued, and this operation cannot revise either.
- A card that is not
activeis refused withcard_invalid_state. So is a card that is alreadyphysical, which is what a second request gets. - A closed card is refused with
card_closed. - A program that does not issue physical cards is refused with
unsupported_form_factor.
No event is emitted. Nothing reports when a card is posted, so the next
thing you learn is the cardholder telling you it arrived — call
POST /v1/cards/{card_id}/activate then to enable the card for use in
person.
You can also issue a physical card directly, without a virtual card
first, with POST /v1/cards and form_factor: physical.
Requires the cards:write scope.
Request
Responses
- 200
- 403
- 404
- 422
The card, now physical, with the plastic on its way.
Credentials are valid but not permitted. Do not retry.
The resource does not exist, or belongs to another organization. The two are deliberately indistinguishable.
Well-formed but fails a business rule.