What happens when a dispute arrives?
It lands in the Qor Disputes console already joined to its original transaction: authorization record, verification results, receipt, and the customer's history, attached automatically. There is no hunting through exports to figure out which sale a dispute belongs to; the case file exists the moment the dispute does. Reason code and response deadline are attached, and the same data is available through the API for platforms working disputes on behalf of their merchants. Every hour your team spends assembling a case today is an hour this console spends on nothing.
Because QorPay processes directly, dispute signal arrives as the card networks' own reporting, received first-party: the raw feed most merchants only see summarized, late, or never. That's the same data feeding MID/BIN Intelligence, so every dispute outcome also sharpens the routing and health scores on the rest of your traffic. A dispute here is never just a loss; it is a lesson the platform learns on your behalf.
What is pre-dispute resolution?
The cheapest dispute is the one that never becomes a chargeback. Through integrated dispute-resolution networks (Verifi on the Visa side, Ethoca on the Mastercard side), a cardholder complaint surfaces before formal chargeback processing, and QorCommerce can resolve it in-platform: an automatic refund issued under rules you define, with the resolution recorded against the original transaction like any other ledger event.
Visa's RDR (Rapid Dispute Resolution) takes this further: qualifying disputes resolve automatically against your decision rules (amount ceilings, transaction types) with no case to work at all. What you're buying with an auto-refund is concrete: no chargeback fee, no representment labor, no angry cardholder escalating, and no losing the same dollar twice.
How does representment work when you fight?
For disputes worth contesting, the console is the workbench: upload evidence, attach it to the case, and QorCommerce packages the response in the format the network expects. The platform's advantage does the heavy lifting: most of the evidence that wins representments (authorization results, verification outcomes, delivery confirmation, prior undisputed history) is already in the ledger and already attached.
And for merchants who never want to see a case: as a managed service, QorPay drafts the representment response automatically from the correlated record, submits it, and tracks the outcome to the ledger. You set the policy (auto-fight above a threshold, auto-accept below it, review in between) and the console shows you everything either way.
Why does one console matter?
Dispute tools bolted onto someone else's processing stack work from copies: exported transactions, delayed dispute files, evidence assembled by hand. QorCommerce Disputes works from the source: the processor answering the dispute is the one that processed the transaction, holds the settlement record, and receives the network's dispute reporting first-party. One console, one ledger, no reconciliation between what your dispute tool believes and what your processor knows. Provable beats promised, here too.