---
title: "Issue Card (Instant)"
method: POST
path: "/cards/{cardholderId}/instant"
tags: ["Cards"]
---

# Issue Card (Instant)

`POST /cards/{cardholderId}/instant`

This endpoint offers similar card issuing functionality as [the main card issuing endpoint](./issue-card), but specifically allows for a _synchronous_ and _instant_ card issuing, 
whereas the main card issuing flow works asynchronously and requires the consumption of a callback to confirm the card is actually active. 
This endpoint issues cards instantly in a synchronous fashion. Meaning the card is active and usable when this endpoint returns a `200 Ok` response. 
The use case being here a fully automated card issuing flow, followed by an immediate card usage on API level for normally PCI-DSS certified companies. 
Please note, that the [sensitive card data](./card-pan-and-cvv-pci-vault) still needs to be fetched separately after issuing a new card (if PCI-DSS compliant).

**This endpoint should only be used if aligned with Pliant upfront. In 90% of cases, you want to use the normal card issuing endpoint instead, as linked above.**

## Path parameters

- `cardholderId` string, uuid, required

## Request body

- 0 — unresolved $ref

## Response `200`

Ok. The card can be directly used now.

- Schema — unresolved $ref

## Other responses

- `400` — unresolved $ref
- `401` — unresolved $ref
- `403` — unresolved $ref
- `404` — unresolved $ref
- `429` — unresolved $ref
- `500` — unresolved $ref

---

[API](https://skmtc.dev/getpliant/apis/pliant-customer-api.md) · [All operations](https://skmtc.dev/getpliant/apis/pliant-customer-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/getpliant/pliant-customer-api/revisions/f3f589cfa718/schema)