A card's status is designated by a single capital letter in the Galileo system, as shown in the <a href="ref:api-reference-card-statuses" target="_blank">Card Statuses</a> enumeration.

Note

Card status is not the same as account status. The statuses may be similar in some cases, but they operate independently. Compare with the <a href="ref:api-reference-account-statuses" target="_blank">Account Statuses</a> enumeration.

When a merchant attempts to authorize a transaction, the Galileo system checks to see whether the card is active (`status: N`). The account must also be active (`status: N`) for the transaction to be approved. When a card or account is not active the authorization request is denied.

In both the <a href="ref:api-reference-card-statuses" target="_blank">Card Statuses</a> and <a href="ref:api-reference-account-statuses" target="_blank">Account Statuses</a> enumerations, the columns on the right show which operations are permitted for each status. Keep in mind that the Galileo system always checks both the card and account statuses when determining whether to allow a transaction.

## Changing card statuses

The original status of a card is determined by the XAACT parameter. This parameter has three characters—the third character specifies which status to assign to new cards. Default is `W` (waiting to be processed). For virtual and <<glossary:Digital First>> cards the value is `N` (normal, active), because they are activated at the time they are created.

Card statuses can be changed either manually with an endpoint or automatically by internal Galileo processes. To manually change a card status, use the <a href="ref:post_modifystatus" target="_blank">Modify Status</a> endpoint. Make sure the `type` affects what you want it to affect—some types affect both the card and the account, whereas others affect only the account or only the card. See <a href="ref:api-reference-modify-status-types" target="_blank">Modify Status Types</a> for the list of possible values.

Automated processes that change a card status include:

  • **Emboss process** — Picks up cards in `status: X` (set to emboss) or `status: W`, includes them in the batch file for the emboss vendor, and changes the cards to `status: Y` (ready to activate).

  • **Card activation** — When the cardholder activates the card using your designated methods, the card is changed to `status: N` (normal, active). Depending on your settings, other cards on the account may be set to `status: C` (canceled) at the same time. See <a href="doc:activate-card-procedure" target="_blank">Activating a Card</a> for more information.

  • **Lost/stolen** — When you use <a href="ref:post_modifystatus" target="_blank">Modify Status</a> to report a lost or stolen card, the process changes the card to `status: L` or `status: S`. See <a href="doc:lost-stolen-or-damaged-cards" target="_blank">Lost, Stolen, or Damaged Cards</a> for more information.

  • **PIN failures** — When the number of failed PIN attempts reaches a threshold, the card may be changed to `status: B`, depending on your settings.

  • **Card reissue or replacement** — When a reissued or replacement card is activated, the previous card may be set to `status: C` or `status D`, depending on the parameters you pass with the <a href="ref:post_reissuecard" target="_blank">Reissue Card</a> endpoint call. See <a href="doc:reissuing-cards" target="_blank">Reissuing Cards</a> for more information.

  • **Fraud detection** — If you are using Galileo's fraud-detection engine, you can configure a rule to set a card to a disabled status when certain criteria are true.

## Freezing cards

Instead of reporting a card as lost or stolen, your cardholders might want to temporarily freeze a card. A frozen card cannot be used for purchases but has not been canceled. As soon as the card is unfrozen it is usable again without reissuing the card or creating a new card. Reasons for freezing a card rather than disabling or canceling it include:

  • The cardholder cannot locate their card but is not ready to report it lost or stolen.

  • Parents want to stop their teenager from accessing funds for a time.

  • A company wants to temporarily withdraw fund access for an employee.

To freeze a card call the <a href="ref:post_modifystatus" target="_blank">Modify Status</a> endpoint with `type: 17`. To unfreeze it use `type: 18`.

When you call Modify Status with `type: 17` to freeze a card, use the `startDate` and `endDate` as follows:

`startDate``endDate`Result
_blank__blank_Freeze starts at the current date-time and ends in current date-time +24 hours in Galileo System Time.
_blank_PopulatedFreeze start defaults to current date-time in <a href="ref:galileo-system-time" target="_blank">Galileo System Time</a>.
Populated_blank_Returns status code 2.

