BigBang Casino API — Game Aggregation Service Agreement

1Definitions

1. 1.1
   “Platform” — the BigBang Casino API service at api.bigbangcasino.bet, its REST API (/api/v1), customer portal, sandbox and related infrastructure.
2. 1.2
   “Customer” — the legal person that registers an account, holds an API key and integrates the Platform into its own gaming site (“Customer Site”).
3. 1.3
   “Standard Titles” — games served from the Platform’s own remote game server (in-house and emulated engines). Listed with mode: standard.
4. 1.4
   “Premium Titles” — games served from the original studio’s remote game server through a licensed aggregation partner. Listed with mode: premium.
5. 1.5
   “Provider” — a game studio or engine family as listed by GET /api/v1/providers. Fees are set per Provider.
6. 1.6
   “GGR” — Gross Gaming Revenue: total bets minus total wins on completed rounds, per Provider, per Billing Period, as defined in clause 3.
7. 1.7
   “Billing Period” — one calendar month, midnight to midnight, server time (Europe/Berlin, UTC+1/+2).
8. 1.8
   “Prepaid Balance” — the Customer’s credit held on the Platform, denominated in USDT, from which all Fees are debited.
9. 1.9
   “Live Key” — the production API key. “Sandbox Key” — the free ek_test_ key that plays on a virtual balance.
10. 1.10
    “Dedicated Shop” — an optional isolated casino instance for one Customer, with its own currency, bet ladders, risk rules and player pool, as opposed to the shared multi-tenant instance.

2Service tiers and fees

1. 2.1
   Sandbox is free, has no time limit and requires no funding. It provides a 100,000-unit virtual balance, Standard Titles only, real game sessions and real wallet callbacks flagged "sandbox": true. Sandbox play is never billed and never counts toward GGR.
2. 2.2
   Standard tier — Standard Titles are billed at 4.5% of GGR per Provider per Billing Period, unless a different rate for a specific Provider is shown in the portal’s Providers page.
3. 2.3
   Premium tier — Premium Titles are billed at 7.5% of GGR per Provider per Billing Period. Pragmatic Play Live is billed at 9.0%.
4. 2.4
   Both tiers are available on the same Live Key. Premium and real-money play require a positive Prepaid Balance (clause 4).
5. 2.5
   Dedicated Shop add-on — 100 USDT per month, billed in advance from the Prepaid Balance. Launch offer: the first 6 months at 50 USDT per month, applied automatically at signup and stepping up to the standard price afterwards. GGR fees apply on top.
6. 2.6
   Reseller add-on — 100 USDT per month, billed in advance from the Prepaid Balance. Enables issuing sub-keys to the reseller’s own clients; the Platform bills the reseller at its wholesale rate and does not bill the reseller’s clients.
7. 2.7
   The rate applied to a Provider is the rate shown in the portal at the moment a round is played. BigBang may change per-Provider rates with at least 30 days’ notice by e-mail and portal notice; a change never applies to rounds already played.
8. 2.8
   There are no setup fees, integration fees, minimum monthly commitments, per-request charges or API rate-tier charges. The only charges are those in this clause and in Schedule A.

3GGR calculation and settlement

1. 3.1
   Formula. For each Provider and each Billing Period: GGR = max(0, Σ bets − Σ wins) over completed rounds attributed to the Customer’s Live Key. Fee = GGR × Provider rate.
2. 3.2
   Floored per Provider. A Provider on which players win more than they bet in a period contributes zero, not a negative amount. Losses on one Provider never offset GGR on another, and a negative period is never carried into the next. Consequently a Customer whose players are net winners overall may still owe Fees on the Providers where the house won.
3. 3.3
   Currency conversion. Rounds are recorded in the currency of the session. GGR is converted to USDT at the Platform’s daily reference rate at the time of settlement; currencies without a market rate use the fixed rate published in the portal.
4. 3.4
   Continuous settlement. Fees are debited from the Prepaid Balance progressively during the Billing Period (approximately every 5 minutes) against month-to-date GGR. If month-to-date GGR on a Provider later falls, the corresponding Fee is credited back, down to zero for that Provider and period. The Billing Period is closed and reconciled after month end.
5. 3.5
   Attribution. A round is attributed to the Live Key whose session launched it. Rounds launched on a Sandbox Key are excluded. Free rounds, bonus rounds and feature purchases are included at their recorded bet and win values.
6. 3.6
   Reporting. The portal’s Reports page shows live-key GGR per Provider and the resulting Fee for the current and past periods, and the Ledger page shows every debit and credit. The portal’s env=live view is the billing basis; env=sandbox and env=all are informational only.
7. 3.7
   Rounds with no Provider. Rounds whose game cannot be matched to a Provider are grouped under “Other” and billed at the Standard rate.

4Prepaid balance

