Chipstars Affiliates - Refuses to pay Huffson Group for traffic and admits tracking bugs on their platform

In early 2026, Huffson Group launched a partnership with Chipstars Affiliates (Chipstars brand), bringing in three independent media buyers across different traffic sources - ASO, Facebook, and SEO. All terms were agreed upon upfront. The total earned payout came to $3,310 + €660.
Instead of paying, the advertiser first ghosted, then started introducing new requirements that never existed at campaign launch.

During the review, it emerged that Chipstars' own platform had not been used for CPA tracking for at least three months due to multiple bugs - none of which partners were informed about. The only "proof" of traffic quality the advertiser could produce was a manually edited Excel file.

Huffson Group considers the non-payment unjustified and is sharing a full timeline of events.

*** Timeline
January 2026
Partnership kicks off. Huffson onboards a partner running ASO traffic.
February 2026
Huffson brings in two more partners - Facebook and SEO.

Terms agreed with the advertiser at launch:
Test period applies.
Restricted / not accepted traffic:
Fraud, Incent­ivi­zed­/Mo­tiv­ated, Chargebacks, inactive players (min dep + 0 activity), multi-accounts, scheme traffic, disabled, self-excluded players and duplicates.
No BL
Min deps: 10 EUR/GBP/AUD/CAD/NZD

Final results: ASO - 3 FTD, FB - 1 FTD, SEO - 11 FTD.
Total payout: $3,310 + €660

One Chipstars manager leaves the chat without explanation. A second manager goes completely silent.
Huffson pauses all campaigns and attempts to re-establish contact.
Once contact resumes, Chipstars proposes a call - where they claim all traffic is “motivated”.
Huffson pushes back and requests a per-stream breakdown, since the traffic came from three entirely different teams with different sources.

March 2026
Chipstars delivers an Excel report with a set of post-hoc rejection reasons: "too small amount", "low bet count doesn't meet our expectations", "the player didn’t ask to withdraw", " traffic does not meet our usual validation criteria". None of these KPIs were part of the original agreement.

April 2026
Huffson cross-references the Excel data against Chipstars' own platform - and finds significant discrepancies in both player count and deposit volume.

Chipstars' final offer: a "one-time goodwill payment" - three times less than what their own platform shows. In doing so, they admit the platform hasn't been used for CPA tracking in 3 months, is riddled with bugs, and has been handed back to devs for fixes. None of this was disclosed before or during the campaigns.

*** Huffson Group's Position
Huffson Group fulfilled every agreed condition and is demanding full payment of $3,310 + €660, based on the following:
Unreliable evidence base. Chipstars is refusing CPA payouts citing "traffic quality issues" while simultaneously admitting their own tracking platform is broken and wasn't being used. The only thing they can put on the table is a manually edited spreadsheet. That's not a basis for rejecting a payout - that's a red flag.

Post-factum KPIs. Requirements around wager volume, session count, and deposit thresholds appeared only after traffic was delivered. At launch, there was a standard restricted list and nothing else. No additional criteria were agreed upon.

Flawed traffic evaluation. Three different sources - ASO, Facebook, and SEO - were lumped together under a single verdict: "motivated traffic". Anyone who's ever run media buying knows these sources have completely different user behavior patterns and need to be evaluated independently.

Behavior as a red flag. Huffson pulled the plug on campaigns the moment the advertiser's behavior turned suspicious — one manager quietly left the chat, another went dark. That's exactly why the final volumes are small (3, 1, and 11 FTDs). Assessing traffic quality on numbers this low is meaningless.

Huffson Group remains open to a genuine resolution, but considers Chipstars' current position manipulative and in bad faith. Moving the goalposts after delivery, using a broken platform as an argument, and systematically dodging communication are not acceptable practices - with any partner.

Chipstars Affiliates would like to clarify several points regarding this case.

