This guide explains how to activate physical cards using the <a href="ref:post_activatecard" target="_blank">Activate Card</a> endpoint. Do not follow this procedure to activate virtual cards; instead, use the <a href="ref:post_modifystatus" target="_blank">Modify Status</a> endpoint if necessary. Most virtual cards are active upon creation.

As an anti-fraud measure, physical cards must be activated by the cardholder prior to use. (A <a href="doc:choose-a-card-strategy#digital-first-cards" target="_blank">Digital First</a> card is activated automatically upon creation but not when reissued.) You determine the card-activation method for cardholders in cooperation with your bank and Galileo at the time you set up your program. This method may be through Galileo's <<glossary:IVR>>, on your web site or mobile app, or by another method. If you choose the IVR option you do not need to follow this procedure.

Note

For <a href="doc:choose-a-card-strategy#digital-first-cards" target="_blank">Digital First cards</a> you should not follow this procedure, because the cards are already activated upon creation. Instead, follow the instructions in <a href="doc:setup-for-digital-first#protecting-the-physical-card" target="_blank">Protecting the physical card</a> in the _Setup for Digital First_ guide.

## Result of calling Activate Card

When <a href="ref:post_activatecard" target="_blank">Activate Card</a> has run successfully, the card is changed to `status: N` (active). If the CANOC parameter is set, the cardholder's other active cards have been canceled. If temporary cards were issued and the TEMPC parameter is set, the temporary cards have been canceled. (See [Galileo setup](🔗) for more information.)

## Parameters

This table explains the parameters that are specific to the Activate Card endpoint. See the <a href="ref:post_activatecard" target="_blank">Activate Card</a> endpoint reference for details.

ParameterUsage
`accountNo`Pass the <<glossary:PRN>>, <<glossary:PAN>>, or <<glossary:CAD>>. If you pass the PRN you may also want to request `cardNumberLastFour` from the cardholder to select the correct card. To pass in the PAN you must be PCI compliant.
`cardExpiryDate`_Cardholder-provided_. Use this value to test against the card to be activated.
`cardSecurityCode`_Cardholder-provided_. Use this value to test against the card to be activated.
`cardNumberLastFour`_Cardholder-provided_. If the cardholder has more than one card associated with their account, and if you passed PRN as `accountNo`, use this parameter to ensure that the correct card is selected.
`deactivateTemporaryCards`If you issued one or more temporary cards while the cardholder waited for the physical card to arrive in the mail, pass `1` to deactivate those cards. This applies to cards that are associated with the account of the card that is being activated (same PRN), not cards that are associated with other accounts that the account holder has. The TEMPC parameter must be set for this parameter to take effect.

## Card-activation workflow

This flowchart shows the logical progression of the <a href="ref:post_activatecard" target="_blank">Activate Card</a> endpoint. The actual sequence of events in the Galileo system may vary.



<!--activateCard-flowchart.pngggg-->

  1. Retrieve cardholder input, populate the <a href="ref:post_activatecard" target="_blank">Activate Card</a> endpoint, and send.

  2. Galileo performs a number of preliminary checks. Failures return the status codes shown in the diagram. Consult the [Status codes](🔗) table for next steps.

  3. Galileo checks for a card with the `accountNo` that has an emboss record in `status: Y`. Failure to find such an emboss record returns `status_code: 467-02`.

  4. Galileo verifies that the card's account is not in an improper status:

    • If it is in a status that is specified in the CRDBL parameter, the endpoint returns`status_code: 467-06`.

    • If it is in `status: F` (fraud), the endpoint returns `status_code: 467-05`.

    • If it is in `status: R` (charged off), the endpoint returns `status_code: 467-04`.

  5. If the data the customer supplied matches the data on record, Galileo activates the card and sends the webhook <a href="ref:api-reference-events-api-card-activated" target="_blank">`BACT: card_activated`</a>, if you are configured to receive it. If there is no match, the endpoint returns `status_code: 467-01`.

  6. If `deactivateTemporaryCards: 1`, Galileo attempts to deactivate any temporary cards that were issued. If Galileo cannot deactivate the cards, the endpoint returns `status_code: 467-03`. If the cards are successfully deactivated or `deactivateTemporaryCards` is not set, the endpoint returns`status_code: 0`.

## Sample endpoint request and response

Consult the <a href="ref:post_activatecard" target="_blank">Activate Card</a> endpoint to see how to build the API request and to see the response schema.

## Status codes

Consult <a href="ref:post_activatecard" target="_blank">Activate Card</a> to see status codes and next steps.

## View the activated card

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 `card_status`.

## Galileo setup

These product/program parameters affect card-activation behavior. Galileo sets these parameters according to your use case.

ParameterDescription
CANCSUsed in conjunction with CANOC, it specifies the status that a card must be in to be canceled when a new card is activated. Default: `N,X,Y,W`
CANOCWhen this parameter is set to `Y`, cards that belong to the same cardholder and that are in a status specified in CANCS are changed to status `C` (canceled) when the new card is activated. When this parameter is not set, the cardholder's other cards are not canceled. <br><br>Set this parameter at the product level so that cards with the same product ID are canceled. Set this parameter at the program level so that cards with the same program ID (including different product IDs) are canceled.
CRDBLContains statuses of cards that should not be activated.
TEMPCCancels temporary instant-issue cards when the personalized card is activated. The instant-issue card and the personalized card must have the same balance ID but different product IDs. Set this parameter on the instant-issue product.