Visa

Contents

Overview

Visa is a trusted world leader in digital payment technology.  It facilitates the transfer of funds electronically via debit cards, credit cards and prepaid cards.  Consumers trust the Visa brand, in part, thanks to their Zero Liabilty Policy that guarantees you won't be held responsible for unauthorized charges.  Issuers choose visa to help make everyday transactions more convenent, reliable and secure.

In addition to Visa's Zero Liability Policy, they have a strict set of rules that issuers must follow.  These rules cover every aspect of payment processing, including claims.  Visa constantly revises their rules through a process referred to as "mandates".  These new rules are implemented twice per year, in April and October.  

QFD provides complete support for processing Visa claims, including direct connections to Visa's Real-Time Systems Interface (RTSI).  This interface allows QFD to automatically process most actions related to consumer claims.  Additionally, our team of experts keeps QFD up-to-date with all the latest rules mandated by Visa to ensure that our clients are compliant and efficient in their claim processing.

See the sections below for more details about how QFD streamlines and automates the Visa claim process.

Configuration

QFD includes various options for customizing the behavior of the application.  The following settings are applicable to Visa claims.

Initial Interaction

Initial Interaction options are available for applying automation to a claim at the time of initial contact with the accountholder.  This includes settings for automatic issue of provisional credit, as well as automatically issuing final credit.  These settings can be customized, based on transaction type.

AutoPay

AutoPay can be enabled to automatically pay a claim during the initial interaction with the accountholder.  This feature allows you to establish a dollar threshold for claims that should be automatically granted provisional or final credit.  When the amount of the claim is below the defined threshold, and does not meet any specific exclusion criteria, a credit is issued and communicated to the accountholder immediately.  This frees up users to spend more time on claims with higher loss potential and improves the customer experiencing by streamlining the process and providing a quick resolution to their issue.

Setting NameSetting DescriptionAdvanced Options
AutoPay ThresholdUpon submission, automatically pay claims that are less than or equal to X dollars AND all disputed transactions are less than X dollars.Split thresholds for fraud and non-fraud.
Auto-PC ThresholdUpon submission, automatically grant provisional credit to claims that are less than or equal to X dollars.Split thresholds for fraud and non-fraud.
Auto-PC Non-RegulatoryGrant provisional credit on non-regulatory disputes?

Exclusions

By default, QFD will not automatically pay or grant provisional credit for:

  • ATM Missing Deposit claims
  • Accounts opened in the last 60 days (if this information is made available to QFD)
  • Claims containing manual (user-entered) transactions
  • Claims containing an aged transaction (120 days or more old)

The following settings are available for customizing exclusion criteria.

Setting NameOptions
Potential Claim AbuseX claims have been filed in the last X days.  Pend these items for Fraud Review instead of Provisional Credit Review?
Suspicious VelocityMore than X claims opened within 24 hours.
Previous Denial    One, or more, disputes on the current or another claim by the same customer/member was previously denied.
New AccountA new account has been opened with the same customer/member within X days of the contact date.
Early TransactionsA disputed transaction occurred within X days of the account opening.
Documents RequiredOne or more disputes require documentation.
Non-Protected Claims AutoPayExclude Non Reg protected claims from AutoPay and Auto-PC automation?  This includes claims that are not protected by regulation, based on Regulatory Settings.
Account TakeoverExclude Account Takeover (ATO) claims from AutoPay and Auto-PC automation?
Proprietary ATMExclude Proprietary ATM claims from AutoPay and Auto-PC automation?

Provisional Credit

If provisional credit was not automatically granted as as result of the Initial Interaction settings above, the following options apply.

Setting NameSetting Description
Provisional Credit Review

When Provisional Credit is not automatically granted as as result of the Initial Interaction settings, do one of the following:

  • Require user review for all claims to determine if Provisional Credit should be issued
  • Require user review for regulatory-bound claims only to determine if Provisional Credit should be issued
  • Skip and proceed to Recovery
Post Reg E 10 Provisional Credit Review

When the deadline to grant provisional credit on a claim covered by Regulation E has expired and provisional credit is automatically issued by the system, do one of the following:

  • Proceed to Recovery
  • Remain in Provisional Credit Review to require user review

QFD provides the ability to enable approval thresholds for important decisions made by users.  Thresholds can be established to trigger the approval requirement, where applicable.  When enabled, and the claim or dispute meets the criteria for approval, an assignment is created to prompt manager review.  For more information, see Approvals.

Approval Settings

