authUserId (the UAC role assignment ID returned by addAuthorizedUser) to create the card for that user’s underlying cardholder record while keeping the card scoped to the caller’s account.
The authUserId must belong to the caller’s account, must be ACTIVE, and cannot be an OWNER assignment. If addAuthorizedUser returns PENDING, the authorized user must accept the invite before this mutation can use that authUserId.
Virtual card creation can use a saved billing address (userAddressId) or an inline billingAddress. For select offers, providing either address value triggers billing-address registration with the card issuer before the card is issued. If issuer approval is still pending after the server-side wait window, the mutation returns GraphQL error code VC-0020 with extensions.addressId; retry with that value as userAddressId.
🔒 Restricted Access
This mutation requires a Bearer token with the CREATE_VIRTUALCARD scope.
Parameters
Response
Success Response
Response Fields
Example Requests
Create a card for an authorized user with a saved address:Full Flow: Register User, Add Authorized User, Add Address, Create Card
This flow registers a new Fluz user, adds that user to the caller’s account as an authorized user, saves a billing address for that authorized cardholder, then creates a virtual card on their behalf. Step 1: Register the user. This requires a Bearer token for the developer user of an ACTIVE application with registration enabled.status is ACTIVE. If the status is PENDING, the authorized user must accept the invite before addVirtualCardAddress or createVirtualCard can use the returned authUserId.
Step 3: Save the authorized user’s billing address.