We are in the process of coding to the COF mandates. We are being told that the TransactionID returned in the verification transaction response is being generated by VISA and passed back through the processor to the requester. If that is the case, then is the following use case accurate:
Assuming I am the VISA card holder:
Any help would be appreciated.
That's a good question! Can you please let us know which VDP API you are relating your questions to? Once you provide us with the name of the API product that you are referring to then I will be able to provide you with further assistance.
Please check our website for specific APIs relevant to your business case.
That would be a great question, and one i must guess at as we are writing our own card gateway, where we will be integrating to multiple processors, such as Global Payments, FirstData, etc., we are not coding directly to VISA. Since they are the ones ultimately sending the verification request to you, I would assume they would be using the Payment Verification API.
The question comes down to the TransactionId value returned in the verification transaction response.
If my card is verified before storing it for Credential on File mandates, does the TransactionID value returned the very first time it is verified stay with it on subsequent verifications? Or as my card is verified by the many billers/merchants that I have my card stored with get a new TransactionID values assigned to it? When a verification transaction request comes in, Does VISA/Issuing bank check to see if a card account as already been verified, if it has, it will it send the same TransactionID value it first created or will it generate a new value?
To further clarify, are you relating your questions to the Visa Payments Processing APIs, which include the Verification API?
The Verification API can be used to validate cardholder account information. Account verification is supported for both Visa and non-Visa brands*. Link to this API is here - https://developer.visa.com/capabilities/vpp/docs-getting-started#section5
Please confirm, thanks!