Chargeback and dispute testing

What chargeback and dispute testing covers

An acquirer platform that misses a response date leaves the merchant with the debit on a sale it could have defended, and an issuer platform that files outside the time limit processes an invalid Dispute, which section 11.1.2 of the Visa Rules forbids. We test dispute flows in acquiring and POS platforms, buy now pay later and spend management products, and the software described on the chargeback management segment page. Rules below cite the Visa Core Rules and Visa Product and Service Rules of 18 April 2026, checked on 2026-09-16.

Dispute lifecycle per card network

For Visa, the stage order depends on the dispute category:

• categories 10 (Fraud) and 11 (Authorization), Table 11-1: Dispute, pre-Arbitration attempt by the acquirer, pre-Arbitration response by the issuer, Arbitration;
• categories 12 (Processing Errors) and 13 (Consumer Disputes), Table 11-2: Dispute, Dispute Response by the acquirer, pre-Arbitration attempt by the issuer, pre-Arbitration response by the acquirer, Arbitration.

Checks after each transition:

• Balances and fees. The dispute debit, the dispute fee, and the credit on a win post once each. Section 11.4.2 makes the party assigned or accepting final liability responsible for a currency conversion difference, and the ledger books it there.
• Amounts. A partial Dispute amount carries through the response, and no Dispute amount exceeds the Transaction amount, except under condition 12.2 (section 11.4.1).
• One response. Section 11.2.1 says an acquirer must not respond more than once to the original Dispute, so a retried submission job must not send a second one; API and webhook testing covers duplicate processor events.
• Closure on silence. Under section 11.2.1, when a member does not respond through Visa Resolve Online within the specified timeframe, the cycle is closed and that member is responsible for the last amount the opposing member received. The product marks the case lost and posts the final debit.
• Reversal. A member may reverse an action no later than 31 calendar days after its Processing Date, if the opposing member has not moved to the next stage and neither has accepted full or partial liability (section 11.3.3).

Other networks get stage models built from the rule edition you operate under.

Deadline and reason code rules

The checks map each processor reason string to a network condition, and each condition to its next permitted action and due date. Date tests cover:

• the Processing Date of the preceding event, which section 11.2.1 does not count as one day;
• a due date counted from the Dispute Processing Date, not from a later processor notification;
• issuer-side filing for condition 13.1, where Table 11-92 requires a wait of 15 calendar days from the listed dates, or 30 calendar days after a provider cancels for travel agencies and third-party ticket sellers, unless the wait would pass the time limit or the merchant is insolvent or bankrupt, and a filing limit of 120 calendar days from the Transaction Processing Date, or from the last expected receipt date up to 540 calendar days after the Transaction Processing Date.

Because section 11.1.2 requires issuers to extend the protections of applicable laws and regulations, consumer account checks run the error resolution timers of Regulation E and the billing error timers of Regulation Z beside the network limits. For BNPL plans whose terms pause collection during a dispute, the checks confirm that instalments and late fees stop, then resume or are refunded on the outcome.

Evidence package generation

The Dispute Management Guidelines for Visa Merchants (June 2024, checked on 2026-09-16) list a separate response for each situation under condition 13.1, from proof of delivery to a credit with its amount and date, so each branch needs its own template. The report checks per template:

• each required field comes from the order, shipping, or refund record, with dates in one time zone;
• documents are in English or carry an English translation (section 11.3.1);
• file type and size stay within your processor's documented limits;
• attachments built from cardholder data show at most the BIN and last four digits of the card number, the display limit in PCI DSS v4.0.1 requirement 3.4.1 for staff without a business need to see more;
• card-present packages from POS terminals carry the entry mode and chip data record, because the guidelines describe condition 10.1 disputes where the terminal could not read chips or full chip data did not reach Visa.

Simulated chargeback data set

Synthetic transactions and disputes cover each supported condition: full and partial amounts, a transaction currency different from the billing currency, due dates on calendar days 29, 30, and 31, month ends, and every final outcome. Spend management card programmes get issuer-side cases filed from the cardholder app before, at, and after the 13.1 waiting period. Processor sandboxes create disputes from test card numbers or amounts, and the chargeback simulation guide shows the requests.