[UNPAID COMMISSION + ANTI-FRAUD RETALIATION] BigBettyPartners / Bino.bet — €1,000 withheld after 5 confirmed FTDs

[slotmasters1k]

Ref: SM1K-BIGBETTY-20260605
Affiliate: SlotMasters1K (slotmasters1k.net)
Program: BigBettyPartners — Brand: Bino.bet
Manager: Stacy
Amount: €1,000.00 (5 FTDs × €200 CPA)
Status: Unpaid. No resolution after 26 days.

---

**THE DEAL**

Agreed May 21, 2026 with manager Stacy via Telegram. Terms confirmed in writing:
• Traffic source: SEO site (slotmasters1k.net)
• GEO: ES only
• Deal: €200 CPA + 30% RS
• Payment threshold: 5 FTDs
• Brand: Bino.bet — Campaign ID: 478618

All terms were met without exception.

---

**RESULTS — CONFIRMED BY BIGBETTYPARTNERS' OWN PANEL**

• Visits: 16
• Registrations: 5
• FTDs: 5 (100% reg-to-FTD conversion)
• FTD sum: €190.81
• Total deposits: 8 (players returned to deposit)
• Deposits sum: €303.74
• Cashouts: €1,097.92
• Casino NGR: −€904.05
• Partner income shown in panel: €1,000.00

The €1,000 Partner Income figure is BigBettyPartners' own calculation in their own system. The payment threshold was met in full.

---

**THE SEQUENCE — READ THIS CAREFULLY**

→ May 21: Deal agreed. Tracking link provided. Campaign live.
→ May 21–24: 5 FTDs delivered in just 4 days. Payment threshold reached in full.
→ May 25: Just 4 days in — AFTER threshold met — BigBettyPartners requests immediate traffic pause citing low ROAS and negative NGR. We comply and halt all activity.
→ May 30: We request payment instructions. Stacy confirms NET25 terms and start-of-month reconciliation. Zero mention of any fraud investigation.
→ June 5: For the FIRST TIME — 15 days after FTDs were delivered — Stacy mentions sending traffic to anti-fraud team.
→ June 5: We issue formal dispute document (SM1K-BIGBETTY-20260605) with deadline of June 9.
→ June 9: Deadline passed. No report. No evidence. No payment.
→ June 16 (today): 26 days since FTDs delivered. 11 days since our formal deadline. Still no payment, no evidence, no timeline.

They paused the traffic after just 4 days — the exact moment the payment threshold was hit — and only raised fraud concerns 15 days later when payment was requested. This is not a coincidence. This is a pattern.

---

**WE FORMALLY REQUESTED SPECIFIC TECHNICAL EVIDENCE. NONE WAS PROVIDED.**

Throughout this dispute we explicitly requested:
• IP analysis of the 5 FTDs
• Device fingerprinting results
• List of flagged FTDs with deposit IDs
• Specific fraud methodology used by their anti-fraud team
• The contractual clause suspending an already-triggered payment
• A defined timeline for the investigation

In 26 days, BigBettyPartners has not provided a single specific technical data point. Not one IP. Not one device flag. Not one deposit ID. Their "evidence" consists entirely of negative NGR, low average deposits, and same-day activity — standard behavioral patterns for cold organic SEO traffic, not fraud indicators.

---

**THEIR ARGUMENTS — AND WHY THEY FAIL**

✔ "Negative NGR" — Players won. Operator variance under a CPA model. Not affiliate liability.

✔ "Low average deposits / same-day activity" — Standard behavior for first-exposure SEO users. BigBettyPartners publicly markets itself as a program working with SEO affiliates and boasting Reg2Dep rates up to 70%. Our 100% reg-to-FTD conversion is exactly what quality SEO traffic looks like.

✔ "Clause 5.1 T&C / 180-day hold" — Requires a suspected breach by the affiliate. No specific breach has been identified or communicated in 26 days. Clause 5.1 is not a blank 180-day shield to avoid paying earned CPA commissions.

✔ "You used AI" — Stated as grounds for dismissing our formal dispute. Facts do not change based on the tool used to articulate them.