Setting NameDescriptionRead Only?
Write Off ApprovalRequire approval if the amount of the dispute is greater than X dollars or the amount of the claim is greater than Y dollars
Deny ApprovalRequire approval if the amount to be denied is greater than X dollars or the amount of the claim is greater than Y dollars
Deny Approval ExclusionsExclude specific denial reasons, such as Merchant Credit or Withdrawn, from requiring approval.  Only applicable when Deny Approval is enabled.
Provisional Credit ApprovalRequire approval if the amount of the claim is greater than X dollars.
Letter ApprovalRequire approval for specific letters.

Denial Configuration

The following settings allow customization of available deny reasons and justifications.  These settings determine what correspondence is sent to the accountholder.  For more information about the denial process, see Denied.

Setting NameDescriptionRead Only?
Deny ReasonsLists available deny reasons and their applicability to Claim types.  Some reasons can be disabled so that they are not available for use.Yes
Denial Commentary Require commentary when a user denies one, or more, disputes?Yes
Deny Justifications

When enabled, deny justifications can be configured to require users to select one, or more, specific justifications for a "No Error" deny decision.  These justifications are fully configurable by transaction type and fraud/non-fraud and allow the user to provide additional context to the accountholder via the resolution letter.  The following "applicable to" options are supported:

  • Fraud
  • Non-Fraud
  • Always
  • ACH
  • ACH Fraud
  • ACH Non-Fraud
  • ATM
  • ATM-Fraud
  • ATM Non-Fraud
  • Balance Transfer
  • Convenience Check
  • Credit Card
  • Credit Card Fraud
  • Credit Card Non-Fraud
  • Debit Card
  • Debit Card Fraud
  • Debit Card Non-Fraud

DPS

QFD includes full support for the DPS version of the Real-Time Systems Interface (RTSI).

Setting DescriptionRead Only?Ticket Required?
DPSUse DPS version of RTSI?
Yes
Stop Payment DurationSpecify the number of months stop payments are applied when Visa Stop Payment Service (VSPS) is enabled.
Yes
Commercial Card Virtual AccountIssues Visa Commercial Card Virtual Account?
Yes
Fraud Report DeletionDelete Fraud Report on denial?
Yes

Fraud Reporting Options

QFD includes full support for automated fraud reporting via the Real-Time Systems Interface (RTSI).  The following options are available for customization of this feature.

Setting DescriptionRead Only?Ticket Required?
Fraud Report DeletionDelete Fraud Report on denial?
Yes

Stop Payment Service

QFD includes full support for the Visa Stop Payment Service (VSPS).

Setting DescriptionRead Only?Ticket Required?
Visa Stop Payment Service (VSPS)Enable VSPS?
Yes
Stop Payment TypeSpecify Merchant or Pan stop payment usage.
Yes
Stop Payment DurationSpecify the number of months stop payments are applied.
Yes

For additional configuration settings that are not specific to Visa, see Configuration.

Supported Functions

Collect

The collect stage is generally referred to as “intake”. This is where the case is created and information is collected from the claimant in order to provide all the details that are necessary to investigate the claim. Rules are evaluated as the user navigates through the collection process so that content is based on the context of the case.  This is invisible to the user and developed in such a way that the user need not understand the underlying rules or have detailed knowledge of the claims process.  To see the process in action, check out a short video demonstration.

Dispute Reasons & Supported Transactions

The following dispute reasons are applicable.

Which of the following best describes the reason for your dispute?

Selection

Claim Reason

Questionnaire

I was charged for something more than once.

Charged More Than Once

Visa Charged More Than Once

I haven't received merchandise or a service I purchased.

Merchandise/Service Not Provided

Visa Merchandise or Service Not Received

I cancelled or returned merchandise or services and did not receive the expected credit.

Cancelled/Returned Merchandise/Service

Visa Cancelled or Returned Merchandise or Service

I continue to be charged for a recurring transaction after I cancelled.

Cancelled Recurring

Visa Cancelled Recurring

I am dissatisfied with merchandise or a service I received.

Merchandise or Service Issue

Visa Merchandise or Service Issue

I was charged or credited incorrectly.

Charged or Credited Incorrectly

Visa Charged or Credited Incorrectly

See Dispute Reason or Dispute Transactions for more details about these steps.

Required Documentation

Dispute Category

Claim Reason

Required Document

Additional Criteria

Fraud

Fraud Application

Statement of Fraud Application

Claim Reason = Fraud Application

Processing Error

Paid by Other Means

Proof of Payment

Required when the other form of payment is not a card issued by the same issuer as the transaction being disputed.

Processing Error

Incorrect

Document detailing the correct transaction amount

"I was charged the wrong amount" must be selected

Consumer Dispute

Merchandise/Services Not Received

Statement of Dispute

3 or more Merchandise/Services Not Received disputes on same account, at same merchant, within a 30-day period

Consumer Dispute

Merchandise/Services Not Received

