Create a physical card
You create a physical card with the same Provision account API that you use for Virtual Cards. Set the following parameters:
typeset tophysical_cardcard_program_id: the Card Program the card is issued under. It must be a Card Program for physical cards.printed_name: the name to emboss on the card (max. 26 characters). Optional: leave it out to issue a no-name card.shipping_address: the address the card is delivered to. Optional: leave it out when your personalization bureau ships cards to you in bulk and you distribute them yourself.
As with virtual cards, the tenant_customer_ref and tenant_account_ref fields are required. They hold your references to the customer and their account. You don't need to set instrument.
The Card Program decides how the card is issued, including the card network, the personalization bureau and the card design used for production. A Card Program issues either virtual or physical cards, so a physical card needs a Card Program for physical cards. See BIN Setup and Card Programs for more details.
printed_name and shipping_address are personal data. They are only used for card production and delivery. They are never included in webhook notifications.
Sample request
Headers:
Idempotency-Key: 40709949-0712-487c-a2fe-1dd2e64af506
Payload
{
"type": "physical_card",
"tenant_customer_ref": "customer-00000000000001",
"tenant_account_ref": "FR00000000000001",
"tenant_token_ref": "TOK000000000000001",
"card_program_id": "3c1e7a52-8f4b-4d2a-9e6f-1b2c3d4e5f60",
"printed_name": "JANE DOE",
"shipping_address": {
"line1": "1 Raffles Place",
"line2": "#20-01",
"city": "Singapore",
"postal_code": "048616",
"country_code": "SG"
}
}
Sample response
{
"tenant_account_ref": "FR00000000000001",
"tenant_customer_ref": "customer-00000000000001",
"of_customer_id": "40095c2f-d391-4e06-94d9-cf0b3191c548",
"of_account_id": "5bafb9bc-9573-4acf-b686-04bf62c81af8",
"customer_id": "40095c2f-d391-4e06-94d9-cf0b3191c548",
"account_id": "5bafb9bc-9573-4acf-b686-04bf62c81af8",
"static_token_id": "180106f9-8177-42fa-99bf-23ae8d785636",
"instrument": "manual_card_entry",
"status": "inactive",
"locked": false,
"card_program_id": "3c1e7a52-8f4b-4d2a-9e6f-1b2c3d4e5f60",
"created_at": "2026-03-10T10:27:58.253Z",
"updated_at": "2026-03-10T10:27:58.253Z"
}
The physical card details, such as printed_name, shipping_address, provisioning_status and fulfilment_status, are returned when you get the card.
No-name cards
A no-name card has no cardholder name printed on it. Issuers use them, for example, to hand out cards instantly in a branch. To issue a no-name card, leave out printed_name. No-name cards are usually shipped to you in bulk, so you can also leave out shipping_address. Whether no-name cards are possible depends on your Card Program and personalization bureau.
Card status after creation
A new physical card is always created with status inactive. Physical cards are never activated automatically. The card can only be used after it has been activated, normally once the cardholder has received it.
Card production and delivery
Once issuance is complete, Open Fabric automatically sends the card to the personalization bureau configured for you. The bureau embosses and prints the card and encodes its chip. Card data goes straight from Open Fabric to the bureau and never passes through your systems.
How cards reach the cardholder depends on what you agree with your bureau:
- Bulk delivery to you: the bureau ships the produced cards to you in bulk, and you deliver them to your cardholders through your own delivery partner. You don't need to send a
shipping_address. - Direct delivery by the bureau: the bureau mails each card directly to the cardholder's
shipping_address.
The physical_card.fulfilment_status field, returned when you get the card, is created once the card has been sent for production. When the cardholder has received the card, activate it.
Handling timeouts and failures
Issuing a physical card involves several steps: creating the card, registering it, and generating the CVV and PIN. A newly issued physical card returns 201 Created. Resuming an incomplete issuance, or replaying a completed request with the same Idempotency-Key, returns 200 OK.
The provisioning_status field shows how far issuance has progressed:
provisioning_status | Description |
|---|---|
card_created | The card has been created. |
wait_registration | Waiting for the card to be registered with the network. |
generating_cvv | Generating the card's CVV. |
generating_pin | Generating the card's initial PIN. |
completed | Issuance is complete. The card will be sent for production. |
failed | Issuance failed. |
504–physical_card_provisioning_incomplete: issuance did not finish within the request time. The card is not lost. Retry the same request to resume from the step it reached.422–physical_card_provisioning_failed: issuance failed at one of the steps and can't be completed. The card is left withprovisioning_status=failed. Retrying the request returns the same error.
For all other errors, see the Provision account API reference.
See Idempotency for more on retrying requests safely.