Release Notes for 28 October 2022

New changes to the GPS Cards API for the week ending 28 October 2022.

Update Card endpoint updated to support Master Virtual Cards

The Update Card endpoint has been updated to support the Master Virtual Card cardtype.

👍

Documentation

For more details on updating a card, see Updating a Card

Automatic Web Service Fees added to endpoints

The following endpoints have been updated in this release so that program managers can automatically charge customers on using the service. When the request is successful and the specific condition for the endpoint has been met, a new fee transaction for the card will be created.

📘

Note

Automatic web service fees should be completed on the Web Services Fees tab of the customer PSF. For more details, see the Fees Guide.

The below table details each of the available endpoints, the conditions required for a fee to be charged to the card, and the FeeType.

Endpoint

Condition

FeeType

POST /cards

CardType is Virtual

VirtualCardIssuingFee

POST /cards

CardType is Physical

PhysicalCardIssuingFee

PUT /cards/{publicToken}/status

Status is “Active” and Card is Parent Card

ParentCardActivationFee

PUT /cards/[publicToken}/status

Status is “Active” and Card is Parent Card

ChildCardActivationFee

POST /cards/{publicToken}/pin

N/A

PINCVVServiceFee

GET /cards/{publicToken}/pin/status

N/A

PINCVVServiceFee

POST /cards/{publicToken}/pin/unblock

N/A

PINCVVServiceFee

GET /cards/{publicToken}/cvv

N/A

PINCVVServiceFee

GET /cards/{publicToken}/cvv/status

N/A

PINCVVServiceFee

PUT /cards/{publicToken}/cvv/status

N/A

PINCVVServiceFee

POST /cards/{publicToken}/renew

N/A

CardReplacementFee

POST /cards/{publicToken}/replace

RenewStep is empty or RenewState is Renew or RenewStep is RenewWithSameExpiry

CardReplacementFee

POST /cards/{public Token}/cardType

CardType is Physical

CardConversionFee

👍

Documentation

For more details on Web Service Fees, see Web Service Fees