Evidence that the non-fiat currency or non-fungible token(s) was not successfully delivered to the destination wallet address at the time of the Transaction.

“Yes” to “Was non-fiat currency (e.g. cryptocurrency) or non-fungible token(s) not successfully delivered to the destination wallet address supplied by the Cardholder at the time of the Transaction?”

Consumer Dispute

Credit Not Processed

Copy of Credit Transaction Receipt or Voided Transaction Receipt

A Credit Transaction Receipt or Voided Transaction Receipt was issued.

Consumer Dispute

ATM Withdrawal

Statement of Dispute

3 or more ATM disputes on same account, at same ATM, within a 30-day period (does not apply to proprietary ATM transactions)

For more information, see Document Requirements.

Enhance

The Enhance stage is the first fulfillment ("back-office") stage and provides steps for collecting additional information that is needed to support the investigation and processing of the claim.  The information that was gathered in the Collect stage is stored so it can be viewed later.  Once this happens, the system completes the initialization process and transmits the confirmation letter.  Typically, this will happen within seconds, well before a fulfillment user ever opens a claim.  The following steps are executed, where applicable, usually automatically.

For more information, see Enhance.

Authorizations

QFD supports the ability to include pending transactions in a claim.  When pending transactions are included in a claim, QFD will check for new postings every 6 hours.  When new postings are available, QFD will evaluate them and attempt to make an automatic match.

For more information, see Authorizations.

Enrichment

When available, QFD will retrieve additional details about a disputed transaction from the system of record.

For more information, see Enrichment.

Analyze

The Analyze stage is where decisions are made.  This is where back-office users will spend the majority of their time reviewing case details and making decisions that have not already been automated by QFD.  The following steps are executed, where applicable. 

For more information, see Analyze.

Collaboration

QFD supports collaboration with card merchants via Ethoca and Verifi networks.  These integrations allow issuers to attempt recovery from the merchant before initiating a chargeback with the card association.  Merchant collaboration currently only supports card transactions.

For more information, see Collaboration.

Merchant Credits

QFD provides automated merchant credit check algorithms to support quick and automatic dispute resolution.  This feature is available for ACH, BillPay, Card, and Zelle transactions.

For more information, see Merchant Credits.

Provisional Credit

Excerpt lookup error: excerpt "Description" was not found on page "provisional credit" (with ID 348160022) in space "QEK".

If you're experiencing issues please see our Troubleshooting Guide.

For more information, see Investigation.

Investigation

QFD includes various options for automating a reasonable investigation, as well as helping to facilitate investigations performed by a user.

For more information, see Research.

Fees

QFD automatically associates fees with claims and refunds any fees that were caused by disputed transactions.  Various options are available for configuring which fees QFD should refund.

For more information, see Fees.

Interest

QFD can be configured to automatically calculate and refund interest associated with disputed transactions.  Users can also use the Interest Calculator to manually calculate interest and generate a refund.

For more details, see Interest Calculation

Disposition

The Disposition step is where a determination is made about how the dispute will be resolved.  If automated recovery is enabled and the dispute has not been reasserted, the system will attempt to automatically apply a recovery option and execute Recovery.  Otherwise, a user will be prompted to determine the best recovery option.  If no recovery options are available, the Final Investigation Flow flow is executed.  Various options are available for applying automated decisioning at this step to reduce overhead.

For more details, see Disposition.

Responses

Macro lookup error: excerpt "Description" was not found on page "Responses" (with ID 340893101) in space "QEK".

If you're experiencing issues please see our Troubleshooting Guide.

For more details, see Responses.

Approvals

This optional extension provides added control in your fulfillment process by requiring an escalated review of key, manual decision points.  Approvals can be enabled, with configurable thresholds, for the following user decisions: Deny, Provisional Credit, and Write Off.  When an approval flow is enabled, the decision that requires approval is suspended until a manager completes the review assignment.  The manager can approve the decision and the flow resumes, or they can decline the decision, provide an explanation, and the flow returns to the previous decision assignment.

For more details, see Approvals.

Execute

The Execute stage is where processing and maintenance happens. When information collected in Collect and Enhance or decisions made in Analyze trigger new processing or maintenance requirements, flows are executed in Execute and assignments are generated to get the work done.  All Execute tasks can be automated by QFD.  The following steps are executed, where applicable. 

For more details, see Execute.

Recovery

The recovery process is built around recovery strategies and recovery options.  A recovery option is a specific method that is available for recovering funds for a specific transaction type and dispute scenario.  A recovery strategy is a group of related recovery options.  For example, Visa Fraud is a recovery strategy and includes a recovery option that aligns to each of the fraud reason codes that Visa provides for issuer chargebacks.  A single dispute may have recovery rights under more than one recovery option, but it's unlikely that more than one recovery strategy would apply to a single claim.  The system will automatically evaluate dispute details to determine which recovery strategy and, within that strategy, which recovery option is most appropriate.  In some cases, a user may be required to determine an appropriate recovery option or review then one selected by the system.  

