Evidence ev_01m6sgqmgph513gs4hywpervpc: Pawbets withdrawal methods
This page shows one reading behind the statements on Pawbets's page: what CasinoGuard captured, when and from where, how, and the files kept as proof, each with its SHA-256 so anyone can check it is unchanged.
- Evidence: ev_01m6sgqmgph513gs4hywpervpc
- Topic: Withdrawal methods
- Source: pawbets.com, cashier page (official)
- Scope: United Kingdom (GB)
- Captured: 2026-11-06 22:47 UTC
- Result: read, the first version of what the source states
- Read by:
wintop-payments@1
Crawl
- Crawl: 01m6sgcbmx1jdd9tkkeeychtk4 (done)
- Requested: 2026-11-06 22:41 UTC
- Started: 2026-11-06 22:47 UTC
- Finished: 2026-11-06 22:47 UTC
- Collected with:
[email protected] running wintop-payments@1 - Looked from: United Kingdom (GB) · Desktop · pawbets3.com · language en
- Proxy: pool
uk-residential-di(Residential, GB) - Exit network: not recorded (where the casino saw the visit come from)
View 2: payments:withdrawal
- Asked for: https://pawbets3.com/en/payment
- HTTP status: none (reached without loading a page)
- Captured: 2026-11-06 22:47 UTC
- Steps: click Withdrawal (tab)
Full-page screenshot:
Screenshot of what it read:
| File | Size | SHA-256 |
|---|---|---|
| Full-page screenshot | 35.8 KB | 1717ba32cc689028b723811e3a00d91649dbf13f51a5c3425e858faec244e685 |
| Screenshot of what it read | 25.5 KB | 1ebb8591677f2b85f3588319edd73dc548242b63831d129079f1604960c78368 |
| Web archive (WACZ) | 2.8 MB | 24716530e6bb25220a3c66530269e68e35107a3d5ac252b87567778f5a9b04c7 |
What it read
The reading as the worker sent it:
{
"methods": [
{
"name": "Bank Transfer",
"currency": "GBP",
"max_amount": 4000,
"min_amount": 50
},
{
"name": "Credit Card",
"currency": "GBP",
"max_amount": 2500,
"min_amount": 50
},
{
"name": "USDT TRC-20",
"currency": "GBP",
"max_amount": 10000,
"min_amount": 50
},
{
"name": "USDT ERC-20",
"currency": "GBP",
"max_amount": 10000,
"min_amount": 50
},
{
"name": "USD Coin",
"currency": "GBP",
"max_amount": 10000,
"min_amount": 50
},
{
"name": "ETHEREUM",
"currency": "GBP",
"max_amount": 10000,
"min_amount": 50
},
{
"name": "SOLANA",
"currency": "GBP",
"max_amount": 10000,
"min_amount": 50
},
{
"name": "TRON",
"currency": "GBP",
"max_amount": 10000,
"min_amount": 50
},
{
"name": "BITCOIN",
"currency": "GBP",
"max_amount": 10000,
"min_amount": 50
},
{
"name": "BITCOIN CASH",
"currency": "GBP",
"max_amount": 10000,
"min_amount": 50
},
{
"name": "DOGECOIN",
"currency": "GBP",
"max_amount": 10000,
"min_amount": 50
},
{
"name": "LITECOIN",
"currency": "GBP",
"max_amount": 10000,
"min_amount": 50
}
]
}
How to check it
- The web archive is what the browser received during the crawl: every response with its request, and each view as rendered, listed as a page of its own (a crawl's views share one archive). Download it and open it in ReplayWeb.page to browse each page as it was.
- Each file's SHA-256 is that of the file when it was received; recompute it to check the file is unchanged.
- Cookies, logins and tokens are left out of every file, and so is the proxy's credential.
- The Markdown version and plain-text version of this page say the same.