Rejected FTDs and Chargebacks: Reconcile a Streamer Campaign

Separate three kinds of exception

First, the referral may not qualify under the attribution rule. Second, the account or event may fail a contract condition. Third, an initially accepted payment or commission may be reversed later. Keep those categories separate because the evidence and remedies differ.

Arena’s published terms describe qualified-player conditions, invalid traffic and correction mechanisms. XYES describes statement adjustments. Those programme examples show why a report needs reasons; they do not supply the rules for every casino or creator contract.

Use a ledger with an audit trail

Record reporting period, controlled reference, original status, revised status, reason category, contractual basis and decision time. Keep the reporting owner and statement version visible. If aggregate reason totals are sufficient, do not collect more granular records.

Do not send player names, payment-card details, identity documents or private account histories to a creator. A privacy-safe reconciliation should let the parties check the commercial count without turning a campaign dispute into unnecessary personal-data sharing.

Reconcile an invented correction

Suppose a provisional statement lists 60 qualified acquisitions. A later review reverses four for a specified contract condition and identifies two payment reversals. The revised total is 54 if those sets do not overlap and the contract removes all six from commission.

These are hypothetical counts, not an industry rejection rate. Check whether the two payment reversals were already included among the four exclusions before subtracting. The report should preserve both versions and the actual rule, not merely replace 60 with 54 in a dashboard.

Dispute the line, not the entire relationship

Use the actual agreement’s query window and authorised contact. Identify the affected period and reason code, explain the inconsistency and request the minimum supporting clarification. Do not assume every rejected conversion is fraud or that every reversal proves tracking failed.

If a record remains under review, label it provisional. Finance can separate undisputed accepted work from contested variable commission where the agreement permits. The production team should not rewrite the creator’s delivery evidence to compensate for an unresolved settlement issue.

Feed confirmed causes back into the brief

A repeated wrong-market referral pattern may require a corrected creator brief or stopping the activity. A technical attribution defect requires a tracking repair. A legitimate exclusion must remain in force. Different causes need different actions.

Never ask a creator or player to evade verification, self-exclusion or territorial controls so an FTD becomes payable. The useful outcome is an accurate count and a corrected campaign process, not an artificially low rejection percentage.

Start with an explicit FTD definition before deciding whether a conversion was correctly rejected.