Chargebacks and Reversals

What a reversal is

A reversal, also called a chargeback, takes back a result that was already credited. It is rare with clean traffic. Common reasons:

• Fraud, for example fake proof, multiple accounts, bots, or hidden VPN traffic.
• The result was refunded, or the offer requirements were not met after all.
• Our staff found that an approved result broke the offer rules.

How you recognize it

We do not change or delete the postback you already got. We send a new postback for the same transaction:

• {transaction_id} is the same as in the status 1 postback you credited.
• {status} is 2 and {state} is reversed.
• {reward} and {payout} are the same positive amounts as in the credit. They are never negative.
• {reason} says why, and {event_id} is new.

Credit:   tx=8f3k2a  status=1  state=credited  reward=315  payout=0.315
Reversal: tx=8f3k2a  status=2  state=reversed  reward=315  payout=0.315  reason=Duplicate accounts

What happens on our side

• The transaction is marked as reversed in our records, with the date and the reason. You see it in your dashboard under Logs, Chargebacks.
• The payout is deducted from your Sharklio balance, or offset against your next settlement.
• The user sees the offer as Reversed under Reward status on your offerwall.

What your server should do

• Take {reward} back from the user whose ID is in {user_id}.
• Do it only if you credited that transaction_id, and only once.
• If the user has already spent the reward, decide how you handle it: let the balance go below zero, or hold withdrawals until it is recovered. Make sure your own terms allow it.
• Answer with HTTP 200, even if you ignore the event, so we do not retry it.

The example handler on the Postbacks page shows the checks.

Keep reversals low

• Use a user ID that stays the same and turn link security on.
• Do not reward users for rating apps or for offers they did not complete.
• Stop accounts that complete offers faster than a person could.