✔ "You didn't wait for the report" — We waited 26 days. No timeline was ever given for when the report would arrive. An investigation with no deadline is not a valid mechanism to indefinitely defer an earned payment.

---

**WHAT WE ARE ASKING**

1. Immediate payment of €1,000.00 — triggered, confirmed in their own panel, owed
2. Specific technical fraud evidence if it exists
3. A defined investigation timeline
4. Or written confirmation that no evidence exists and payment will proceed

---

**NOTE FOR AGD MODERATORS**

BigBettyPartners holds CERTIFIED status on this forum. AGD's certification explicitly requires timely payment and non-predatory terms.

What happened here:
• Traffic paused after 4 days — the exact moment the CPA threshold was met
• Fraud investigation opened only when payment was requested, 15 days later
• 26 days elapsed with zero specific technical evidence provided
• Formal requests for IP data, fingerprints and deposit IDs completely ignored
• Clause 5.1 invoked as a blanket 180-day payment shield with no evidentiary basis
• Formal deadline of June 9 passed with no substantive response

This is a textbook case of using anti-fraud procedures as a payment avoidance mechanism. If this conduct is compatible with CERTIFIED status, every affiliate working with BigBettyPartners on CPA deals should know it.

Full evidence available: panel data export (May 1–June 1, 2026), panel screenshot, complete Telegram conversation with timestamps, formal dispute document SM1K-BIGBETTY-20260605, T&C clause 5.1 screenshot, agreed deal terms.

SlotMasters1K — slotmasters1k.net
Ref: SM1K-BIGBETTY-20260605

 

[Alkis]

So you want to get paid 1k for 303 deposits? You didn't know you traffic doesn't worth 200 CPA? I agree that NGR has nothing to do with CPA tho.

 

[MissExposé]

Hello @slotmasters1k please note that your complaint has been sent to Big Betty representatives and you will be informed here with the feedback from them.

 

[slotmasters1k]

**UPDATE — June 16, 2026**

BigBettyPartners has now shared their anti-fraud report (SEON). We are posting the full technical analysis here for the record.

---

**SEON RESULTS — PROVIDED BY BIGBETTYPARTNERS**

· Player 6727068 — REVIEW (score 11) — NordVPN detected, email_hits 725
· Player 6722857 — APPROVE (score 1)
· Player 6735181 — APPROVE (score 5)
· Player 6727621 — APPROVE (score 2)
· Player 6728115 — APPROVE (score 1)

Their own fraud tool approved 4 out of 5 players. BigBettyPartners offered to pay for 1.

---

**THE "SHARED IP" ISSUE — IT'S THEIR OWN SERVER**

All 5 players share IP 3.123.197.135, flagged as GEO: DE. This IP belongs to PacketHub S.A. — a German datacenter. This is BigBettyPartners' own tracking/postback infrastructure appearing in session data. It is not players sharing devices or connections.

The "non_ES_geo" flag on 3 players is caused by their own server. Not by the traffic source.

---

**THE ISPs CONFIRM SPANISH TRAFFIC**

· Xtra Telecom S.A. — Spanish ISP
· Orange Espagne SA — Spanish ISP
· Euskaltel S.A. — Spanish ISP
· Telefonica de Espana SAU — Spanish ISP

4 out of 5 players connected through Spanish ISPs. The traffic is from Spain, as agreed.

---

**THEIR RESPONSE TO OUR TECHNICAL ANALYSIS**

When we pointed out that SEON approved 4 players, BigBettyPartners responded that "SEON approval is not payment approval" and referenced "additional internal data and risk indicators" — but provided no specific data when formally requested.

When we identified the shared IP as their own server, there was no technical rebuttal.

---

**CURRENT STATUS**

We have accepted removing player 6727068 from the claim (VPN flag noted). Our claim stands for the remaining 4 players: all SEON APPROVE, all Spanish ISPs, zero specific fraud evidence presented.

Amount claimed: €800 (4 × €200 CPA)

BigBettyPartners has stated they are preparing a response on this forum. We welcome that and look forward to seeing their technical evidence presented publicly.

SlotMasters1K — slotmasters1k.net
Ref: SM1K-BIGBETTY-20260605

 

[slotmasters1k]

