Through this service, issuers can place stop payment instructions in the VisaNet Cardholder Database (CDB) in line with a cardholder's request. When an eligible transaction is matched to a stop instruction during Authorization, a decline response code informs the acquirer that the cardholder has withdrawn their consent for payment to be taken from the card. Acquirers are expected to pass this decline response code through to the merchant, and the merchant is not expected to resubmit the Authorization Request. If the transaction is submitted unauthorized for clearing and settlement, VisaNet will again attempt to match and return the transaction to the acquirer with the corresponding return response code.
The process for stopping a payment is as follows:
- The issuer creates a stop payment instruction using the VSPS APIs on VDP, or the VSPS user interface on Visa Online.
- The instruction is allocated a unique ID and at a minimum needs to contain the Visa card number, the stop payment type, a merchant identifier (Card Acceptor ID, Merchant Name, Payment Facilitator ID or MCC) and the active date range. It may optionally include additional transaction identifiers to help ensure that only the intended payments get stopped, such as minimum and maximum transaction amounts.
- VisaNet matches authorization and clearing messages based on:
- Transactions identified as "eligible" for stopping.
- Matching criteria defined in the stop payment instruction.
- If a match is identified, VisaNet:
- Declines an authorization request with a specific response code, either R0, R1 or R3 and sends an advice to the issuer.
- Returns a clearing message to the acquirer with a specific return/reclassification reason code, either C0, C1 or C2.
- Stopped transactions are assigned back to the specific stop instruction ID, allowing stop instruction performance to be assessed later using the VSPS UI.