Final Technical Specification
# Description
The bot automatically tracks new items on the live page, compares prices and parameters, instantly adds the suitable product to the cart, proceeds to the payment method selection step, and stops. Further input of CVV and confirmation is done manually.
# Functionality (briefly)
* Tracking the live feed without reloading in real-time.
* Item selection by filter: name, type, price (min/max or exact), float (range), pattern (number).
* Support for prioritizing sets of filters (drag&drop).
* Instant add to cart → transition to cart → agreement with rules → "Pay" button → card payment selection → stop.
* When multiple matches are found - forming a queue and opening each one in turn in a separate window, so as not to interfere with the current payment. The search continues during payment.
* GUI: panel for managing filters, priorities, and start/stop. Possibility to expand settings later.
# Technical Requirements
* Platform: primary support for Windows. Multiplatform for future deployment on Linux/VPS.
* Speed and stability are a priority. Balance between efficiency and anti-detect mechanics to reduce the risk of bans.
* Minimize browser usage in the search module (reverse-engineering API) for speed if possible. Purchase module - through a real browser.
* Ability to connect/update proxy lists.
# Architecture and Stack
* Search module: Go, multithreading, direct requests to the server (if feasible) for maximum speed.
* Purchase module: Node.js + TypeScript with browser management.
* GUI: Electron with React.js + Material UI.
* Configuration: saved filter sets (JSON), ability to transfer settings.
# Proxy and Deployment
* Two types of proxies: rotating fast for searching; mobile (residential/mobile) for purchase operations.
* Geo recommendation: proxies/VPS closer to the website host (servers in Germany) to reduce latency.
* VPS - optionally in the future. The bot runs locally on Windows. If hosted on VPS, ensure an encrypted channel and do not store payment data on the server.
# Anti-detect and Security
* Emulation of real user behavior during clicks and navigation in the purchase module.
* IP and user-agent rotation. Timings and random pauses within acceptable limits.
* Do not store CVV on disk.
* Logs are minimal. Do not include notifications with payment information.
# UI (minimum set of fields)
* List of filter sets (name, item types, float min/max, pattern, price min/max, priority drag&drop).
* Buttons: Add filter, Edit, Delete, Start, Stop.
* Status indication (searching, found, payment - waiting for CVV).
* Simple proxy and account settings page.
# Filter Logic and Behavior
* By name - simple string inclusion. Support for multiple types simultaneously.
* Float and pattern - numerical ranges.
* Prioritization: top element - highest priority; when multiple appear simultaneously, the bot selects by priority.
* If multiple items are found - they are queued; opened in separate tabs; after completing the payment for the first, the user proceeds to the next without manual refresh.
# Accounts and Sessions
* Working with one account. Manual initialization: authorization and input of contact details before starting.
* If the session is lost - work stops and shows the status "manual login required".
# Logs, Notifications, Debugging
* Minimal logs for reasons of unsuccessful purchases. Storing logs locally.
* Sound/visual indicator of success/error.
# Limitations and Risks
* The site uses Cloudflare and anti-bot mechanics. Possible degradation of the bypass method with future changes in protection.
* Checkout is strictly implemented through the browser module.
* Input of CVV manually.