The following recovery options are available for Visa.

Allocation

Visa Allocation includes the following Fraud and Authorization recovery options.  Recovery options may be automatically selected and executed by the system, when enabled.  In some cases, primarily fraud and authorization disputes, recovery options are set based on a number of validations to determine if chargeback rights exists.  Any applicable validation rules are documented in each recovery option. 


Authorization

Card Recovery Bulletin or Exception File 11.1

Declined Authorization 11.2

No Authorization/Late Presentment 11.3

Fraud

EMV Liability Shift Counterfeit Fraud 10.1

EMV Liability Shift Non Counterfeit Fraud 10.2

Other Fraud – Card Present Environment (10.3)

Other Fraud – Card Absent Environment (10.4)

Visa Fraud Monitoring Program 10.5

Collaboration 

Visa Collaboration includes the following Consumer Dispute and Processing Error recovery options.   Recovery options may be automatically selected and executed by the system, when enabled.  For consumer disputes or processing errors, recovery options are typically set based on certain claim attributes.  This logic is defined in Visa Recovery Option Settings.


Consumer Disputes

Services Not Provided or Merchandise Not Received 13.1

Cancelled Recurring Transaction 13.2

Not as Described or Defective Merchandise or Services 13.3

Counterfeit Merchandise 13.4

Misrepresentation 13.5

Credit Not Processed 13.6

Cancelled Merchandise or Services 13.7

Original Credit Transaction Not Accepted 13.8

Non Receipt of Cash or Load Transaction Value at ATM 13.9


Processing Errors

Late Presentment 12.1

Incorrect Transaction Code 12.2

Incorrect Currency 12.3

Incorrect Transaction Account Number 12.4

Incorrect Transaction Amount 12.5

Duplicate Processing or Paid by Other Means 12.6

Invalid Data 12.7


For more details, see Recovery.

Accounting

QFD performs general accounting operations required for claims processing. The system can be integrated with most real-time accounting service interfaces or support batch accounting file generation and delivery. When no services are available, these operations are performed by a user.  Specific accounting rules can be configured for each transaction type and adjustment type to ensure all accountholder and GL to GL accounting needs are supported.  Additionally, QFD performs account balancing to ensure that all require accounting is performed on-time.

For more details, see Accounting.

Account Maintenance

When any type of maintenance is required, such as account blocks or stand-in file listing, these tasks are executed in the Account Maintenance step.  All maintenance tasks can be automated by QFD.

There are no Account Maintenance tasks that are specific to Visa .

For more details, see Account Maintenance.

Fraud Reporting

For most card networks, fraud reporting must be completed before a fraud chargeback can be submitted.  The system facilitates automatic fraud reporting via direct integration with popular card networks.  This step is only applicable to credit and debit card claims.

For more details, see Fraud Reporting.

Notifications

QFD includes pre-defined correspondence for all supported claim functions and supports multiple channels for correspondence with customers.  Each channel uses a formatting template that simplifies the design process by applying the template to all communications in that channel and allowing the content to be managed independently of branding.  Content rules determine what is included in each letter, regardless of channel (though some content is channel-aware).  Notifications are automatically generated, based on regulatory requirements and configurable settings.

The following letters are all applicable to Visa disputes.

For more details, see Correspondence

Resolve

The Resolve stage is the final stage in the fulfillment process. When a dispute is paid or denied, it enters this flow and triggers final resolution activities.

For more details, see Resolve.

Paid

A dispute is paid when the accountholder's claim is found to be valid.  In many cases, claims and disputes are automatically paid by QFD.  A claim or dispute can be resolved as 'Paid' via the following methods:

  • A user determines that the claim or dispute is valid and decides to issue a final credit  (Manual)
  • The claim meets the requirements defined for AutoPay  (Automatic)
  • A dispute is fully recovered  (Automatic)
  • No final decision has been made and an applicable regulatory resolution date is reached  (Automatic)

When a pay decision is made, by a user or the system, a Paid letter is generated and any accounting adjustments are executed by QFD.

For more details, see Paid.

Denied

Denying a dispute can be achieved via several different methods within QFD, depending on where the dispute is at in the case lifecycle.  Most commonly, this will happen in Final Investigation or during a review assignment in Recovery.  This action triggers several systematic checks and balances to ensure that all required resolution activities are complete, such as customer notification and accounting.

The following deny reasons are applicable to Visa disputes.  Some deny reasons can be disabled via Config.

For more details, see Denied.