There are two use cases for updating a Virtual Card. One is to update the PurchaseType which in turn updates the MCC where the Virtual Card can be used at. The second use case is for reloading the card in the event an issue occurred that requires more value to be added. Both scenarios are explained below.
Updating PurchaseType to change where a Virtual Card may be used at
When a Virtual Card is first created using the /IssueCard route, the PurchaseType in that original request dictates what MCC group (a list of MCCs that fall under the specific type of travel supplier) should be applied to the Authorization Controls (what MCCs the VC can be authorized at). There are a couple cases where these MCC groups need to be changed: When a mistake was made when the VC was issued - use this PUT route to update the PurchaseType to the appropriate PurchaseType. When the travel supplier is under the wrong MCC but the MCC is unknown - use this PUT route to update the PurchaseType to 98.
Reloading the Virtual Card amount
Reloading a card is useful in a few scenarios. One example would be when a supplier has used the Virtual Card, but then there was a change that required them to charge a bit more than what was issued. Or, if the supplier used the card, voided it for some reason and needs to process the transaction again. When a Virtual Card is voided, the funds are not available for immediate use - so this presents issues as the supplier may expect to be able to use the Virtual Card after it’s voided. Reloading the card will allow them immediate availability to use the card again.