Hello @slotmasters1k please note that your complaint has been sent to Big Betty representatives and you will be informed here with the feedback from them.

Hi, thank you very much.

 

[Big Betty Partners]

Dear partner @slotmasters1k and the Affiliate Guard Dog community,

We would like to provide the full context of this case to ensure all parties have a clear and accurate understanding of the situation.

Timeline of events:​

1. Initial traffic quality concerns (May 25)
Our Affiliate Manager informed the partner that the traffic being delivered showed signs of low quality. The partner acknowledged this concern and agreed to monitor the traffic further.

Additionally, our Affiliate Manager explicitly informed the partner that low-quality traffic is not eligible for payment under the terms of cooperation, and the partner directly agreed to these conditions. Furthermore, this is clearly stated in our Terms & Conditions, where it is specified that low-quality traffic is not subject to payment.

2. Additional fraud concerns raised (June 2)
On June 2, our Affiliate Manager once again notified the partner that the traffic continued to demonstrate low-quality patterns and unusual player behavior. Based on these signals, traffic was paused and sent for a fraud investigation.

3. Partner request for verification report
On the same day, the partner requested to receive the investigation report once the review was completed.

4. Complaint threat before investigation completion (June 9)
On June 9, before the investigation had been finalized, the partner informed our Affiliate Manager that a public complaint would be submitted within 30 minutes unless documentation was provided immediately.
We would like to note that this approach did not indicate a willingness to resolve the matter through normal communication channels.

5. Compliance with agreed review procedures
On the same day, our Affiliate Manager explained that there is an internal procedure and established timeline for reviewing traffic quality. The partner confirmed that they were familiar with our Terms & Conditions and understood the situation regarding low-quality traffic.

In particular, Clause 5.1 of our Terms & Conditions clearly states that in the event of suspected violations, including low-quality or potentially fraudulent traffic, the affiliate program has the right to suspend cooperation and conduct a review and investigation for a period of up to 180 days.

Therefore, the partner’s actions in publishing this case before the completion of the agreed review procedure directly contradict the accepted cooperation terms and, from our side, are considered an attempt at manipulative pressure rather than a constructive resolution of the dispute.

6. Investigation results delivered (June 15)
On June 15, the Affiliate Manager provided the partner with the final investigation report. Following a full review, it was confirmed that:

• 1 player was qualified as valid traffic
• 4 players were identified as low-quality / invalid traffic

Important clarification regarding SEON data:​

As already explained in private communication, SEON approval does not automatically equal payment approval.

Based on the SEON verification, it was determined that 4 out of 5 players had a significant Email Fraud Hits history, specifically:

• 725 fraud hits
• 64 fraud hits
• 58 fraud hits
• 26 fraud hits

Only one player had this metric within the acceptable range and was therefore recognized as valid.

SEON is only one of many verification tools we use. However, even its data confirmed the presence of significant fraud-risk signals across the majority of the submitted traffic.

Summary:​

1. The partner acknowledged the traffic quality concerns from the very beginning, reviewed the Terms & Conditions, and confirmed acceptance of them.
2. The partner was informed in advance that the submitted traffic would be sent for additional review.
3. The partner received the full report with the results of the completed investigation.
4. A public complaint was announced before the completion of the agreed review process, which under Clause 5.1 of the Terms & Conditions may take up to 180 days.
5. The final decision was made in accordance with the Terms & Conditions accepted by the partner and based on a multi-layer fraud assessment and a comprehensive traffic quality review.

Final decision:​

Big Betty Partners is committed to fair, transparent, and long-term cooperation with all partners. At the same time, we cannot accept or pay for traffic that does not pass our quality and fraud verification standards.

Based on the completed review:

• 1 verified player will be approved for payment
• 4 players were rejected due to failing fraud and quality validation

This decision is fully aligned with the terms agreed upon between both parties.

Dear partner, we remain open to constructive cooperation and further communication. However, we cannot accept manipulative pressure or low-quality traffic.

Please contact your Affiliate Manager directly to proceed with the payment for the approved player and discuss any further questions.

 

[slotmasters1k]

Thank you for your public response. We will address each point with documented facts.

---

