Virtual Cards
Issue Virtual Card
Issue a single-use virtual card through a supported provider and automatically tokenize it.
POST
Issues a virtual card through a supported provider (e.g. WEX, Rapyd) and automatically stores the issued card as a PCI Booking token. 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
Your API key prefixed with
APIKEY. Example: APIKEY your-api-key. See the Authentication guide.Query String
The ID of stored credentials for a virtual card provider. When provided,
ProviderName and Credentials in the request body are ignored.Token storage region. One of:
US, IN, AU, JP, CA, IE, GB, BR. If omitted, uses the account default.Request Body
The virtual card provider name (e.g.
WEX, Rapyd). See List Virtual Card Providers for available providers. Not required when credentialsId is provided.Provider-specific credential key-value pairs. Not required when
credentialsId is provided. See the provider’s credential structure for required fields.The virtual card issuance request.
Response
201 - Virtual card issued and tokenized. TheLocation header contains the PCI Booking token URI.
Response Fields
The PCI Booking token for the issued virtual card.
The virtual card provider’s response.

