稽核培训工具

远程稽核提款审核 · 审核流程、风险点、代理套利、日常巡查

一、培训定位 / Training Positioning

本工具整合《PHB_审核培训手册》、远程稽核岗位操作手册,以及本次新增的提款审核注意流程。用于训练远程稽核人员识别大额、首提、代理提款和主域名注册来源中的高风险订单。

This tool combines the PHB audit training manual, the remote audit operations manual, and the newly added withdrawal-review cautions. It trains remote auditors to identify high-risk large withdrawals, first withdrawals, agent withdrawals, and main-domain registration sources.

必须审核 / Must Review 主域名注册重点关注 / Main Domain Watch 同 IP / Same IP 账变 / Fund Changes 宝箱与拼多多 / Treasure Chest and PDD

需要审核的提款订单

  • 大额会员提款:金额 5000 以上。
  • 首次提款会员:首提必须检查完整链路。
  • 代理提款:重点查下级、上级、同 IP、宝箱与玩法。

Review all large withdrawals over 5000, first withdrawals, and agent withdrawals.

本次新增重点

  • 提款后账户余额必须留意。
  • 提款账号和注册账号是否一致。
  • 主域名注册来源要特别关注。
  • 上级无存款、下级用新站推广彩金盈利提款,一概不出。

New emphasis: balance after withdrawal request, account consistency, main-domain registration, and no payout when upper agent has no deposit and lower member profits from new-site promotion bonus.

培训使用方式

  • 先学习岗位操作图片。
  • 再按提款审核清单演练。
  • 最后用问答题复盘。

Learn workstation steps first, then practice with the withdrawal checklist, and finish with quiz review.

二、远程稽核岗位操作 / Remote Audit Workstation Operation

以下 8 张图片来自远程稽核岗位操作手册。图片按原用途分为三组:云桌面登录、验证码绑定、直属下线与同 IP 检查。

The following 8 images come from the remote audit operations manual. They are grouped by purpose: cloud desktop login, authenticator binding, and direct-subordinate/same-IP checks.

2.1 云桌面登录 / Cloud Desktop Login

云桌面登录入口
图 1:输入账号、密码和向管理人员索取的验证码。
Figure 1: Enter account, password, and the verification code from management.
打开云桌面
图 2:点击链接、电脑图标,再打开云桌面。
Figure 2: Click the link, computer icon, then open the cloud desktop.

2.2 验证码绑定 / Authenticator Binding

绑定后台 Google Authenticator 验证码教程:后台网址打开后,先在登录页点击“我还未绑定验证码,点击此处绑定”;进入绑定页后输入后台账号和密码,点击下一步;再打开手机 Google Authenticator;最后扫描后台二维码并输入 6 位动态验证码完成绑定。
Backend Google Authenticator binding tutorial: after opening the backend URL, first click the unbound-authenticator entry on the login page; then enter the backend account and password and click Next; open Google Authenticator on the phone; finally scan the backend QR code and enter the 6-digit dynamic code to complete binding.
后台绑定入口
图 3:后台登录页,先点击“我还未绑定验证码,点击此处绑定”。
Figure 3: On the backend login page, first click the unbound-authenticator entry.
输入账号密码
图 4:进入绑定页后,输入账号和密码,再点击下一步。
Figure 4: On the binding page, enter account and password, then click Next.
Google Authenticator
图 5:打开手机端 Google Authenticator 身份验证器。
Figure 5: Open Google Authenticator on the phone.
二维码绑定
图 6:使用 Authenticator 扫描二维码,输入 6 位动态验证码完成绑定。
Figure 6: Use Authenticator to scan the QR code, then enter the 6-digit dynamic code to complete binding.

2.3 直属下线与同 IP 检查 / Direct Subordinate and Same-IP Check

最近登录 IP 示例
图 7:直属下线页面中的最近登录 IP 示例,对应提款审核中的同 IP 检查。
Figure 7: Recent-login IP example on the direct-subordinate page, used for same-IP checks.
同 IP 核对
图 8:同 IP/下线信息核对页面,用于判断是否多账号或上下级同 IP。
Figure 8: Same-IP/subordinate verification page for multi-account and upper-lower same-IP checks.

三、提款审核注意流程 / Withdrawal Review Caution Flow

1. 订单分类大额、首提、代理、主域名注册来源。
Classify: large, first withdrawal, agent, main-domain source.
2. 同 IP检查是否同 IP 多账号、上下级同 IP。
Check same-IP multi-account or upper-lower same-IP.
3. 账变查最近存款、提款和彩金领取。
Check recent deposits, withdrawals, and bonuses.
4. 游戏检查投注量、游戏类别、是否同一非热门游戏。后台投注/游戏记录仅保留近 7 天,审核时不要超出可查范围;更早记录需结合账变与订单交叉核对。
Check turnover, game type, same non-hot game pattern. Backend betting/game records only cover the last 7 days; do not expect older betting rows.
5. 余额留意提款发起后账户余额。
Check balance after withdrawal request.
6. 账号一致提款账号与注册账号是否一致。
Confirm withdrawal account matches registration account.

