I have a question regarding the use of Card Services/Update Card Status (V2) and its codes.
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.
Solved! Go to 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
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:
For debit, must use valid values available for debit:
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.