For Galileo clients who want to provide instant spending-account availability as well as physical cards to their customers, Galileo offers the Digital First program. When your customers sign up for a Digital First product, you immediately provide them with an image of the physical card that is displayed in your app or on your web site, or the card can be provisioned to a mobile wallet. At the same time, Galileo sends a card order to the embosser. The physical card has the same PANPAN - Primary account number. The 16-digit number that is printed on a card, beginning with the BIN. This number is not the same as the account identifier, which is the PRN, or the card identifier, which is the CAD., CVVCVV - Card verification value. A number that is included on a card to help verify that a cardholder has the actual card (physical or virtual) in hand. CVV1 is a value that is embedded in a card's magnetic stripe, CVV2 is a 3- or 4-digit number printed on the actual card, and iCVV is a number embedded in security chips. In most cases, "CVV" refers to CVV2., and expiry dateexpiry date - The date that a card expires. This date is displayed on a virtual or physical card and is randomly set at the time the card is created. The expiry date is encrypted in the Galileo system and cannot be retrieved by anyone who is not PCI compliant. as the digital card, so if the customer sets up recurring payments with the digital card, the arrival of the physical card won't require them to input new information. When the physical card arrives at the customer's location, the card is already activated, so they can use it immediately after setting the PIN.
- You and Galileo set up a Digital First product.
- Your customer goes to your app or web site and signs up for the product.
- You create the customer account.
- The card is created in an active state.
- You retrieve a digital version of the physical card and present it to the customer in your app. The customer can see the PAN, CVV, and expiry. Alternatively, you provision the card to a mobile wallet.
- The physical card order is sent to the embosser.
- The customer uses the digital card for purchases and other purposes.
- The physical card arrives in the mail, and the cardholder can use it immediately after setting the PIN.
You must provide a digital card template to Galileo.
- For cards that are provisioned to mobile wallets, see About Mobile Wallets.
- For other cards, see Creating a digital card template in the Digital Cards guide for instructions.
The sequence of events for card creation is slightly different for Digital First cards than for conventional cards. You must also arrange with Galileo to receive the event webhooks:
- You call Create Account or Add Account.
- Galileo creates the account and card records.
- Because the card is active upon creation, Galileo sends the
BACT: card_activatedevent webhook.
- The emboss process places an emboss record in a file to send to the embosser. This process runs once per day.
- When the emboss record is placed in the file, Galileo sends the
SHIP: card_shippedevent webhook.
When using the Create Account endpoint for a Digital First product, the
CAPP: app_completedevent webhook is not sent.
Because the card is in an active state upon creation, there is a risk of the physical card being intercepted and used while in transit to the cardholder. To prevent the physical card from being used before it reaches the cardholder, set a block when the account is created, and then when the cardholder sets the PIN for the physical card, remove the block. (This type of block does not prevent the account from receiving deposits.)
At the time of account creation, call the Set Account Feature endpoint. According to your use case, choose one of two types of block:
- If you do not provide your cardholders with the PAN immediately, set Feature 20 so that the physical card cannot be used online or at physical points of sale. However, push-provisioning a card to a mobile wallet and mobile wallet transactions are permitted.
- If you provide the PAN to your cardholders to use immediately, set Feature 21, which prevents the physical card from being used at physical points of sale. This setting permits card-not-present and mobile wallet transactions.
Account Features 20 and 21 are mutually exclusive—only one can be set to
Yat a time.
Your next steps depend on how the PIN was set:
- If your cardholders use the IVRIVR - Interactive voice response. A telephone-answering system that can recognize caller speech and touch-tone input. Galileo offers an IVR for customers to activate their cards and set their PINs. to set the PIN, Feature 20 or 21 will be automatically set to
N, and you will receive the
PINC: PIN_changed event. Your IVR process must specifically be configured for Digital First for this automation to work.
- If your cardholders use another method besides the IVR to set the PIN, you will receive notification of the PIN set through the Account Events webhook, by arrangement with Galileo. When you receive notification that the PIN has been set, call the Set Account Feature endpoint again with these parameters, depending on which one you set previously:
Choose one of these options:
- To provision the digital card to a mobile wallet, follow the About Mobile Wallets guide.
- To retrieve a digital image of the physical card, follow the Retrieving a digital card image procedure in the Digital Cards guide.
With cards in the Digital First program, the lost/stolen processes is the same as with other cards, with one variation—the physical replacement card is activated at the same time it is created, and then it is sent to the embosser. The digital version of the card is created at the same time, which can be used until the physical card arrives. See the Lost, Stolen, or Damaged Cards guide for the default lost/stolen processes.
When you report a physical card as lost or stolen, call the Set Account Feature endpoint and set feature 20 or 21, as you did at the time of account creation. When the cardholder sets the PIN for the physical card, remove the block.
If a cardholder reports a mobile wallet as lost or stolen, you can call Set Account Feature to set feature 22 to
Y, which blocks all mobile wallet transactions but permits card-present and card-not-present transactions.
When a cardholder reports the physical card as damaged, you can reissue the card using the same reissue process as for other card types:
A reissued Digital First card is not activated upon creation, and so there is no need to set account features to protect the reissued card in transit. No digital version of the reissued card is created, because the existing card is usable in mobile wallets and online until the reissued card is activated.
When a Digital First card is about to expire, Galileo automatically reissues the card. The number of days before expiration is configurable, with a default of 30 days. There is no need to protect the physical card while in transit and no digital version of the card is created.
These internal product parameters must be set at Galileo.
|FEMBO||Y||Forces cards to be embossed regardless of card status after account creation.|
|NNEXP||Y||Prevents a new expiration date from being generated by the card-emboss process, so that the digital and physical cards have the same expiry.|
|XAACT||YNN||Activates both the card and the account immediately after calling the Create Account endpoint. Bypasses the standard account/card setup processes to create a digital card that is active and ready to use immediately.|
Updated 3 months ago