When unfreezing a card with `type: 18`, the `startDate` and `endDate` parameters are ignored and the card is unfrozen immediately.

When a card is frozen because of suspected fraud—such as when a fraud-detection rule is triggered—the expiration date is set to 3000-01-31. Fraud-related freezes that are created by the API or the CST have that same expiry date.

Note

Modify Status types 17 and 18 do not change the card or account status. To see whether a card is frozen call the <a href="ref:post_getcard" target="_blank">Get Card</a> or <a href="ref:post_getaccountcards" target="_blank">Get Account Cards</a> endpoint and check the `freeze_info` object.

  • When a card is frozen, Galileo sends the <a href="ref:api-reference-events-api-frozen" target="_blank">`FRZN: frozen`</a> event message.

  • When you unfreeze a card using Modify Status, Galileo sends the <a href="ref:api-reference-events-api-unfrozen" target="_blank">`UFRZ: unfrozen`</a> event message.

  • When a card freeze expires, Galileo does not send an event message.

### Affected transaction types

When a card is frozen, it cannot be used for transactions that arrive at Galileo through the authorization stream:

  • Authorizations (purchases)

  • Completions

  • Reversals

  • Merchant credits

  • Card loads (except Green Dot and Western Union)

Note

If you want to permit transactions on frozen cards that credit the account, set CTRNS. Setting this parameter permits merchant credits, reversals, and card loads, but anything that debits the account is still blocked.

Transactions that are not initiated in the authorization stream can still be performed:

  • Settlements

  • ACH

  • Billpay, including scheduled transactions

  • Direct deposits

  • Funds movement created by automated processes or the Program API (payments, adjustments, internal transfers, fees)

  • Provisional credit and other dispute-related money movement

  • Green Dot and Western Union card loads

## Events API messages

These event messages indicate stages in the card lifecycle and changes to card status. You must arrange with Galileo to receive these event messages:

  • <a href="ref:api-reference-events-api-card-shipped" target="_blank">`SHIP: card_shipped`</a> — The card has been picked up by the emboss process and is included in the batch file for the embosser. Card is now in `status: Y`.

  • <a href="ref:api-reference-events-api-card-activated" target="_blank">`BACT: card_activated`</a> — Card has been activated and is now in `status: N`.

  • <a href="ref:api-reference-events-api-card-status-change" target="_blank">`CSNT: card_status_change`</a> — The card status has changed to a status specified in the CDMSG parameter. This event message is triggered regardless of which process changed the status.

  • <a href="ref:api-reference-events-api-frozen" target="_blank">`FRZN: frozen`</a> — The card has been frozen. The `status` has not changed.

  • <a href="ref:api-reference-events-api-unfrozen" target="_blank">`UFRZ: unfrozen`</a> — The card has been unfrozen. The `status` has not changed. This event is not sent when a freeze expires.

  • <a href="ref:api-reference-events-api-bulk-frozen" target="_blank">`CDFR: bulk_frozen`</a> — The card has been frozen by a bulk-freeze action in the <<glossary:CST>>.

  • <a href="ref:api-reference-events-api-card-expiring" target="_blank">`RBEX: card_expiring`</a> — The card will expire in the number of configured days. Default: 30 days.

  • <a href="ref:api-reference-events-api-card-returned" target="_blank">`PSUC: card_returned`</a> — The cardholder mailed the card back and the shipping room recorded the return.

  • <a href="ref:api-reference-events-api-lost-stolen-card-no-replacement" target="_blank">`LSCN:lost/stolen card no replacement`</a> — The card has been marked lost or stolen and no replacement card has been created. Status is `L` or `S`.

  • <a href="ref:api-reference-events-api-lost-stolen-card-with-replacement" target="_blank">`LSCR:lost/stolen card with replacement`</a> — The card has been marked lost or stolen and a replacement card has been created. Status is `L` or `S`.