First, the reporting inconsistencies mentioned by Huffson were related to a temporary backoffice display issue, not to the underlying tracking or player event data itself. During the entire cooperation period, deposit events were tracked and shared via postback integrations in real time, including with Huffson’s team directly.

Second, CPA qualification is not determined solely by the number of deposits or FTDs. As with any affiliate program, all traffic is subject to internal fraud prevention, traffic quality analysis, and player behavior validation. This includes evaluating activity patterns beyond the initial deposit event.

After detailed internal review, the traffic in question did not meet our internal CPA validation standards. This decision was based on a broader assessment of player quality and behavior, not on isolated metrics introduced “after the fact.”

At the same time, despite our position regarding CPA qualification, Chipstars offered a one-time goodwill payment covering deposited amounts in an attempt to resolve the matter fairly and avoid unnecessary escalation.

We remain open to professional communication, but we reject the implication that the decision was made arbitrarily or without supporting internal analysis.

When this payment dispute arose, we reviewed our previous conversations with your former manager and found that Chipstars had the exact same technical problems with your platform back in 2024. It is disappointing that two years later, the issue remains unresolved - and yet it is now being used as a justification for non-payment.
Describing it as a "temporary backoffice display issue" does not change the underlying fact: your own platform cannot be relied upon as a source of truth. Framing a long-standing, unresolved technical problem as a one-off display glitch looks less like an explanation and more like a convenient excuse.

We also want to draw attention to a clear discrepancy between the deposit amounts in your Excel report and the figures shown on your own tracking platform — the platform numbers are significantly higher. We have screenshots confirming this. We have no way to independently verify which figure is accurate.
* Accepting a manually edited spreadsheet as the sole basis for a payment decision is not a constructive approach, and a situation where reported figures are consistently lower than platform data, with no transparent explanation, is what the industry typically calls "shaving".

Regarding the fraud accusation: this was a test campaign, and no KPIs, baselines, or additional requirements were communicated before we began working together. You now accuse us of fraud without providing a single specific marker or criterion to support that conclusion. We understand that fraud markers are not typically disclosed publicly — that is standard industry practice.
But we would ask a straightforward question: how is it methodologically possible to assess traffic quality and label an entire stream as fraudulent when one of the flows produced just 1 FTD?
That is not analysis — that is a verdict without evidence.

The agreed terms of cooperation are documented. Your manager Lazar provided separate tracking links for each traffic source, and stated the following conditions in the same conversation: "We would just like to keep soft KPIs: Fraud Traffic, Motivated (Incentive) Traffic, Chargebacks, inactive (min dep and 0 activity), Multi, Scheme Traffic, Disable, Self-excluded and Duplicates. Is that fine?" That is the complete list of restrictions that was agreed upon — nothing more.
No volume caps were set. No KPI. No additional requirements of any kind were communicated before, during, or after the launch. The terms were clear, and we operated within them.
Test traffic is meant to be paid for. That is the entire point of a test: the advertiser evaluates the results and then decides whether to continue the partnership or not.

Finally, we want to note that the conduct of your representatives throughout this cooperation has been unprofessional. One manager left the chat without explanation, another ignored messages for extended periods, and names have been confused in correspondence. Reading through the full exchange, your responses read as copy-paste templates rather than a genuine, individual review of our specific case. That falls below the standard of professional communication in any business partnership.

I have attached screenshots showing the difference between the total deposit amount and the number of deposits on the platform and in the Excel report

We are confident that the traffic we delivered consisted of real players and we expect full payment: $3,310 + €660.

screenshots:
https:­//p­rnt.sc­/1X­Zql­dsD6Ol8

Total report
https:­//p­rnt.sc­/WI­rVQ­2O5bhtX

We would like to clarify several inaccurate assumptions being presented in this thread.

The issue referenced regarding the affiliate backoffice was related to reporting display inconsistencies, not to the underlying player tracking itself. During the cooperation period, all deposit events were tracked and shared through postback integrations in real time, including with Huffson directly.

