When to use Verify
Situations where Verify could be used.
- First payment from a new card
In parallel with the first payment from a new card for a customer, following capture of the card details, you want to verify that the customer name matches the name held by the issuer - prior to allowing a payment to proceed. You may want to take different actions in your separate payment flow depending on the result of the check - allowing the payment to proceed, failing the payment, or holding the payment. - Regular checks on an existing card-on-file
You may want to perform ad-hoc checks on saved cards on file - either timing these on, for example, an annual basis, or following a lifecycle event for the card such as issuance of a new card linked to a network token. This check is likely to be standalone from a payment. - Checks on imported cards
When you are importing a new set of cards, or when you gain access to the service for the first time and have an existing set of saved cards on file, you may want to run all of the cards through verification in a bulk exercise. This would be performed standalone from a payment. - Requesting last month's Verify data report from BR-DGE
You can request a report for last month's Verify data showing for each verification request:-
Date and time of verification request
-
Request MUT
-
Visa ANI response
-
BR-DGE normalised response
You can then analyse the partial match responses to flag accounts for data cleansing.
-
Updated about 1 hour ago
Did this page help you?