1. 4.1
   All Fees are debited from the Prepaid Balance. The balance is denominated in USDT and funded by cryptocurrency (USDT, BTC and other assets offered at checkout) through NOWPayments. Card and bank transfer are not accepted. Minimum top-up: 50 USDT.
2. 4.2
   A top-up is credited when the payment processor confirms the transaction on-chain. Network fees and exchange spread are borne by the Customer; the amount credited is the amount received in USDT.
3. 4.3
   The balance never goes below zero. A Fee larger than the remaining balance is debited only up to the balance; the remainder is recorded as Outstanding Fees and collected from the next top-up before any new usage.
4. 4.4
   At zero balance the Live Key is paused: new real-money and Premium launches are refused, and a Dedicated Shop remains visible in the portal but locked (read-only) until the balance is topped up by at least the outstanding amount. Rounds already in progress are completed and settled. Sandbox play is unaffected.
5. 4.5
   Dedicated Shop and Reseller subscriptions renew monthly from the balance. If the balance cannot cover a renewal, the subscription is marked past due; a Dedicated Shop is locked and Reseller rights are suspended until the balance covers the renewal, after which they resume automatically.
6. 4.6
   Low-balance and zero-balance notices are shown in the portal; the Customer is responsible for maintaining sufficient balance. BigBang is not liable for lost play while the key is paused for lack of funds.

5RTP and Standard RTP controls

1. 5.1
   Premium Titles run on the original studio’s server. Their RTP is the studio’s published RTP for the variant made available to the Platform, and cannot be altered by BigBang or the Customer.
2. 5.2
   Standard Titles run on the Platform’s own game server. Their theoretical RTP is governed by the Platform’s risk engine and by rules the Customer may configure in the portal’s RTP Risk Management page (Dedicated Shop customers) — target RTP, minimum/maximum RTP, maximum win per spin, per session and per day, maximum win multiplier, bet overrides, active hours and days, and streak limits. Rules resolve by priority and specificity (player+game > player > game > Provider > shop-wide).
3. 5.3
   Auto Session RTP — an optional control that steers the realised RTP of each player session toward the configured target. It is enabled in “soft” mode by default for customer shops and can be turned off in the portal.
4. 5.4
   Platform RTP governor. Independently of any Customer rule, the Platform withholds wins on Standard Titles while a Customer account’s realised RTP over the governor’s window exceeds 96%, and resumes normal payouts once it falls back below. The governor never acts below 96%. This protects both parties from runaway payouts on emulated engines and is not configurable by the Customer.
5. 5.5
   What a player sees is what a player is paid. No control described in this clause changes a win after it has been displayed to the player. Controls act before a result is presented.
6. 5.6
   The Customer is solely responsible for ensuring that the RTP configuration it chooses, and the fact that Standard Titles are emulated engines, comply with the laws and licence conditions applicable to the Customer Site and are disclosed to players as those laws require.

6Providers, games and market restrictions

1. 6.1
   The catalogue available to a Live Key is the catalogue returned by GET /api/v1/games for that key at any given time. BigBang may add, remove, rename or reclassify Providers and games at any time; removals of an entire Provider are notified with at least 7 days’ notice where practicable.
2. 6.2
   The Customer may disable any Provider for its own key in the portal; disabled Providers are excluded from catalogue, detail and launch responses.
3. 6.3
   Premium Titles are subject to the studio’s own restrictions on currency and territory. A launch may be refused by the upstream studio for a currency, country or player the studio does not accept; such refusals are returned as API errors and are not a Platform failure. BigBang does not warrant that any specific Premium studio remains available in any specific market.
4. 6.4
   Standard Titles are served in the currencies listed for the Customer’s shop. Currency is fixed per session at launch.
5. 6.5
   The Customer must not offer the Platform’s games to players in jurisdictions where the Customer is not licensed or where such offering is unlawful, and must not offer them to minors or self-excluded persons. Geo-blocking and player verification on the Customer Site are the Customer’s responsibility.

7Wallet and transaction responsibilities

1. 7.1
   Seamless wallet. The Customer’s wallet is the single source of truth for player balances. The Platform never holds player funds; it sends signed callbacks (user_data for balance, balance_change for bets, wins and rollbacks) to the wallet URLs configured in the portal, and the Customer applies them to its own ledger.
2. 7.2
   Customer obligations. The Customer must: (a) verify the HMAC-SHA256 signature on every callback and reject unsigned or mis-signed requests; (b) treat transaction_id as idempotent — a repeated callback with the same id must return the original result and must not be applied twice; (c) respond within 2.5 seconds (target under 200 ms); (d) return the exact balance after the change; (e) keep the wallet endpoints reachable over HTTPS 24/7.
