Skip to main content
POST

Virtual Card Issuance Guide

Issue virtual cards through connected providers
Requests a virtual card from a connected issuing provider - see List Virtual Card Providers for the current list - and automatically stores the issued card as a PCI Booking token. The provider issues the card; PCI Booking does not. The card number and CVV in the response are masked for security. The token URI is returned in the Location response header.

Error Responses

Parameters

Headers

string
required
Your API key prefixed with APIKEY. Example: APIKEY your-api-key. See the Authentication guide.

Query String

string
The ID of stored credentials for a virtual card provider. When provided, ProviderName and Credentials in the request body are ignored.
string
Token storage region. One of: US, IN, AU, JP, CA, IE, GB, BR. If omitted, uses the account default.

Request Body

string
required
The virtual card provider name (e.g. WEX). See List Virtual Card Providers for available providers. Not required when credentialsId is provided.
object
Provider-specific credential key-value pairs. Not required when credentialsId is provided. See the provider’s credential structure for required fields.
object
required
The virtual card issuance request.

Response

201 - Virtual card issued and tokenized. The Location header contains the PCI Booking token URI.

Response Fields

string
The PCI Booking token for the issued virtual card.
object
The virtual card provider’s response.