A Worldpay chargeback happens after a cardholder's bank reverses a transaction through its own dispute process, with its own deadline, documentation requirements, and fee, separate from the fraud screening Worldpay runs before a transaction goes through. We match a chargeback notice back to the original order the moment it arrives, and route it to whoever has to respond before the deadline closes, instead of letting it surface as a surprise debit on a settlement report.
A chargeback starts with the cardholder's bank, not Worldpay. The bank reverses the charge and sends Worldpay a dispute notice carrying a numeric reason code, something like an unrecognized-transaction or merchandise-not-received code, rather than a plain-language explanation. The code itself is often the only detail a merchant gets at first, which is part of why specific codes show up in search on their own.
From there, Worldpay routes active disputes through a dedicated chargeback team, separate from its general merchant support line, and opens a window to submit evidence if the business wants to contest it: an invoice, a delivery confirmation, proof the cardholder authorized the charge. Miss that window and the reversal stands by default, regardless of how strong the evidence would have been.
Worldpay also charges a dispute processing fee when a chargeback is filed, on top of the reversed transaction amount itself, in most merchant agreements. The exact fee and whether it applies win or lose varies by account, so it's worth confirming the specifics directly with Worldpay rather than assuming a number.
The first problem is just finding the original transaction. A dispute notice carries limited detail, a reason code and an amount, and matching it back to the actual order, especially an in-person sale from weeks earlier, often means searching POS or e-commerce records by hand before anyone can even start building a response.
The second is the clock. A short response window doesn't wait for someone to notice an email sitting in a shared inbox. A missed deadline turns a disputable chargeback into an automatic loss no matter how good the evidence was.
This is a different problem from the fraud screening Worldpay's SaferPayments program runs before a transaction goes through. RiskGuardian can catch a risky transaction before it ships; it doesn't do anything once a cardholder's bank files a dispute afterward, which is exactly the gap this page covers instead.
The moment a chargeback notice comes in, it's matched to the original transaction, in-person or online, so whoever has to respond starts with the order pulled up instead of searching old batch reports for it.
Each open dispute gets a countdown and a flag to whoever owns it, so a response window doesn't quietly expire while the notice sits unread in a shared inbox.
If the honest answer is more than zero, tell us how a dispute notice currently reaches your team and we'll look at closing that gap.
A dispute you could have won on the evidence still turns into a loss if nobody responds before the window closes. Chargeback deadlines are one example of a clock a business is tracking by hand somewhere; n-frames builds the tracking and routing for whichever one is actually costing you money, Worldpay or anywhere else.
Let's talk →A Worldpay chargeback is a transaction reversal initiated by a cardholder's bank, not by Worldpay itself. Worldpay passes the dispute through to the merchant along with a reason code and a deadline to respond with evidence if the business wants to contest it.
Through the chargeback or dispute process Worldpay's merchant support directs you to, within a set window after the notice arrives. You'll typically need to submit evidence, an invoice, delivery confirmation, or proof the cardholder authorized the charge, before that window closes.
Most Worldpay merchant agreements include a dispute processing fee charged when a chargeback is filed, separate from the reversed transaction amount itself. Whether it applies regardless of outcome varies by agreement, so it's worth confirming with Worldpay directly rather than assuming a flat rate.
It's a numeric code the card network assigns to classify why a transaction was disputed, like unauthorized use or goods never received. Worldpay passes the code through largely as-is, so merchants often have to look up what a specific number means instead of getting a plain-language reason up front.
No. A fraud alert from Worldpay's RiskGuardian or SaferPayments program flags a transaction as risky before it completes, so it can be held for review. A chargeback happens afterward, initiated by the cardholder's bank, regardless of whether the transaction looked risky at the time.