danops-1/gpt-agreement-paymentChatGPT Plus/Team/Pro 订阅协议端到端重放工具集 · hCaptcha 视觉求解器 · 反欺诈机制实证研究 / End-to-end protocol replay toolkit for ChatGPT Plus/Team/Pro subscription with from-scratch hCaptcha solver and empirical anti-fraud research
简体中文 | English
End-to-end replay tool for ChatGPT Plus / Team subscription agreements: reverse-engineered from packet capture the entire chain Stripe Checkout → PayPal / GoPay / QRIS → ChatGPT manual-approval → Codex OAuth + PKCE and implemented as a runnable client. Includes a from-scratch hCaptcha visual solver, PayPal fraud detection early-exit branch, and a set of empirical anti-fraud mechanism data collected from real execution.
| Logo | Name | Description | Website |
|---|---|---|---|
 | lukyface API (Author-run Relay Station) | Unified AI model aggregation / distribution gateway (based on new-api), OpenAI / Claude / Gemini protocol interconversion, self-use surplus sharing. Author-run, long-term stable. Open to everyone · Author-run relay station exchange group: 1104565621 | https://api.lukyface.com/register?aff=9ipF |
👆 Click the image to visit lukyface · Invite code 9ipF · Exchange group 1104565621
[!CAUTION] Using this project constitutes acceptance of all terms in
NOTICE. The project is provided AS IS, with no warranties, and the maintainers assume no responsibility. Authorized use only on systems you own / legitimate CTF / authorized bug bounty in-scope assets / security research. Strictly prohibited for fraud, payment evasion, bulk account creation for resale, violation of third-party ToS, unauthorized targets. All legal responsibility rests with the user. If you do not accept these terms, do not use.
Supports four subscription activation paths:
| Path | Entry Point | Use Case |
|---|---|---|
| Team / Plus (PayPal billing agreement) | pipeline.py --paypal | Stripe Checkout → PayPal billing agreement → ChatGPT manual approval |
| Plus (promo long link + PayPal agreement auth) | scripts/no_card_paypal_plus.py | OpenAI official promo campaign long link + PayPal guest checkout completing billing agreement protocol |
| Plus / Team (GoPay Indonesia) | pipeline.py --gopay | Midtrans linking + GoPay wallet binding, IDR region exclusive |
| Plus / Team (QRIS scan) | pipeline.py --qris | Midtrans QRIS, remote preview + reference polling settlement |
Given a clean proxy + payment credential, run the command to completion and get the OAuth refresh_token.
Four points worth examining:
webui/backend/parallel_runner.py). Same phone across multiple workers serializes OTP phase using advisory lock, pre/post-OTP fully parallelized; DB atomic claim + placeholder INSERT prevents multiple workers contending for same promo_link / same inventory email. Frontend configures phone pool (M rows) + concurrency N (can exceed M), worker maps to phone pool via i % M round-robin.CTF-pay/hcaptcha_auto_solver.py, ~4000 lines, independently usable). VLM primary path + CLIP/OpenCV heuristic fallback + Playwright human action synthesis, covers 12 known hCaptcha question types.docs/anti-fraud-research.md.pipeline.py::daemon()). Webshare API auto IP rotation (webshare jitter fallback to /tmp/gost_last.json cache), CF DNS quota cleanup, tmpfs orphan recovery, gost relay watchdog, DataDome slider auto-drag. Design goal is unattended operation for weeks.flowchart LR
A[pipeline.py / webui] --> B[CTF-reg/<br/>browser_register.py<br/>Camoufox + Turnstile]
B --> C[CTF-pay/card.py<br/>Stripe Checkout replay]
C --> D{Payment path}
D -->|paypal| E1[Camoufox / Node RPA<br/>PayPal billing agreement]
D -->|gopay| E2[Midtrans linking<br/>+ WhatsApp OTP]
D -->|qris| E3[QRIS QR<br/>+ remote preview]
E1 --> F[Stripe poll<br/>state=succeeded]
E2 --> F
E3 --> F
F --> G[Camoufox second login<br/>Codex OAuth + PKCE]
G --> H[refresh_token<br/>output/webui.db (SQLite)]
For detailed subsystem decomposition, file organization, and protocol chain details, see docs/architecture.md.
To be frank, this is not an out-of-the-box tool. Running through the entire pipeline requires at least:
Full end-to-end setup typically takes 1–3 hours for initial configuration tuning. Once daemon mode runs stably, a single pipeline takes ~5 minutes; concurrent mode with 2 workers on the same phone generates 2 accounts in ~3 minutes.
Code is research-oriented, organized by protocol stage, and doesn't prioritize maximum readability.
Compress 1–3 hours of manual configuration into ~15 minutes. 14-step wizard + real-time preflight self-checks + built-in runtime controller (SSE log stream + concurrency panel) generate CTF-pay/config.auto.json + CTF-reg/config.paypal-proxy.json configurations.