Setup for Virtual Cards

This guide describes developer implementation for virtual cards. For general information and use cases, see Virtual cards in the Choose Your Card Strategy guide.

For information about digital cards, see Digital cards in the Choose a Card Strategy guide.

To create a virtual card account you must first set up a virtual card product. See Galileo setup for the parameters. This card product does not have embossing information included with it.



There is a difference between virtual cards—cards that do not have a physical counterpart—and virtual accounts, which are accounts that do not have cards, such as savings or overdraft accounts.

As part of a virtual-card product setup, you must submit at least one virtual card template to Galileo. Follow the instructions for digital card design in the Design a Card guide.

Creating a virtual card account

Consult this table for the endpoints to use when creating a virtual card account. In all cases, the prodId must be for a virtual card account.



Because the card is active upon creation, Galileo sends the BACT: card_activated event webhook.

Use CaseEndpoint
Onboard a new customer and issue a virtual cardCreate Account

(Creating an Account guide)
Onboard a new customer and issue a virtual card. You must be PCI compliant to use this endpoint.Create Virtual Card Account

(Creating an Account guide)
Add a virtual card account to an existing customer recordAdd Account

(Adding an Account guide)

Presenting the virtual card

After the card account has been created, you can retrieve the card image to display in your app or on your web site. Follow the instructions for Digital card images in the Retrieving Card Information guide.

Upgrading to a physical card

If you are using a Virtual First strategy—where you issue a virtual card first, then upgrade to a physical card for cardholders who meet certain criteria—follow the instructions in Use case 2: Product switch with reissue and same PAN and expiry in the Switching Products guide.

Galileo setup

These internal parameters must be set at Galileo, according to your use case.

NNEXPProductPrevents a new expiry from being generated for the physical card. Set to Y for virtual cards to be upgraded to physical by product switch (Virtual First) or for digital images of physical cards (Digital First).
TSECVProgram or productMaximum seconds of access-token validity (default: 300) when retrieving the virtual card image.
TUSECProgram or productMaximum times an access token can be used (default: 3) when retrieving the virtual card image.