By Vanessa Reed, chargeback operations manager with 9 years of card-dispute and merchant-monitoring experience
Last reviewed: July 30, 2026
Finix creates a Dispute record when a cardholder challenges a payment, removes the disputed amount through the merchant’s settlement flow and shows a deadline for responding. A merchant that misses the displayed deadline may lose the case without its evidence being considered. This independent guide is not operated by or affiliated with Finix.
One chargeback is an account-level problem. A sustained increase can become a card-network problem capable of producing added scrutiny, fees or interrupted payment acceptance.
What is a Finix dispute?
A dispute, commonly called a chargeback, begins when a cardholder protests a transaction through the issuing bank. The issuer reverses the payment, Finix creates a Dispute resource and the corresponding amount is debited from the merchant through a settlement.
Finix then notifies the merchant in two documented ways:
- A record appears on the Dashboard’s Disputes tab.
- A webhook is sent to the configured endpoint.
The merchant can accept the dispute or challenge it with evidence. Accepting ends the contest. Challenging sends supporting material into the card-network process for review by the issuing bank.
| Finix action | Practical result |
|---|---|
| Accept dispute | Merchant stops contesting the chargeback |
| Challenge full amount | Merchant contests the complete disputed value |
| Challenge partial amount | Merchant contests only part of the value |
| Submit no response | Case may proceed without merchant evidence |
| Upload evidence | Supporting files are sent for review |
A refund is different. Once a dispute exists, Finix blocks the ordinary refund and reversal workflow for that transaction because the chargeback process already controls the challenged funds.
Where is the response deadline?
Finix displays disputes needing action by default and shows how much time remains before each response deadline. Opening an individual record reveals the dispute details and the evidence-submission workflow.
The deadline is case-specific.
Do not rely on a general statement such as “chargebacks allow 30 days.” Mastercard says network and dispute timeframes vary, with merchant response windows commonly falling between 20 and 45 days after notification. The operative date is the earlier deadline shown in the Finix case.
Prioritize the displayed respond-by date. Skip calculations based only on when the customer first contacted support.
A merchant may learn about a complaint days before the issuing bank creates the formal dispute. The card-network response clock follows the actual case, not the first angry email.
What evidence should a merchant upload?
Finix recommends evidence that directly addresses the dispute reason. Useful records may include tracking information, delivery confirmation, transaction receipts and communications with the customer.
The strongest package changes with the claim.
| Dispute claim | Evidence that may be relevant |
| Product not received | Carrier tracking and delivery confirmation |
| Service not provided | Completion records, appointments or signed acceptance |
| Unauthorized transaction | Authentication, device and buyer-account records |
| Subscription canceled | Enrollment terms and cancellation timeline |
| Refund not received | Refund record and transaction reference |
| Product not as described | Product listing, order details and communication |
| Duplicate payment | Separate order and fulfillment records for both charges |
Finix allows merchants to upload evidence and add an explanation for the issuing bank. The explanation should connect the files to the specific dispute rather than repeat a generic statement that the charge was valid.
More files are not always better.
A folder containing unrelated invoices, lengthy internal notes and several contradictory policies can weaken an otherwise clear response. Use a short index, name the customer-facing terms and identify the transaction date, delivery event and relevant communication.
Finix’s release notes confirm that receipts, shipping information and customer communications can be uploaded directly through the Dashboard for forwarding into the dispute process.
How long does a Finix dispute take?
Finix says the complete dispute process usually takes approximately two to three months. In unusual cases, it can continue for as long as six months. Accepting the dispute is the only documented way to end it sooner with certainty.
Submitting evidence does not produce an immediate decision.
The issuing bank reviews the case under the relevant network process. The merchant may see the disputed amount removed before the final outcome is known. If the decision favors the merchant, funds can be returned through the settlement flow.
That delay affects bookkeeping.
A business should not count disputed money as permanently lost on the filing date, nor should it treat a challenged amount as available revenue before the decision. Keep a separate dispute-receivable or chargeback account until the case reaches a final state.
The bank decides.
What do Finix dispute states mean?
Finix uses both an overall state and a response_state to describe the dispute lifecycle. The response state shows whether the merchant can still act, has submitted a response or has accepted the case.
Documented response values include:
NEEDS_RESPONSERESPONDEDACCEPTEDNO_RESPONSE_ALLOWEDUNKNOWN
A dispute initially appears in a pending condition while the process moves forward. The issuing bank’s final decision controls the result.
NEEDS_RESPONSE deserves immediate attention. RESPONDED means the submission was made, not that the merchant won. NO_RESPONSE_ALLOWED indicates that the current case state does not permit another merchant response.
Do not equate upload completion with victory.
How is a chargeback ratio calculated?
A dispute ratio generally compares chargebacks or combined fraud-and-dispute events with the number of processed transactions during a defined period. The exact numerator, denominator and timing depend on the card network and monitoring program.
A basic internal calculation might be:
Chargebacks during month ÷ transactions during month × 100
If a merchant received 60 chargebacks against 6,000 transactions, the simple ratio would be 1%.
This example is illustrative. A network may count cases using a different timing method, include reported fraud, separate card brands or apply other program rules.
That difference matters. Finix reports that Visa’s newer Visa Acquirer Monitoring Program combines fraud and dispute measurements rather than relying solely on a merchant’s simple chargeback count.
Use internal ratios for early warning. Use the processor or network measurement for compliance decisions.
What is Visa VAMP?
Visa introduced the Visa Acquirer Monitoring Program as a unified framework for monitoring fraud and disputes across merchants and acquirers. The program replaced separate legacy monitoring approaches and evaluates combined fraud and dispute activity against card-not-present transactions.
Finix’s July 2026 materials state that the excessive-merchant threshold for the United States, Canada, the European Union and Asia-Pacific tightened from 2.2% to 1.5% in April 2026. Finix also reports an $8-per-transaction assessment after the applicable threshold is breached, with no warning tier under the described structure.
Those figures concern VAMP as described by Finix for the relevant markets and period. They should not be applied blindly to every transaction type, country or merchant category.
Visa’s own updates emphasize that VAMP measures the broader fraud-and-dispute environment and that merchants should focus on preventing problematic transactions rather than attempting to adjust only the ratio after entry into monitoring.
Act before 1.5%.
What does Mastercard monitor?
Mastercard operates an Excessive Chargeback Program and an Excessive Fraud Merchant program within its compliance framework.
Finix’s earlier chargeback-monitoring guidance described Mastercard’s entry-level excessive-chargeback threshold as beginning at 1.5% or 100 chargebacks in a month, with assessments beginning after continued program exposure. Those figures came from Finix material published in 2022, so merchants should verify current Mastercard terms through their processor before treating them as 2026 contract rules.
This is a useful example of why old chargeback articles are risky.
Program names, thresholds, calculations and assessment schedules change. The merchant should use Finix’s current risk communications and Mastercard’s current compliance materials rather than copying a number from an undated support blog.
The stable fact is narrower: Mastercard continues to maintain formal excessive-chargeback and excessive-fraud programs.
How can merchants monitor disputes inside Finix?
Finix offers a Chargeback Merchant (Historical) report. The report contains chargeback-related metrics and sorts merchants with higher dispute activity during the latest 30-day period near the top for exception and risk management.
That report is particularly useful to software platforms managing many sellers.
A platform should review:
- Disputes by merchant
- Chargebacks by card brand
- Ratio trend over several months
- Fraud versus service-related reasons
- Response deadlines missed
- Win rate by reason code
- Refunds issued before disputes
- Sellers with sudden volume changes
The highest raw chargeback count may not be the riskiest seller. A large merchant can have 80 disputes and a low rate, while a small merchant with 20 disputes may have a severe percentage.
Track count and ratio.
Finix says excessive dispute levels can cause card-network monitoring and eventual loss of processing access.
What lowers the dispute rate?
Finix recommends prevention measures such as recognizable billing descriptors, clear return policies, delivery confirmation and proactive customer communication.
The fastest operational improvements usually occur before the chargeback:
- Use a statement descriptor customers recognize.
- Send a receipt immediately after payment.
- Display renewal and cancellation terms before enrollment.
- Respond to refund requests before buyers contact their banks.
- Preserve proof of delivery or completed service.
- Stop repeated attempts after issuer declines.
- Review merchants with rising dispute activity weekly.
Fraud controls matter too. Finix says its current processing offering includes integrated fraud monitoring intended to identify risky transactions before they develop into disputes.
Fraud screening will not prevent a customer from disputing poor service, confusing billing or an ignored cancellation. Operations and risk tools need to work together.
Finix chargeback FAQ
Can I refund a disputed Finix payment?
No. Use the dispute workflow.
How long do I have to respond?
Use the deadline shown on the Finix Dispute record. Network timeframes vary, and general Mastercard guidance describes windows commonly ranging from 20 to 45 days.
How long does the decision take?
Finix says most disputes take two to three months, with rare cases lasting up to six months.
What does RESPONDED mean?
It means the merchant submitted a response. It does not mean the issuing bank ruled for the merchant.
Does Finix provide a chargeback report?
Yes. The Chargeback Merchant report includes merchant-level metrics and prioritizes sellers with greater recent dispute activity.
What is the current Visa monitoring threshold?
Finix’s July 2026 material states that the VAMP excessive-merchant threshold became 1.5% in April 2026 for the United States and several other regions. The exact network calculation should be confirmed for the merchant’s account and transaction mix.
Can excessive disputes shut down Finix processing?
They can put payment acceptance at risk. Finix and Mastercard both warn that excessive chargeback activity may trigger network scrutiny and possible disruption of processing access.
Review Finix’s respond-by queue every business day, measure chargebacks against transaction count by card brand and investigate sellers before they approach a network threshold. Once a merchant enters monitoring, evidence submissions alone will not repair the underlying ratio.