- Revenue Share Mechanisms and Real-Time Commission Aggregation
- Performance Marketing Vectors and Indonesia Traffic Ontologies
- Affiliate Dashboard Analytics and Reporting Controls
- Technical Setup: Affiliate API Integration and Tracking Deployment
- Cryptocurrency Payout Infrastructure and Financial Settlement
- Compliance Requirements and Frequently Asked Questions (FAQ)
Each campaign receives an identifier, and subsequent registrations, wagering events and revenue values are assigned to that source. This makes it possible to compare advertising expenses recorded in Indonesian rupiah with partner income held in digital assets. The commission engine then applies the account’s RevShare tier and relevant deductions.
BC.Game is operated by Twocent Technology Limited, a limited liability company registered in Belize under number 000041939. Its registered address is Sea Urchin Street, San Pedro, Ambergris Caye, Belize. The platform operates under Anjouan licence ALSI-202410011-FI1 and may also refer to Curaçao licensing frameworks in contractual materials. These arrangements do not grant authorization in Indonesia.
Online gambling is prohibited under Indonesian law, and enforcement can extend to websites, advertising distribution and connected financial activity. Indonesian publishers must independently examine the legal and tax status of their work before signing an agreement or buying traffic. Commercial exposure also remains significant because media costs, player results, disputed events and cryptocurrency volatility can reduce the amount ultimately settled.
Revenue Share Mechanisms and Real-Time Commission Aggregation
The BC.Game affiliate account assigns a commercial profile to each approved publisher. It defines the RevShare percentage, permitted traffic, deductions and sub-affiliate conditions. Standard traffic normally enters the base tier. Higher rates depend on sustained volume, verified sources and an individual agreement.
Turnover represents accepted stakes, not operator income. GGR measures stakes minus player winnings, while NGR is the margin left after operational deductions. The affiliate split is applied at the end of this sequence.
Mathematical Breakdown of House Edge and NGR Calculations
The theoretical margin can be estimated through the house edge:
Expected GGR = Qualifying Turnover × Theoretical House Edge
Actual results use settled values:
GGR = Qualifying Stakes − Player Winnings
The remaining margin is calculated as follows:
Real NGR = GGR − Provider Fees − Network Costs − Transaction Charges − Administrative Overhead
The final allocation is:
Affiliate Commission = Real NGR × Assigned RevShare Rate
Assume that attributed users place $50,000 in qualifying stakes and receive $47,000 in winnings. GGR equals $3,000. If the applicable deductions total $500, real NGR is $2,500. A 35% RevShare produces a commission of $875. The account statement remains authoritative when a contract applies further adjustments.
Multi-Tier Sub-Affiliate Tracking Protocols
Multi-tier tracking separates direct traffic from activity delivered by other approved partners. Level 1 belongs to the principal publisher. Level 2 records a connected sub-affiliate, while Level 3 creates another controlled branch where the contract permits it.
The main UID preserves account ownership. CIDs and Sub-IDs distinguish domains, placements or buying teams. When registration and turnover events arrive, the system associates them with the originating branch instead of merging all activity into the parent account.
Table 1: Commission Tier Multipliers & NGR Deduction Breakdown
| Traffic Level / Volume Metric | Base RevShare Rate (%) | Sub-Affiliate Split (%) | Deductions (Provider/Gas Fees) |
| Tier 1 (Base Volumetric) | 25% Standard Baseline | 5% Level 1 Override | Fixed Statutory Deductions |
| Tier 2 (Mid-Scale Flow) | 35% Escalated Scale | 3% Level 2 Sub-Split | Automated Provider Fee Offset |
| Tier 3 (High-Volume Partner) | Up to 50% Enterprise Rate | Custom Multi-Tier | Real-Time Net NGR Allocation |
A higher tier is not triggered by clicks alone. Traffic validity, NGR and consistent campaign volume remain part of the assessment.
Last used 6 minutes ago
Performance Marketing Vectors and Indonesia Traffic Ontologies
Indonesian campaigns require separate tracking for every acquisition channel. Media expenses may be paid in IDR while commissions are recorded in cryptocurrency, so combining several sources under one identifier weakens cost analysis.
The traffic verticals covered by the architecture are:
- Organic Search Engine Optimization (SEO): Technical reviews, audit pages and comparison portals serving high-intent searches.
- Social and Community Networks: Verified Telegram or Discord channels covering crypto, Web3 or sports analytics.
- Media Buying and Display Networks: Contextual programmatic inventory limited to approved audiences and transparent placements.
- Mobile App Traffic (PWA/APK): Encrypted wrappers carrying assigned campaign parameters through the mobile journey.
A separate CID for each channel makes it possible to compare registration quality, turnover and NGR without confusing an SEO visitor with traffic from a mobile placement.
Table 2: Data Latency & Reporting Feed Specifications
| Data Parameter | Update Interval | API Endpoint Protocol | Verification Status |
| Clicks & Conversions | Real-Time (< 5 seconds) | Server-to-Server (S2S) Postback | Automated Log Registry |
| NGR & Turnover Calculations | Hourly Aggregation | RESTful Analytics API | Block-Level Audit Sync |
| Commission Payout Settlement | Instant / On-Demand | Smart Contract Execution | Blockchain Ledger Verified |
Clicks can appear almost immediately, whereas financial values need the related gaming and transaction records. This explains why conversion data and NGR may refresh on different schedules.
Last used 6 minutes ago
Affiliate Dashboard Analytics and Reporting Controls
The dashboard connects acquisition data with financial results. Publishers can inspect direct traffic, sub-affiliate branches and individual campaign identifiers without exporting every event to an external tracker.
The principal analytics metrics are:
- clicks, registrations and initial conversion events;
- qualifying turnover for each campaign;
- GGR, deductions and real NGR;
- pending, approved and settled commissions;
- Level 1, Level 2 and Level 3 contributions;
- source-level conversion and retention values.
Registrations alone do not establish campaign quality. A source can deliver many accounts but little qualifying turnover. High turnover with weak NGR may instead reflect player results, deductions or unsettled events.
An Indonesian reporting export should retain these parameters:
- reporting period and time zone;
- UID, CID and Sub-ID;
- domain, placement and traffic type;
- acquisition expenditure in IDR;
- cryptocurrency and settlement network;
- exchange-rate source and conversion timestamp.
IDR serves as an accounting reference, not as the stated affiliate payout currency. Recording the exchange rate is necessary because a crypto balance can change in rupiah value before it reaches the destination wallet.
Last used 6 minutes ago
Technical Setup: Affiliate API Integration and Tracking Deployment
Deployment begins with a source map showing which identifier belongs to each domain, placement or buying team. This prevents attribution errors when the same publisher runs several campaigns simultaneously.
The Affiliate API and Unique Identifier Deployment protocol follows four stages:
- Partner Portal Initialization: Authenticate access to the BC.Game partner dashboard through TLS 1.3 and activate Mandatory Two-Factor Authentication.
- Unique Identifier Generation: Configure UIDs, CIDs and Sub-IDs with neutral labels for individual sources and campaign branches.
- S2S Postback and Webhook Configuration: Map HTTP/HTTPS callbacks for registration and initial-turnover events, then connect event tokens to Voluum, Keitaro or compatible analytics software.
- Data Feed Verification: Send controlled test hits and confirm that timestamps, Sub-IDs and attributed events match across both reporting systems.
Paid distribution should start only after the test data reconciles. The webmaster should also check rejected payloads, callback retries and duplicated events. API secrets, authentication values and wallet credentials must never appear in a public tracking URL.
Last used 6 minutes ago
Cryptocurrency Payout Infrastructure and Financial Settlement
Affiliate settlement transfers an approved balance to an external cryptocurrency wallet. The asset symbol and network must match: USDT on TRON, Ethereum and Polygon represents three different transfer routes.
Table 3: Blockchain Settlement Specifications for Affiliates
| Network Protocol | Supported Asset | Confirmation Threshold | Gas / Fee Structure |
| TRON (TRC-20) | USDT | 3–5 Minutes | Low Fixed Network Energy |
| Bitcoin Native | BTC | 2–3 Blocks | Dynamic Sat/vB Rate |
| Ethereum (ERC-20) | ETH / USDT | 12–15 Block Confirmations | Dynamic Gwei Base Rate |
| Polygon (POS) | USDT / MATIC | 1–2 Minutes | Minimal Micro-Transaction Gas |
The displayed intervals describe ordinary processing conditions. Network congestion, compliance review or wallet maintenance can extend the actual settlement time.
Before approving a transfer, the affiliate should verify:
- asset and blockchain protocol;
- destination address and wallet compatibility;
- minimum settlement threshold;
- network, energy or gas fee;
- required confirmation count;
- transaction hash generated after broadcast.
The TxID supplies a public audit record for the amount and destination. It cannot recover funds sent to an incompatible address or through the wrong network.