Admin Dashboard - webgames.lol

Monthly Revenue

$0.00

0 transactions

Active Players

0 sessions

Leaderboard Entries

0 games

Webhook Health

—

Checking...

Revenue Breakdown

Type	Amount	Count
Loading data

Recent Transactions

Date	Player	Amount	Type
Loading data

Suspicious Scores

Player	Game	Score	Anomaly	IP	Actions
Loading suspicious scores

Leaderboard Scores

Game

Username contains

Max rows

Game	Player	Score	Updated	Actions
No scores loaded yet.

Top Achievement Earners

Rank	Player	Achievements	Points
Loading achievement data

Payment Processors

Choose the active checkout provider and configure Stripe credentials.

Stripe API keys are managed at Developers → API keys: publishable keys start with pk_, server keys start with sk_ or rk_. Webhook signing secrets start with whsec_ and are managed at Developers → Webhooks for each endpoint.

Default Processor Fallback

Stripe is the active checkout provider for tip payments.

Stripe Account Settings

Stripe Server API Key

Use a Secret key (sk_) or Restricted key (rk_) from Stripe API keys.

Stripe Publishable Key

Client-side key from Stripe API keys (pk_).

Stripe Webhook Signing Secret

Not an API key. Copy from Stripe Dashboard → Developers → Webhooks endpoint details.

Stripe Webhook Endpoint URL (use this in Stripe)

Stripe Dashboard → Developers → Webhooks → Add endpoint: paste this full URL.

Path only for reverse proxies: /api/stripe-webhook.php

How To Add This Endpoint In Stripe

Open Stripe Dashboard → Developers → Webhooks.
Click Add endpoint and paste the URL from Stripe Webhook Endpoint URL above.
Click Select events and include checkout.session.completed, checkout.session.expired, and charge.refunded.
Save endpoint, open it, then click Reveal on Signing secret.
Paste that signing secret into Stripe Webhook Signing Secret on this page, then click Save Payment Settings.

Open Stripe Webhooks Stripe Webhooks Docs

Tip: configure both test mode and live mode endpoints in Stripe when you switch environments.

Stripe Tier Product IDs

Product IDs are optional and come from Stripe Product Catalog, not API keys.

Stripe Tier Price IDs

Price IDs are optional and come from Stripe Product Catalog, not API keys.

Stripe Backfill

Pull historical Stripe Checkout sessions and upsert them into local transaction data. Use this if webhook events were missed or old transactions are missing.

Backfill Mode

Full history Last days

Stripe One-Time Checkout

Configure a one-time Stripe product+price, then generate a Checkout Session URL and verify completion via webhook events.

Requires STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY in your server environment. Get these from the Stripe Dashboard.

Product Name

Currency

Unit Amount (cents)

Product ID

Price ID

Last Session ID

Last Checkout URL

Recent Completed Sessions

Completed At	Session ID	Amount	Status	Event ID
No completed sessions yet

Payment API Log

Live API error output for Payment Settings actions.

No API errors yet.

Crypto Checkout Settings

Simple setup: choose coins, add addresses per coin, save, then test derivation.

No JSON editing required in this tab.

BTCPay hosted checkout is now the primary crypto flow. Configure BTCPay first, then save.

BTCPay Server URL

BTCPay Store ID

BTCPay API Key

BTCPay Webhook Secret (optional)

Local Tip Amounts

Local Currency

Supported Coins

Comma-separated symbols. Changing this rebuilds the address fields below.

Default Coin

Receive Addresses Where users send their tips — your on-site wallets

Fallback Receive Address

Optional. Used when a coin has no specific address set above.

Coinbase Destination Addresses Your Coinbase deposit addresses — where you withdraw to

Coinbase Destination (legacy fallback)

Transfer Relay URL (optional)

When set, the Request Transfer action posts to this URL so your relay can execute the Coinbase transfer.

Transfer Relay Auth Header

Transfer Relay Auth Token

Legacy Coinbase API Key (optional)

Legacy Coinbase Webhook Secret (optional)

Enable per-tip auto-generated wallet addresses

When enabled, this site requests unique receive addresses from your wallet service for each new crypto tip session.

Address Derivation Service URL

Derivation Auth Header

Derivation Auth Token

Wallet Service Port

Coins Using Destination Tag/Memo

Wallet Base Addresses (required for derivation) Used by wallet-service for per-tip address/tag derivation

Wallet Derivation Secret

Enable automatic on-chain verification worker

When enabled, wallet-service polls pending submitted tx hashes, calls your verifier provider, and auto-confirms paid tips.

Auto Verify Provider URL

Auto Verify Auth Header

Auto Verify Auth Token

Min Confirmations

Internal App Base URL (wallet-service)

Crypto Service Health

Derivation Service

Checking...

No data yet.

Auto Verification Worker

Checking...

No data yet.

Health URL: pending...

Crypto Wallets

Overview of each configured coin wallet. Receive address is where users send tips. Coinbase destination is where you withdraw to. Confirmed balance is based on on-site confirmed tips.

No wallet data loaded yet.

Crypto Transfer Queue

Local crypto tips are received on-site. Confirm incoming hashes, then request transfer to Coinbase from here.

Created	User	Amount	Status	Tx Hash	Actions
No crypto records loaded yet.

Games

Edit all game variables here. Values are persisted to data/runtime-config.json.

Game Variables JSON

Webhook Proxy

What is Webhook Proxy Forwarding?

Stripe sends webhooks to one URL. Proxy forwarding makes this server relay every incoming Stripe event to a second server immediately after verifying the signature.

Stripe → this server (signature verified here)
This server → your target URL (forwarded instantly)
A loop guard prevents infinite forwarding chains

Use this to mirror events to a staging environment, a second site, or any service that needs to react to Stripe payments.

Step 1 of 3 — Target URL

Enter the webhook endpoint on the other server that should receive the forwarded payloads.

Forward URL

Must start with https://. This is the same path you would register with Stripe on the target server.

Step 2 of 3 — Authentication

Set a shared secret so the target server can verify that forwarded requests come from this proxy.

On the target site, go to Admin → Webhooks and paste the same token in Auth Token — or add WEBHOOK_FORWARD_AUTH_TOKEN=your-secret to its .env.

Auth Header Name

HTTP header sent to the target with every forwarded request. Keep the default unless you need a custom name.

Shared Secret

Leave blank to disable authentication. Use a long random string for production.

Step 3 of 3 — Review & Save

Webhook Events

Time	Type	Status	Retries	Event ID / Proxy
Loading webhook events

Staff Management

Add New Staff Member

Username

Password

Role

Current Staff

Username	Role	Created
Loading staff list...

Create Admin Account

Admin Portal

Advanced Admin Dashboard

Monthly Revenue

Active Players

Leaderboard Entries

Webhook Health

Revenue Breakdown

Recent Transactions

Suspicious Scores

Leaderboard Scores

Top Achievement Earners

Payment Processors

Stripe Account Settings

Stripe Backfill

Stripe One-Time Checkout

Recent Completed Sessions

Payment API Log

Crypto Checkout Settings

Crypto Service Health

Crypto Wallets

Crypto Transfer Queue

Games

Webhook Proxy

What is Webhook Proxy Forwarding?

Step 1 of 3 — Target URL

Step 2 of 3 — Authentication

Step 3 of 3 — Review & Save

Webhook Events

Staff Management

Add New Staff Member

Current Staff