Activate Card

post

https://api-{corename}.{env}.gpsrv.com/intserv/4.0/activateCard

Use the Activate Card endpoint to activate a physical card that has an emboss record in status: Y. Do not use this endpoint to activate a virtual card; instead, use the Modify Status endpoint with type: 7.

Consult the Activating a Card procedure for more information.

If you are not PCI compliant, you can use this endpoint only under certain circumstances. See PCI compliance in Setting Up a Card Program for details.

Status codes

See Global Response Statuses for status codes that are common across endpoints.

The table below lists status codes that apply to this specific endpoint.

Status code	Description
467-01	`No unactivated cards found that match all parameters`. No cards with an emboss `status: Y` match the cardholder-provided input. Cardholder must supply correct card data.
467-02	`No unactivated cards found`. No cards with an emboss `status: Y` match the PRN or customer ID. Retry with valid PRN or customer ID. Your product settings determine which value the system searches on.
467-03	`Card successfully activated - However, there were were errors deactivating temporary cards`. Verify that your product parameters are correct, or send a Modify Status call with `type: 2` for the temporary cards.
467-04	`Invalid account - account is in charged off status and cannot be modified`. Account is in `status: R`. Inform the cardholder that the card cannot be activated.
467-05	`Invalid account - account is in fraud status and cannot be modified`. Account is in `status: F`. Inform the cardholder that the card cannot be activated.
467-06	`Card not activated - card in blocked status`. Account is in a status that is specified in the CRDBL parameter. Inform the cardholder that the card cannot be activated.

Form Data

apiLogin

string

required

Web service username, as provided by Galileo.
Pattern: Max 50 characters
Example: "AbC123-9999"

apiTransKey

string

required

Web service password, as provided by Galileo.
Pattern: Max 15 characters
Example: "4sb62fh6w4h7w34g"

providerId

int32

required

Galileo-issued provider identifier.
Pattern: Max 10 digits
Example: 9999

transactionId

string

required

1 to 60

A unique provider-generated ID to identify this API call. A UUID is preferred.
Pattern: 60 characters or less
Example: "9845dk-39fdk3fj3-4483483478"

accountNo

string

required

≤ 18

The PRN, PAN or CAD of the account. For card-specific endpoints such as this one, the CAD is preferred. Do not use the PRN if more than one card has ever been associated with this account.
Pattern: PAN, PRN, or CAD
Example: "074103447228"

cardExpiryDate

string

required

The expiry date provided by the cardholder. This value is compared to the expiry date in the Galileo system.
Pattern: YYYY-MM
Example: "2019-01"

cardSecurityCode

string | null

The CVV value provided by the cardholder. This value is compared to the CVV in the Galileo system.
Pattern: 3 digits
Example: "123"

cardNumberLastFour

string | null

If accountNo contains a PRN, and multiple cards are associated with this account, use this value to ensure that the correct card is selected.
Pattern: 4 digits
Example: "0789"

deactivateTemporaryCards

int32 | null

0 to 1

If temporary cards were issued, this controls whether to deactivate the temporary cards:

1 — Deactivate
0 — Do not deactivate

Pattern: Integer
Example: 1

Headers

response-content-type

string

enum

Defaults to json

Use this header instead of the standard accept header to specify the response format.

Allowed:

string

enum

Defaults to application/json

Generated from available response content types

Allowed:

Response

Language

URL

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

application/xml

Status codes

default