VCAS Confirmed Marking API

Allows clients to notify VCAS when the status of a transaction has been verified

Confirmed Marking API

VCAS has identified an increased need for Issuers and Issuer Processors to be able to connect to VCAS in real-time to report fraud and good transactions coming through VCAS. The Confirmed Marking API is a real‑time ingress API within the Visa Consumer Authentication Service (VCAS) that allows issuers and issuer processors to notify VCAS when the outcome of a transaction has been verified. By programmatically marking transactions as Good, Fraud, or Undetermined, issuers provide critical feedback that improves fraud visibility and helps optimize VCAS risk models over time. This will provide better insights into fraud transactions for the VCAS issuers.

Many issuers are not able to manually mark transactions as fraud on VCAS as it is resource intensive from a technical development and operational perspective. The Confirmed Marking API will provide a better experience to issuers who would like to mark transactions as good or fraud under different use cases. This will also help enhance the VCAS Risk Model for better performance and better results for VCAS issuers.

The Confirmed Marking API supports the following transaction statuses:

• Good: These are transactions that cardholders have confirmed to be valid/good.
• Fraud: These are transactions that cardholders have advised were not made by them or are known to be fraudulent.
• Undetermined: These are transactions that cardholders have not provided confirmation on. That is, cardholders have not identified it to be good or fraudulent.
• Clear: Choosing Clear resets the selected transactions back to their original default status of Not Marked.

Key capabilities

• Mark single or multiple transactions with confirmed outcomes
• Support bulk confirmed marking for operational efficiency
• Enable continual learning for VCAS risk models through issuer feedback
• Improve fraud detection and approval rates by closing the feedback loop on transaction outcomes

Confirmed Marking Use Cases

There are currently three use cases of confirmed marking used by the Issuer:

• VCAS Portal Customer Service Application: API must provide functionality to mark single PAN as Good/Fraud/Undetermined.
• VCAS Portal Reporting Application: API must be able to mark multiple PANs as Good, Fraud, or Undetermined.
• Bulk Confirmed Marking: API must be able to mark multiple PANs as Good/Fraud/Undetermined.

The input fields will contain PAN data, therefore, a secure connection is required in order for the issuer to provide transaction data to VCAS. Additionally, when an issuer reports a marking status in VCAS as "Fraud" for a specific transaction, VCAS must automatically unbind the related Device ID + PAN.