At no point was CPA validation based solely on the affiliate backoffice interface or on a "manually edited spreadsheet", as repeatedly implied here. Internal traffic validation uses multiple data points and internal monitoring systems beyond what is visible in the affiliate panel.

Regarding the claim that “new KPIs” were introduced afterwards: CPA agreements are always subject to traffic quality review, fraud prevention checks, and internal validation standards. The restricted traffic definitions shared at launch were examples of explicitly prohibited traffic categories, not an exhaustive list of all internal evaluation methodologies.

We also reject the implication that this was a “shaving” situation. Chipstars already offered a goodwill payment covering deposited amounts despite our conclusion that the traffic did not qualify under our internal CPA validation standards.

At the same time, we acknowledge that communication during this case could have been handled better on our side, particularly regarding response delays and management transitions.

Our position regarding the traffic quality itself, however, remains unchanged.

1. The screenshots below clearly show the difference between the statistics on the Chipstars platform and the data provided in the Excel report

You can see the difference in the number of FTDs and the total deposit amount

2. Let’s be honest – Chipstars offered a payout based on the deposit amount, which in their report was around €530, although the platform clearly shows a deposit amount of €1,718

Furthermore, the number of FTDs in the report and in what they sent to our tracking system is half of what is actually on their platform.

This is direct proof that Chipstars are simply shaving off a part of the traffic.

We need to clearly reject the accusation of “shaving”.

The screenshots referenced show differences between the affiliate backoffice display and the final validation report. As already explained, the affiliate backoffice had reporting/display inconsistencies during that period and was not used as the source of truth for CPA validation.

CPA validation is not based on simply taking every number visible in the affiliate panel and treating it as payable. It is based on tracked player events, postback data, internal records, fraud prevention checks, and traffic quality review.

The goodwill amount offered was a commercial attempt to resolve the dispute fairly despite our conclusion that the traffic did not qualify for CPA payment.

We also want to clarify that differences between gross activity shown in a reporting interface and final validated CPA results do not constitute “shaving”. Shaving would imply intentionally hiding valid payable conversions. That is not the case here.

Our position remains the same: the traffic was reviewed internally, did not meet our CPA validation standards, and therefore full CPA payout cannot be approved.

Dear @Dmytro_Huffson,

The AskGamblers Complaint Team is kindly asking you to update your complaint in a timely manner and confirm if you consider the issue resolved. Please note that, in case you fail to respond within the given timeframe we will consider your case resolved and it will be closed accordingly.

Please keep in mind that as per the AGCCS Terms and Guidelines which you accepted upon registering and using our complaint system, you are obliged to provide the necessary level of assistance and cooperation during the process and providing updates in a timely manner is a must.

Thanks in advance for your cooperation.

Huffson Group — Final Statement
We have reviewed your latest response and our position remains unchanged. Below is our final summary:

1. Different sources and publishers
As we mentioned earlier, we have engaged three completely different publishers with ASO, FB, and SEO — each with different audiences, behaviour patterns, and acquisition mechanics — were dismissed under a single blanket conclusion: "motivated traffic."
Each source must be evaluated separately. Grouping them into one verdict is not analysis. It is a methodology that can justify rejecting any traffic from any partner at any time.


2. The advertiser's own data doesn't match itself.
The screenshots we provided show a clear difference between your own platform and your Excel report. All show different figures for the same traffic (FTDs, Deposit Amount). You cannot claim the backoffice had display issues while simultaneously stating that postback data was transmitted accurately in real time — these statements directly contradict each other.

3. The numbers point to shaving.
Excel figures materially lower than your own platform data, combined with partial FTD counts passed to our tracker, are not coincidental inconsistencies. That is what the industry calls shaving. Your internal validation cannot be independently verified by any third party, which makes it a convenient but insufficient basis for withholding payment.

4. The platform issue is not new — and was NEVER fixed.
We have documentation confirming the same technical issues existed in 2024. At that time, when we raised the matter, you processed our payment. Since then, nothing was fixed — yet the same unresolved issues are now being used to justify non-payment. Citing a known, long-standing bug as justification is not an explanation. It is a pattern.