3.1 大额与首提 / Large Withdrawal and First Withdrawal

审核对象 / Target必须检查 / Must Check处理口径 / Handling Standard
大额提款
Large withdrawal
5000 以上;充值提款记录;账变记录;彩金领取;投注记录(仅近 7 天);相同 IP;是否上级代理;提款后余额;提款账号是否与注册账号一致。
Over 5000; deposit/withdrawal records; fund changes; bonus claims; betting records (last 7 days only); same IP; upper-agent relationship; post-request balance; whether withdrawal account matches registration account.
不能只凭“无同 IP”或“盈利不高”直接放行。完成全套检查且无异常,才可继续处理;如发现同 IP 多账号、上下级同 IP、主域名注册异常、近期无存款却持续领彩金等情况,先发 Signal 群复核或转人工审核。
Do not approve only because there is no same IP or the profit is low. Continue only after the full checklist shows no anomaly. If same-IP multi-accounting, upper-lower same IP, abnormal main-domain registration, or continuous bonus claims without recent deposits are found, report to Signal group for review or move to manual audit.
首提
First withdrawal
总投注是否达到宝箱要求;是否卡 3000-4500 危险区间;是否有上级代理。
Check treasure-chest turnover requirement, 3000-4500 risk range, and upper agent.
投注超过 4500 且其他检查无异常,可继续处理;3000-4500 必须详细检查上级代理。
If turnover is over 4500 and other checks show no anomaly, continue processing; 3000-4500 requires detailed upper-agent review.
主域名注册来源
Main-domain registration source
当天会员注册时间、IP 地址、是否批量注册、是否关联代理链。
Check registration time, IP, batch registration, and agent-chain relationship.
主域名来的提款订单要特别关注,发现异常先拉人工审核或发群复核。
Main-domain source requires extra attention; suspicious cases should be moved to manual review or reported for review.
硬性规则:上级无存款的情况下,下级使用新站推广彩金盈利提款,一概不出。
Hard rule: If the upper agent has no deposit and the lower member uses new-site promotion bonus to profit and withdraw, do not approve payout.

四、代理提款审核 / Agent Withdrawal Review

4.1 基础检查 / Basic Checks

检查项 / Check Item中文要求English Requirement
注册来源主域名来的代理要特别关注。Pay extra attention to agents registered from the main domain.
充值提款查询代理是否有充值或提款记录。Check whether the agent has deposit or withdrawal records.
成员数量检查代理总成员数量、直推数量和层级关系。Check total members, direct referrals, and hierarchy relationship.
IP查代理邀请人的 IP,上下级是否同 IP,同 IP 用户是否超过阈值。Check inviter IP, upper-lower same IP, and whether same-IP users exceed threshold.
游戏检查是否同一游戏名、同一下注金额、同一玩法手段;后台投注/游戏记录只能查近 7 天。Check whether they play the same game, same bet amount, and same method; backend betting/game records only cover the last 7 days.
奖励查询是否领取宝箱、拼多多等奖励并提取。Check whether treasure-chest, Pinduoduo-style, or other rewards were claimed and withdrawn.

4.2 代理套利模式(非套娃形式)/ Agent Arbitrage Pattern: Non-Nesting

判定条件 / Decision Conditions

  1. 代理同一个小时内注册,且拥有 3 个及以上充值会员。
  2. 首存金额都卡在活动要求的 300。
  3. 统一玩同一个非热门游戏,玩法手段都一样。
  4. 同一 IP 注册或登录用户超过 5 个。

Same-hour registration with 3+ depositing members; first deposits stuck at 300; same non-hot game and same method; same-IP registered or logged-in users exceed 5.

稽核动作 / Audit Actions

  1. 第 1、2 个宝箱可以派发;第 3 个宝箱需检查是否同时满足拼多多派发条件,满足则卡住第 3 个宝箱和拼多多。
  2. 如果代理已输完本金或已有提款记录,扣除所有彩金与盈利。
  3. 如果领取彩金前已有充值和盈利,保留领取彩金前余额,扣除领取彩金后的彩金与盈利。
  4. 将问题代理拉入套利层,设置为人工出款,并做好备注。

Pay the first two treasure chests; hold the third and PDD if conditions match. Deduct all bonus and profit if principal is lost or withdrawal exists. Preserve pre-bonus balance if applicable. Move the agent to arbitrage layer, set manual payout, and remark clearly.

4.3 代理套娃模式 / Agent Nesting Pattern

