Update Debit Card Status Codes and uses

[bpsymano]

I have a question regarding the use of Card Services/Update Card Status (V2) and its codes.

https://developer.visa.com/capabilities/dps-card-and-account-services/reference#tag/Card-Services/op...

PUT https://sandbox.api.visa.com/dcas/cardservices/v2/cards/{cardId}/cardstatus
Is the intention of this endpoint to set a "decline" code, so when the card use is attempted the vendor is presented with the reason?

In testing, it seems that once the code is set it can not be reset to some other value.

Thank you,

Bruce

[jenn_kh · Accepted solution]

Thank you for reaching out, @bpsymano! An agent will get back to you as soon as possible. In the meantime, if anyone has any ideas that may be helpful to Bruce, feel free to reply here. -Jenn

[API_Products · Accepted solution]

Hi @bpsymano,

The DPS Card and Account Services API is available for use by issuer banks and fintech. This service updates the card status for a given card ID that is associated to a card number and updates the card record in real-time. You can send an update card status request for the card status value to be updated from the enumeration list.

For prepaid, must use valid values available for prepaid:
ACTIVE
SUSPENDED
LOST_CARD
STOLEN_CARD
CLOSED
DAMAGED

For debit, must use valid values available for debit:
LK-LOCKED_BY_CARDHOLDER
__-UNLOCK_BY_CARDHOLDER
__-REMOVE_HOT_CARD_STATUS
P-NO_CARD_RECORD
76-DO_NOT_HONOUR
7A-DO_NOT_HONOUR
7B-DO_NOT_HONOUR
7C-DO_NOT_HONOUR
92-DO_NOT_HONOUR
96-DO_NOT_HONOUR
AH-DO_NOT_HONOUR
AI-DO_NOT_HONOUR
AM-DO_NOT_HONOUR
PF-NO_CARD_RECORD
PH-DO_NOT_HONOUR
Q1-GENERAL_DENIAL(NO_CARD_PICK_UP)
Q4-DO_NOT_HONOUR_(PICKUP)
AD-LOST/STOLEN_CARD_(PICK_UP_CARD)
ND-LOST/STOLEN_CARD_(NO_CARD_PICK_UP)
PU-HOT CARD=TRANSACTION_DENIAL_(PICK_UP_CARD)
Q3-CARD_MISPLACED_(PICK_UP_CARD)
AE-FRAUD_(PICK_UP_CARD)
NE-FRAUD_(NO_CARD_PICK_UP)
QD-SUSPECTED_COUNTERFEIT_CARD
AK-PERMANENT_RESTRAINT_(PICK_UP_CARD)
NK-PERMANENT_RESTRAINT_(NO_CARD_PICK_UP)
Q5-CARD_ACCEPTOR-CALL_ISSUER
Q6-CARD_ACCEPTOR-CALL_ISSUER
RI-VIOLATION_OF_LAW
X1-CARD_NOT_EFFECTIVE
AL-BAD_DEBT_(PICK_UP_CARD)
NL-BAD_DEBT_(NO_CARD_PICK_UP)
C3-CR-DDA_CLOSED_OR_RESTRICTED_FOR_CLOSING
D3-DDA_CLOSED_OR_RESTRICTED_FOR_CLOSING
P8-CLOSED_ACCOUNT_(NO_CARD_PICK_UP)
P9-DORMANT_ACCOUNT_(NO_CARD_PICK_UP)
S3-SAV_CLOSED_OR_RESTRICTED_FOR_CLOSING
UJ-ACM_ACCOUNT_IS_CLOSED
NH-EXPIRED_CARD_(RETURN_CARD)
P6-CR_CLOSED_OR_RESTRICTED_FOR_CLOSING

[bpsymano · Accepted solution]

Diana, thank you for the reply.

I did see the codes you've included in the API documentation.

My questions is, should I, as an issuer, be able to change the status once its already been set?

e.g. status set to Q1-GENERAL_DENIAL(NO_CARD_PICK_UP), then attempt to set status to __-REMOVE_HOT_CARD_STATUS
There seems to be a one time set on the ones I've tested with, as though setting the status renders the card no longer usable by the cardholder.