5. No caps, no KPIs, no benchmarks — nothing.
The agreed terms were defined by your own manager in writing: a restricted list and nothing more. No volume caps. No KPI thresholds. No behavioral benchmarks. Nothing was communicated before, during, or after the launch. This was a test campaign with no cap on volume — test traffic is meant to be paid for. The conclusion that our traffic "did not meet CPA validation standards" is subjective and unverifiable. We do not accept it as a valid basis for refusal.

6. Some lessons in our industry cost money. Don't let ours be yours.
A partner that operates with known unresolved platform issues, applies undisclosed internal standards, and selectively processes payments depending on whether the issue is raised publicly is not a reliable partner. We encourage the affiliate community to take this into account before entering any cooperation with them. We do not recommend working with Chipstars

We demand full payment of $3,310 + €660.

Chipstars Affiliates — Final Response

We have reviewed Huffson Group’s latest statement and our position remains unchanged.

We clearly reject the allegation of shaving. The differences referenced in screenshots relate to reporting/display inconsistencies in the affiliate backoffice, not to intentional hiding of valid payable conversions.

It is important to clarify a technical misunderstanding. Postback tracking and affiliate backoffice reporting are not the same thing. Postback is a server-to-server communication where, once a tracked event such as a deposit occurs, our system sends the relevant signal directly to the partner’s tracking system. This gives affiliates direct and immediate event-level information about actions generated by their players.

The affiliate backoffice, on the other hand, is a reporting interface used to display aggregated and calculated data from our internal systems. A reporting/display issue in that interface does not mean that postback event tracking itself was not functioning.

This is why there is no contradiction in saying that postback events were transmitted while the affiliate backoffice had reporting inconsistencies.

CPA validation was not based solely on the affiliate panel or on a manually edited spreadsheet. It was based on tracked player events, postback data, internal records, fraud prevention checks, and traffic quality review.

Regarding the deposit amounts mentioned by Huffson, even if we take the higher deposit figure they reference, the average deposit value remains low in relation to the claimed CPA payout. This further supports our concern that the traffic did not demonstrate the expected commercial quality for CPA qualification.

We also reject the claim that new commercial terms or post-factum KPIs were introduced. CPA campaigns are always subject to traffic quality checks, fraud prevention, and internal validation. The restricted traffic list shared at launch does not remove the advertiser’s right to review traffic quality before approving CPA payouts.

The traffic was reviewed internally, including by source and player behavior, and our conclusion remains that it did not meet our CPA validation standards.

Despite this conclusion, Chipstars offered a one-time goodwill payment covering the verified deposited amounts in an attempt to resolve the matter fairly. This was not an admission that the claimed CPA amount was payable.

We acknowledge that communication during this case could have been handled better, especially regarding response delays and management transitions. However, this does not change the outcome of the traffic validation.

This is our final position on the matter.

Dear @Dmytro_Huffson,

The AskGamblers Complaint Team is kindly asking you to update your complaint in a timely manner and confirm if you consider the issue resolved. Please note that, in case you fail to respond within the given timeframe we will consider your case resolved and it will be closed accordingly.

Please keep in mind that as per the AGCCS Terms and Guidelines which you accepted upon registering and using our complaint system, you are obliged to provide the necessary level of assistance and cooperation during the process and providing updates in a timely manner is a must.

Thanks in advance for your cooperation.

Your response is yet another boilerplate reply. We are recording specific facts.
Regarding the back office and postback
You claim that the postback worked correctly, whilst the back office had ‘display inconsistencies’. But it is precisely the data from the back office that you rely on as one of your arguments when refusing payment. This is a logical contradiction that you have created for yourselves. If the back office is unreliable, this must be communicated before work begins; otherwise, it cannot be grounds for refusal.