3. 7.3
   Platform obligations. BigBang will: (a) send a bet callback before any win for the same round, with matching round_id; (b) retry a failed win callback and never silently drop a win; (c) send a rollback (type refund) for a bet whose round cannot be completed; (d) never issue a callback that would take a balance negative — an insufficient-balance response from the wallet cancels the bet.
4. 7.4
   Failed callbacks. If the wallet does not answer a bet callback within the timeout, the bet is not placed and the player is shown an error. If the wallet does not answer a win callback, the Platform retries; unresolved wins are listed in the portal for manual reconciliation. Money lost because the Customer’s wallet was unreachable, slow or returned wrong balances is the Customer’s responsibility.
5. 7.5
   Reconciliation. The portal’s Transactions page and GET /api/v1/transactions expose every bet, win and rollback with round and transaction ids. The Customer should reconcile daily and raise discrepancies within 14 days of the round; after that period the Platform’s records are final for billing purposes.
6. 7.6
   Live Key credentials and wallet secrets must be kept confidential. All use of a key is deemed the Customer’s use until BigBang is notified of a compromise and has rotated the key.

8Refunds, cancellations and disputes

1. 8.1
   Round cancellation. A round that cannot be completed (studio error, session loss, timeout) is cancelled by the Platform and the bet is returned via a rollback callback. Cancelled rounds do not count toward GGR.
2. 8.2
   Displayed wins are honoured. A win presented to the player in the game client is paid in full through the wallet. BigBang does not claw back a displayed win.
3. 8.3
   Player disputes. The Customer handles disputes with its own players. BigBang provides round logs (bet, result, win, timestamps, callback responses) on request within 3 business days to support the Customer’s decision.
4. 8.4
   Provider malfunction. Where a studio or the Platform declares a game malfunction (“malfunction voids all pays” applies to Premium studios’ own rules), affected rounds are voided, bets are returned by rollback, and the rounds are excluded from GGR. The Customer must pass the same treatment on to its players.
5. 8.5
   Fee disputes. The Customer may dispute a Fee within 30 days of the close of the Billing Period by e-mail with round-level detail. Undisputed Fees are final. Agreed corrections are applied as credits to the Prepaid Balance.

9Prepaid balance refund policy

1. 9.1
   Top-ups are prepayments for services and are non-refundable, except as set out in 9.2 and 9.3.
2. 9.2
   Termination by BigBang without cause (clause 10.4): the unused Prepaid Balance, less Outstanding Fees, is returned in USDT to a wallet address nominated by the Customer within 14 days.
3. 9.3
   Termination by the Customer (clause 10.3): the unused Prepaid Balance is returned less Outstanding Fees and a 5% processing charge, provided the amount to be returned is at least 100 USDT; smaller balances are forfeited.
4. 9.4
   No refund is made on termination for cause (clause 10.5). Subscription fees already charged for a Dedicated Shop or Reseller month are not refunded pro rata.
5. 9.5
   Refunds are made only to a wallet controlled by the Customer, in USDT, and only after any Outstanding Fees are cleared.

10Suspension and termination

1. 10.1
   Automatic pause. The Live Key is paused at zero Prepaid Balance (clause 4.4) and resumes automatically on top-up. This is not a suspension under this clause.
2. 10.2
   Suspension. BigBang may suspend a key immediately, with notice, where it reasonably believes: the key is compromised; the wallet is returning incorrect balances or failing signature checks; the Customer is offering games in a prohibited market or to prohibited persons; the account is used for fraud, bonus abuse at scale, or money laundering; or a studio requires the Customer’s traffic to be stopped. Suspension is lifted when the cause is resolved.
3. 10.3
   Termination by the Customer — at any time, by e-mail to support@bigbangcasino.bet. The key is disabled at the end of the current day; open rounds are completed.
4. 10.4
   Termination by BigBang without cause — on 30 days’ written notice.
5. 10.5
   Termination for cause — immediately on written notice for material breach not cured within 7 days of notice, or without cure period for fraud, unlawful use, or repeated wallet failures that expose players or the Platform to loss.
6. 10.6
   On termination: Outstanding Fees become immediately due and are deducted from the Prepaid Balance; the Customer must remove all Platform game links and artwork from the Customer Site; clauses 3, 7.5, 9, 11, 12, 14 and 15 survive.

11Availability and liability for game, RGS and API failures

1. 11.1
   Service level. BigBang targets 99.5% monthly availability of the API and the Standard Titles game server, measured on /api/v1/games and /api/v1/launch, excluding scheduled maintenance announced at least 24 hours in advance and events outside BigBang’s control (upstream studio outages, network attacks, hosting-provider failures). The target is an operational objective, not a guarantee; no service credits are payable for missing it.
2. 11.2
   Premium Titles depend on third-party studios and aggregation partners. BigBang passes through their availability and is not liable for their outages, latency, rejected launches or changes to their game catalogue.