满足条件 / Conditions说明 / Explanation
层级超过 3(包含 3)一层层往下注册、游戏,形成套娃链。
Hierarchy reaches 3 or more, creating a nested registration/play chain.
存款金额 300-600金额集中卡活动要求。
Deposit amounts are clustered around promotion requirements.
打码 3000-4500卡宝箱危险区间。
Turnover is stuck in the treasure-chest risk range.
线下会员都玩同一款游戏玩法高度一致。
Downline members play the same game with similar methods.
本金存款后已取款,之后才领取邀请宝箱先取本金,再领邀请奖励。
Principal was withdrawn before claiming invitation treasure chest.
每个线下只有一个会员一层层往下注册,结构异常。
Each downline has only one member, creating an abnormal chain.
稽核动作:满足以上所有条件,直接从第三层用户开始,往后所有用户拉进套利层,余额清零。
Audit action: If all conditions are met, starting from the third-level user, move all subsequent users into the arbitrage layer and clear balances.

五、日常审核 / Daily Audit Routine

频率 / Frequency动作 / Action目的 / Purpose
每天用户列表选择注册来源“主域名”并查询,检查当天会员注册时间和 IP 地址。提前发现主域名批量注册或异常来源。
Detect main-domain batch registration or abnormal source early.
发现刷水嫌疑账号后备注:“几月几日嫌疑刷水,审核留意”。下级一并拉到人工出款,等提款时重新查看。提款时加强审核,按情况冻结或拉回。
Strengthen review during withdrawal; freeze or restore based on actual findings.
宝箱活动记录检查会员领取宝箱奖金,以及带来的下级是否正常。识别宝箱套利链。
Identify treasure-chest arbitrage chains.
不定时用户追踪页面查看是否有同时间段代理线下批量注册。有嫌疑的新用户可先拉人工审核,提款时复查是否刷水。
Suspicious new users can be moved to manual review and rechecked during withdrawal.
持续早发现异常,避免亏损。减少平台损失。
Reduce platform loss through early detection.

六、备注与人工审核 / Remarks and Manual Review

备注格式:“几月几号” + “上下级是否同 IP / 是否投注卡宝箱 + 玩法情况” + “稽核人员姓名”。
Remark format: Date + whether upper/lower are same IP or treasure-chest turnover stuck + gameplay situation + auditor name.
场景 / Scenario处理 / Handling
代理邀请人相同 IP必须调整为人工审核,并备注清楚。
Move to manual review and add a clear remark.
拥有 3 个以上下级且投注卡宝箱必须调整为人工审核。
Move to manual review.
代理只带来一个下级投注卡宝箱进入代理管理 -> 代理分析,时间选 30 天,检查是否层层套下。
Go to Agent Management -> Agent Analysis, select 30 days, and check nesting.
发现层层套下发群由上级处理;上下级都要查清楚。
Report to group for superior handling; check both upper and lower agents clearly.

七、培训题库 / Training Quiz

可在 Telegram 群中逐题发出,先让员工回答,再展开答案讲解。

Use these in Telegram group training. Ask staff to answer first, then expand the answer for explanation.

Q1:需要审核的提款订单分为哪三类?

答案:大额、首提、代理。

Answer: large withdrawal, first withdrawal, and agent withdrawal.

Q2:审核大额会员的金额标准是多少?

答案:5000 以上。

Answer: over 5000.

Q3:宝箱活动充值要求是多少?投注危险区间是多少?

答案:充值 300;投注 3000-4500 需要特别留意。

Answer: deposit 300; turnover 3000-4500 is the risk range.

Q4:主域名注册来源为什么要特别关注?

答案:可能出现同时间批量注册、同 IP、多账号或代理链套利。

Answer: it may indicate batch registration, same IP, multi-accounting, or agent-chain arbitrage.

Q5:代理非套娃套利的四个典型条件是什么?

答案:同小时注册且 3 个以上充值会员;首存卡 300;玩同一非热门游戏且玩法一致;同 IP 注册或登录用户超过 5 个。

Answer: same-hour registration with 3+ depositing members; first deposit stuck at 300; same non-hot game and same method; same-IP registered/logged-in users exceed 5.

Q6:代理套娃满足全部条件后怎么处理?

答案:从第三层用户开始,往后所有用户拉进套利层,余额清零。

Answer: starting from the third-level user, move all subsequent users to the arbitrage layer and clear balances.

Q7:发现嫌疑刷水账号,备注怎么写?

答案:“几月几日嫌疑刷水,审核留意”。

Answer: "Date suspected wash betting, audit pay attention."

Q8:上级无存款,下级用新站推广彩金盈利提款,是否可以出款?

答案:一概不出。

Answer: do not approve payout.

Q9:后台投注/游戏记录能查多久?

答案:只能查近 7 天;更早争议需结合账变、订单等数据交叉判断。

Answer: only the last 7 days; older disputes require cross-checking fund changes, orders, and other retained data.