Responsible Gaming

Purpose

Stakeworks provides B2B casino game software and integration tools. We do not operate a consumer sportsbook, casino, cashier, or player wallet through this public website. Because the platform can support gambling-adjacent and real-money operator use cases, responsible gaming controls must be designed into every operator integration before real-money traffic is enabled.

This page describes Stakeworks platform expectations and operator responsibilities. It is not a substitute for jurisdiction-specific responsible gaming rules, regulator requirements, operator procedures, or professional clinical advice.

Operator Responsibility

• Operators are responsible for determining whether their product is gambling, sweepstakes, social casino, skill game, promotional play, pay-per-head, sportsbook add-on, or another regulated model in each jurisdiction they serve.
• Operators must publish player-facing responsible gaming terms, help resources, self-exclusion instructions, complaint paths, bonus rules, and age/jurisdiction restrictions.
• Operators must implement legally required age verification, identity checks, geolocation, self-exclusion, blocked-jurisdiction controls, and problem-gambling interventions.
• Operators must train support, risk, compliance, and VIP teams to identify and respond to signs of gambling harm.
• Operators must not use Stakeworks to avoid player protection, licensing, AML, KYC, sanctions, responsible gaming, or advertising obligations.

No Underage Use

Stakeworks is not intended for children or underage players. Operators must prevent underage users from accessing real-money, prize, sweepstakes, credit, or age-restricted gaming activity. Minimum age varies by jurisdiction and product type. Operators must apply the strictest age rule required for the player, jurisdiction, and product.

Jurisdiction And Eligibility Controls

• Operators must block players in prohibited jurisdictions.
• Operators must confirm that each player is legally eligible for the product offered.
• Operators must apply jurisdiction-specific rules for deposits, withdrawals, bonuses, advertising, game availability, game speed, limits, disclosures, and self-exclusion.
• Operators must not use offshore, crypto, pay-per-head, affiliate, agent, or mirror-domain structures to evade laws or regulator restrictions.

Player Limits

Stakeworks supports operator-configured player limits, including minimum bet, maximum bet, daily and weekly bet limits, daily and weekly loss limits, daily and weekly win limits, and suspended status. Operators should configure these controls before enabling real-money mode.

Stakeworks does not replace the operator’s own KYC, AML, self-exclusion registry, geolocation, affordability, or player-support systems. Operators must keep those controls on their side and use Stakeworks player limits and suspension status as integration-level enforcement tools.

• Limits should be tested with demo and staging players before launch.
• Limit changes should be logged and reviewed, especially increases to limits.
• Operators should offer player-initiated cooling-off, timeout, deposit limits, loss limits, wager limits, and self-exclusion where required or appropriate.
• Operators should apply stricter controls to high-risk accounts, credit accounts, agent-managed accounts, and accounts showing signs of harm.

Self-Exclusion And Timeouts

Operators must maintain their own self-exclusion, cooling-off, and timeout processes. If a player is self-excluded, timed out, restricted, suspended, blocked by jurisdiction, or otherwise ineligible, the operator must not launch that player into Stakeworks games and must decline wallet actions for that player.

• Self-exclusion should apply across the operator account and related products where required.
• Excluded users should not receive promotional messages, bonus offers, reactivation campaigns, or VIP contact.
• Reinstatement after exclusion should follow documented legal and responsible gaming procedures.
• Support teams should have clear escalation paths for self-harm, distress, or loss-of-control statements.

Wallet And Credit Controls

In seamless wallet mode, the operator controls player balances. Operators must design debit, credit, rollback, and balance flows to prevent overspending, duplicate charges, mistaken credits, and play by restricted users.

• Debit requests should be declined when funds are insufficient, the player is restricted, limits are exceeded, the jurisdiction is blocked, or the account is under review.
• Credit and rollback requests should be idempotent and reconciled so players are not paid twice or denied legitimate reversals.
• Credit or pay-per-head models should include affordability, exposure, settlement, and agent oversight controls appropriate to the jurisdiction and business model.
• Operators should monitor abnormal bet patterns, rapid losses, repeated failed deposits, frequent limit increases, high-risk credit exposure, and unusual payout spikes.

Game Design And Player Information

• Operators should clearly disclose that games involve risk and that outcomes are uncertain.
• Operators should disclose rules, bet ranges, payout behavior, game modes, and any bonus or promotional conditions before play.
• Operators should avoid misleading statements about guaranteed winnings, risk-free play, skill control where chance dominates, or urgency that pressures players to continue.
• Operators should provide session history, balance history, transaction records, and support paths so players can understand their activity.
• Operators should consider reality checks, session reminders, and visible access to limits and timeouts where appropriate.

Marketing And Promotions

• Marketing must not target minors, excluded users, vulnerable users, blocked jurisdictions, or users who have opted out.
• Promotions must be truthful, clear, and not misleading about odds, wagering requirements, payout restrictions, eligibility, expiration, or withdrawal rules.
• Affiliate, agent, streamer, influencer, and pay-per-head marketing must follow the same restrictions as operator-owned marketing.
• Operators should avoid messages that frame gambling as income, debt relief, investment, guaranteed profit, social status, or a solution to financial pressure.

Signs Of Potential Gambling Harm

Operators should train teams and automated monitoring systems to identify patterns that may indicate harm. No single signal proves a problem, but repeated or severe signals should trigger review.

• Frequent limit increases, rapid deposit attempts, or chasing losses.
• Long sessions, repeated failed deposits, repeated declined debits, or sudden high-risk play.
• Requests for credit after losses, distress statements, threats of self-harm, or claims that play is unaffordable.
• Multiple account creation, account sharing, agent pressure, or attempts to bypass exclusions.
• Unusual payout spikes, suspicious wallet reversals, chargebacks, or inconsistent identity/payment behavior.

Support And Escalation

• Operators should provide visible player support routes for limits, timeouts, self-exclusion, disputes, and responsible gaming help.
• Support teams should be able to restrict accounts quickly when a player requests exclusion or shows urgent risk indicators.
• Operators should document responsible gaming contacts, restrictions, reinstatements, disputes, and escalations.
• Where available, operators should refer users to appropriate local problem-gambling support organizations and emergency services for immediate safety concerns.

Platform Controls Available In Stakeworks

• Operator game enablement and disabling by game and mode.
• Demo mode and real-money mode separation.
• Operator player limits and suspended-player status.
• License status controls that can block access when an operator is expired, suspended, or unpaid.
• Wallet transaction idempotency keys and transaction records.
• Admin and operator audit logs for sensitive changes.
• Reports and history pages for session, round, wager, payout, bonus funding, and transaction review.
• Hand-by-hand search by external player ID, approximate date/time window, round ID, game, status, and funding source for dispute review.

Testing Before Real-Money Launch

• Test demo launch, real launch, balance, debit, credit, rollback, insufficient funds, expired license, revoked API key, disabled game, suspended player, exceeded limits, and failed wallet callback paths.
• Test self-excluded and blocked-jurisdiction players from the operator side before calling Stakeworks launch APIs.
• Test duplicate wallet requests using the same idempotency key.
• Test reporting and dispute exports against expected wallet and session records.
• Test monitoring alerts for failed wallet calls, abnormal payout spikes, failed auth bursts, cron failures, and admin changes.

Emergency And Help Resources

If someone may harm themselves or others, contact local emergency services immediately. Operators should publish jurisdiction-appropriate support resources for their players. In the United States, operators commonly refer users to the National Problem Gambling Helpline at 1-800-GAMBLER where appropriate, but local requirements and resources vary.

Contact

Operators with responsible gaming, player protection, integration, or suspension questions can contact partners@stakeworks.online.