3. 11.3
   Exclusions. BigBang is not liable for: loss of profit, revenue, players or goodwill; losses caused by the Customer’s wallet, network or configuration; losses from the Customer’s RTP or risk settings; regulatory penalties incurred by the Customer; or any indirect or consequential loss.
4. 11.4
   Cap. BigBang’s total liability under this Agreement in any 12-month period is limited to the total Fees actually paid by the Customer in the 3 months preceding the claim, or 1,000 USDT, whichever is greater. Nothing excludes liability that cannot be excluded by law.
5. 11.5
   Customer indemnity. The Customer indemnifies BigBang against claims arising from the Customer Site, its players, its marketing, its licensing status, and its use of the games in any territory.

12Standard game titles, trademarks and artwork

1. 12.1
   Standard Titles are in-house and emulated engines that reproduce the mathematics and presentation of well-known games. BigBang grants the Customer a non-exclusive, non-transferable, revocable licence to display and offer Standard Titles on the Customer Site for the term of this Agreement, solely through the Platform’s launch URLs.
2. 12.2
   No trademark licence. No right in any studio name, game title, logo, character or artwork is granted beyond displaying the catalogue thumbnails and names the Platform supplies, as supplied. The Customer must not: represent Standard Titles as original, certified or licensed releases of the named studio; use a studio’s name or logo in advertising, app-store listings or affiliate material; or modify, extract, re-host or redistribute game clients, thumbnails or artwork.
3. 12.3
   Take-down. If a rights holder objects to a Standard Title or its artwork, BigBang may withdraw it immediately and the Customer must stop offering it on notice. Withdrawal of a title is not a breach and does not entitle the Customer to compensation.
4. 12.4
   Premium Titles are used under the studio’s own terms as passed through by the aggregation partner; the Customer may use only the marketing material the Platform provides for them.
5. 12.5
   The Customer is responsible for determining whether offering Standard Titles is permitted under its licence and in its markets, and accepts that certification (e.g. GLI/BMM) is not provided for Standard Titles.

13Compliance, data and security

1. 13.1
   The Customer holds all licences and approvals required to operate the Customer Site and is the operator of record toward its players and regulators. BigBang is a technology supplier only.
2. 13.2
   The Platform processes a player identifier, currency, session and round data supplied by the Customer. The Customer must not send names, e-mail addresses, documents or other personal data in player identifiers. Each party is an independent controller of the data it holds. Round data is retained for 24 months.
3. 13.3
   The Customer must implement responsible-gambling, AML and KYC controls appropriate to its licence; the Platform provides per-player win limits and cooldowns as tools only.
4. 13.4
   Neither party will attempt to reverse-engineer, scrape, load-test without consent, or circumvent the security of the other’s systems. Security incidents affecting the other party are notified within 48 hours.

14Governing law and dispute resolution

1. 14.1
   This Agreement is governed by the laws of Curaçao, excluding its conflict-of-law rules.
2. 14.2
   The parties will first attempt to resolve any dispute by good-faith negotiation between senior representatives for 30 days from written notice.
3. 14.3
   Unresolved disputes are finally settled by binding arbitration by a single arbitrator seated in Willemstad, Curaçao, conducted in English; the award is final and enforceable in any competent court.
4. 14.4
   Either party may seek injunctive relief in any competent court to protect its intellectual property or confidential information.

15General

1. 15.1
   Changes to these terms. BigBang may update this Agreement with at least 30 days’ notice by e-mail and portal notice. Continued use after the effective date is acceptance; a Customer who does not accept may terminate under clause 10.3 before that date.
2. 15.2
   Confidentiality. API keys, wallet secrets, fee rates, GGR figures and integration details are confidential to both parties for the term and 3 years after.
3. 15.3
   Assignment. The Customer may not assign or resell the service except through the Reseller add-on. BigBang may assign to a successor of the Platform business.
4. 15.4
   Notices are given by e-mail to the address on the portal account and to support@bigbangcasino.bet; a notice is received on the next business day.
5. 15.5
   Entire agreement. This document, Schedule A, the API documentation at api.bigbangcasino.bet/docs and the rates shown in the portal form the whole agreement. In case of conflict this document prevails, then Schedule A, then the documentation.
6. 15.6
   Language. The English version governs. Translations are for convenience.

ASchedule A — Fee summary

Worked example. In one month a Customer’s players bet 120,000 USDT and win 108,000 USDT on Standard Provider A (GGR 12,000 → fee 540 USDT), and bet 50,000 USDT and win 58,000 USDT on Premium Provider B (GGR −8,000 → floored to 0 → fee 0). Total fee for the month: 540 USDT, debited progressively from the Prepaid Balance, even though the Customer’s combined net was +4,000 USDT in the players’ favour.