**1. "The partner acknowledged traffic quality concerns from the very beginning"**

We acknowledged that BigBettyPartners requested a traffic pause on May 25 citing low ROAS. We complied immediately. Acknowledging a pause request is not the same as admitting traffic fraud. These are two completely different things.

For the record, the actual timeline is:
· May 21 — deal agreed
· May 21–24 — 5 FTDs delivered. Payment threshold reached in full.
· May 25 — traffic pause requested citing low ROAS and negative NGR. We comply.
· June 2 — anti-fraud investigation first mentioned, 12 days after FTDs delivered and AFTER the payment threshold was already met.
· June 9 — our formal deadline. No report, no timeline, no payment.
· June 15 — SEON report finally delivered, 26 days after FTDs.

The anti-fraud investigation was opened 12 days after the payment threshold was reached — not before, not during. This is the core issue.

---

**2. "Email fraud hits: 725, 64, 58, 26"**

These specific figures were not included in the SEON report shared with us on June 15. We received SEON scores and decisions — APPROVE or REVIEW — not email fraud hit counts. These numbers are being presented publicly for the first time here.

More importantly: email fraud hits in SEON reflect the historical reputation of an email address across fraud databases. They do not indicate that the affiliate sent motivated or incentivized traffic. A player can have a flagged email and still be a genuine organic user who found the casino through a Google search. The affiliate has zero control over what email address a player registers with.

If email fraud hits were a disqualifying criterion, this threshold should have been defined in the deal terms. It was not.

---

**3. "SEON approval is not payment approval"**

BigBettyPartners shared a SEON report as their official anti-fraud findings. We responded to that report. Their own fraud tool returned:
· Player 6727068 — REVIEW (score 11) — NordVPN detected
· Player 6722857 — APPROVE (score 1)
· Player 6735181 — APPROVE (score 5)
· Player 6727621 — APPROVE (score 2)
· Player 6728115 — APPROVE (score 1)

4 out of 5 APPROVE. BigBettyPartners offered to pay for 1. When we challenged this, they said SEON doesn't determine payment. That is a moving goalpost — share the SEON report as evidence, then dismiss it when it doesn't support your position.

---

**4. "Shared IPs and proxy-related activity"**

All 5 players share IP 3.123.197.135, flagged as GEO: DE. This IP belongs to PacketHub S.A. — a German datacenter. This is BigBettyPartners' own tracking and postback infrastructure appearing in session data. It is not players sharing devices or connections.

The actual ISPs of the players are:
· Xtra Telecom S.A. — Spanish ISP
· Orange Espagne SA — Spanish ISP
· Euskaltel S.A. — Spanish ISP
· Telefonica de Espana SAU — Spanish ISP

4 out of 5 players connected through Spanish ISPs. The "shared IP" flag is their own server. No technical rebuttal to this has been provided.

---

**5. "Clause 5.1 — 180 days"**

Clause 5.1 requires a suspected breach by the affiliate. In 27 days, BigBettyPartners has not identified a single specific action by SlotMasters1K constituting a breach of the affiliate agreement. Email fraud hits on player accounts are not an affiliate breach. Negative NGR is not an affiliate breach. Low average deposits are not an affiliate breach.

Clause 5.1 is not a blank 180-day shield to avoid paying earned CPA commissions whenever a casino loses money on a deal.

---

**SUMMARY FOR AGD MODERATORS**

BigBettyPartners:
· Payment threshold (5 FTDs) was reached on May 24 — 4 days after the deal started
· Traffic paused May 25 — the day after threshold was met
· Anti-fraud investigation opened June 2 — 9 days after threshold was met
· SEON report shows 4 APPROVE, 1 REVIEW — then claims SEON doesn't determine payment
· Email fraud hit counts presented publicly for the first time — not included in the original report shared with us
· "Shared IP" flag is their own tracking server, not player behavior
· Zero specific affiliate breach identified in 27 days

Our position remains: €800 for 4 SEON-approved players with Spanish ISPs and no demonstrated affiliate breach.

We are available to share the full timestamped Telegram conversation with AGD moderators privately.

SlotMasters1K — slotmasters1k.net
Ref: SM1K-BIGBETTY-20260605