Regarding internal validation criteria
There was no warning whatsoever about the existence of ‘internal validation’ — not even a mention such as ‘we are conducting an internal check’. There was none before launch, none during, and none after. The terms set out in writing by manager Lazar are exhaustive. Any requirements that arose after the test deposit and were not discussed at the outset cannot serve as a legitimate basis for refusing payment.

Regarding ‘players’ unwithdrawn balances’ as an argument
You are refusing to pay us, citing the fact that players have not withdrawn their balances. But on AskGamblers itself, there are public complaints from the players themselves who tried to withdraw their balances from your brands — and were unable to do so. You are using as an argument against us behaviour that you yourselves make impossible for the end user. This is not a valid criterion. It is a vicious circle that benefits only you.

A similar case — and this is a recurring issue
An open complaint from Spinstarz on AskGamblers. The player made three deposits: €200, €300 and €300. He won €25,000. His withdrawal request was refused. The official reason was a €1,000 withdrawal limit for streamers and affiliates. The player provided AskGamblers with screenshots confirming that this condition was introduced only after the win had been recorded and following a personal conversation with the ‘boss’, who promised to ‘look into it’. The complaint remains open.
Now our case: the manager leaves the chat without a word. The second goes silent for weeks. A conversation with the ‘boss’. Terms change after traffic delivery. Postback, Excel and the platform’s own data contradict each other; naturally, no one warns of a platform malfunction, as it is not in their interest.

Spinstarz — new terms applied retroactively after a player wins. Huffson — new KPIs applied retroactively after traffic delivery. The same mechanics and patterns. And we have focused on the cases on this resource

Our position remains unchanged. Huffson Group demands full payment and does not recommend working with Chipstars.

Chipstars Affiliates — Final Clarification

We will not comment on unrelated player cases or other disputes in this thread, as this complaint concerns Huffson Group’s affiliate traffic only.

Regarding the repeated claim of contradiction between postback tracking and the affiliate backoffice: there is no contradiction. Postback tracking refers to event-level transmission between systems, while the affiliate backoffice is a reporting interface. A reporting display issue does not automatically invalidate tracked event data, internal records, or the traffic validation process.

The affiliate backoffice was not used as the sole basis for refusing payment, nor was an Excel file the sole basis for the decision. The traffic was reviewed using tracked events, internal player records, fraud prevention checks, and traffic quality analysis.

We also reject the claim that internal validation was a newly introduced KPI. Traffic quality review and fraud prevention are standard parts of CPA approval in affiliate cooperation. A restricted traffic list does not mean that every generated deposit automatically qualifies for CPA payout regardless of player behavior.

Our position remains unchanged: after internal review, the traffic did not meet our CPA validation standards. A goodwill payment covering verified deposited amounts was offered as a commercial resolution, not as an admission that the full claimed CPA amount was payable.

This is our final response on the matter.

Dear Chipstars Affiliates,

The AskGamblers Complaint Team is kindly asking you to provide a detailed explanation of the issue along with all the relevant facts and evidence that could support your accusations towards the affiliate. Please make sure to state all the relevant terms that you believe have been breached by the affiliate, if any. Please send required information to suppor­t@a­skg­amb­ler­s.com directly.

Please note that according to the AGCCS Terms, we consider all the information presented during the course of our complaint process confidential and as such it will not be shared with third parties.

Please be in aware that in case you fail to respond and/or provide requested information within the given timeframe, the complaint will be closed as unresolved.

Thanks in advance for your cooperation.

Hello Dear AskGamblers Team,

Thank you for your message.

We are currently preparing a detailed explanation with all relevant facts and supporting evidence, and we will send it to you directly shortly.

Kind regards,
Chipstars Affiliates

Dear all,

Following a careful review and consideration of all the information, details and/or proof presented by the parties during the complaint process, the AskGamblers Complaint Team reached the conclusion that Chipstars Affiliates management acted in accordance with their Terms and Conditions.

Based on the abovementioned information, the AskGamblers Complaint Team considers this case resolved and it is now officially closed.