Offerwall Chargebacks: Why Publishers Pay for Fraud They Never Saw

Short answer: An offerwall chargeback (or reversal) is a conversion the advertiser rejects after it was reported, usually after the publisher has already rewarded the user. On most offerwalls the publisher receives it weeks later as an unexplained deduction. A transparent chargeback is different: it points to the exact original conversion, states the reason and who made the decision, never rewrites history, and can be disputed. It is the part of the offerwall business that needs decentralization most.

If you run a GPT site, a reward app or a Telegram mini app, you know the message. "Advertiser reversal: -$312.40." No user list. No offer breakdown. No way to know which of your members did it, so no way to take the reward back from them. The users who caused it are long gone with their withdrawals. Your margin pays the bill.

This article follows a chargeback from start to finish, shows where publishers lose visibility at each step, and describes what a chargeback record should look like if the industry took transparency seriously. For the practical side of lowering your reversal rate, see our publisher's guide to reducing chargebacks.

How a chargeback travels

1. Day 0, the conversion. A user completes an offer. The advertiser's attribution system records it and sends a postback to the network. The network sends a postback to the publisher. The publisher credits the user.
2. The following days, the cashout. On most reward sites the user can withdraw within hours or days. The reward is now gone.
3. Weeks later, the review. The advertiser or its attribution partner reviews traffic quality. Fraud tools flag installs from emulators, VPNs, device farms, reused devices, or users who never engaged after installing.
4. The rejection report. The advertiser sends the network a list of rejected conversions, usually a spreadsheet keyed by click IDs or transaction IDs.
5. The deduction. The network deducts the rejected amount from the publisher's balance.

At step 5 the publisher usually sees a single line. Everything that existed at step 4 (which conversions, which users, which reasons) stays on the other side.

Five ways the process fails publishers

1. Chargebacks arrive as a total, not a list

A lump-sum deduction leaves you nothing to act on. You can't reverse a specific user's reward, can't ban the account that farmed the offer, and can't even check whether the amount is correct.

2. There is no reason attached

"Invalid traffic" covers very different things: a VPN user, a device farm, a user who installed and uninstalled, or an advertiser that overspent its budget. Without a reason per conversion, you can't fix the source.

3. History gets rewritten

In some systems the original conversion is edited or deleted when it's reversed. Your reports for last month quietly change. If the past can be edited, no report is worth anything, and you can never reconcile your logs against the network's.

4. Reversal rates stay hidden until it's too late

Offers differ enormously in how often they get reversed. If the chargeback rate per offer isn't visible before you promote it, you find out by losing money.

5. There is no dispute process

When a reversal is wrong (a duplicate, a conversion you were never paid for, an advertiser error), the only path is a support ticket. No deadline, no evidence standard, no record of the outcome.

Who actually pays

On paper the chain looks fair: the advertiser refuses to pay for fraud, the network passes that on, the publisher absorbs it. In practice the risk lands on the party with the least information.

• The advertiser has the attribution data and the fraud signals.
• The network has the click data, the payouts and the rejection report.
• The publisher has the user, and has already paid them.

A system where the party with the least information carries the most risk, and can't see the evidence, isn't a market. It's a trust arrangement.

What a transparent chargeback record contains

A reversal should be a record in its own right, detailed enough that the publisher can act on it automatically.

When every reversal carries these fields and reaches your server by postback, chargebacks stop being a monthly surprise and become a process your site runs on its own.

Where decentralization comes in

Transparency is the minimum. Decentralization makes it impossible to take back.

• Append-only records. A reversal is a new entry that references the original. Nothing is overwritten. If records are committed to a public chain as hashes, anyone can detect a later change.
• Signed claims. Each reversal is attributed to whoever made the decision, so "the advertiser rejected it" becomes a verifiable statement instead of a convenient one.
• Public reversal rates. Chargeback rates per offer and per period, computed from the same records and published for everyone.
• Dispute windows. A defined period to challenge a reversal, with the evidence and the outcome on the record.
• Escrowed budgets. When an advertiser's budget is prefunded, a reversal returns money from a known pool under known rules, instead of being clawed back from a publisher's balance after the fact.

None of this stops advertisers from rejecting fraud, and it shouldn't. Fraud is real, and a network that never reverses anything is a network advertisers leave. The point is that every reversal should be explainable, traceable, and final only once it has been open to challenge.

What AdswedMedia already does

At AdswedMedia a chargeback is a record, not a deduction. Most of the industry is still sending a monthly total.

• The original is never touched. When a conversion is reversed, AdswedMedia adds a separate reversal entry with its own date. The original conversion stays in your history exactly as it was reported.
• Every reversal reaches you individually. Chargebacks are sent to your postback URL in the same format as the conversion, with a chargeback status, plus an email. Your site can find the user by their ID and reverse the reward automatically.
• Chargeback rates are visible per offer. Each offer page shows its real chargeback rate across the network, next to conversion rate and EPC, so you can avoid high-reversal offers before they cost you.
• Fraud is stopped before payment. Duplicate devices, repeated IPs, multiple payouts to the same user, VPN and proxy traffic, and location mismatches are checked when the conversion arrives, before anyone is paid. Blocking a bad conversion up front is better for everyone than reversing it a month later.
• Reversals are settled before you're paid. Payouts run on Affiliate Pay, SwedSwap's non-custodial payment system, and each payout is linked to the exact conversions it settles. You know what was deducted before the money arrives.
• Exports for reconciliation. Full reports export to Excel so you can match them against your own records.

That is the foundation a decentralized chargeback process is built on: every reversal is a separate record tied to one conversion. The rest is making that record impossible to change.

Key takeaways

• A chargeback should be a record, not a deduction.
• The publisher carries the risk but sees the least information. That has to change.
• Reversals must reference the original conversion, give a reason and name their source.
• History must be append-only. Corrections are new entries.
• Decentralization makes transparent chargebacks permanent and verifiable by anyone.

Frequently asked questions

What is an offerwall chargeback?

An offerwall chargeback, also called a reversal, is a conversion the advertiser rejects after it was reported as complete. The payout is deducted from the publisher, usually weeks after the user was rewarded.

Why do offerwall chargebacks take so long?

Advertisers and their attribution partners review traffic quality over several weeks, looking at engagement, devices and fraud signals. Rejection reports are usually sent to the network in batches after that review.

Can a publisher dispute a chargeback?

On most offerwalls only through support. A transparent system gives each reversal a reason, a source and a dispute window, so a publisher can challenge a duplicate or an error with evidence.

How does AdswedMedia send chargebacks to publishers?

Each reversal is sent individually to the publisher's postback URL in the same format as the original conversion, with a chargeback status, and by email. The original conversion is never edited or deleted.

Does decentralization eliminate chargebacks?

No. Fraud still has to be rejected. Decentralization makes each rejection traceable, permanent and open to dispute, so publishers stop paying for decisions they can't see.