Card Expiration
As you set up each card product, you consult with your bank to determine how many years until expiration. Galileo then assigns an expiration (expiry) date to the cards it issues for your program. This date is printed on the physical card, is known to the customer, and is recorded in the cards table.
On the card, the expiry date is expressed as a month and year (MM/YY), with the card expiring on the last day of the month. Beginning at 00:00 (midnight, Galileo system time) on that last day, the card can no longer be used. For example, if the card's expiry is 6/26, the card's last valid day is 29 Jun 2026, and at midnight on 30 Jun 2026, the card cannot be used.
In the Galileo system, Galileo represents expiry dates in multiple ways:
- In Program API responses – Galileo represents expiry dates as
expiry_dateusing a YYYY-MM-DD format. This response can also include a time if you set the CXPTM parameter. - In events – Galileo represents expiry dates as
exp_dateusing a MM/DD/YYYY format. - In RDFs – Galileo represents expiry dates as
EXPIRATION DATEusing a YYYY-MM-DD hh:mm:ss format.
In all of these instances, the day and time listed do not affect the actual expiry date of the card. Unless you've set a specific expiration time using the CXPTM parameter, the expiry day or time just reflects the day of the month that the card was created in the Galileo system.
For example, a Create Account response might include expiry_date: 2026-06-13, because the card was created on the 13th day of the month. However, the card expires at midnight on 30 Jun 2026, not on the 13th.
Updated about 3 hours ago