Description
Summary ## Overview Develop a Telegram bot that allows users to validate, inspect, and activate PUBG Mobile UC codes through integration with Midasbuy (or an alternative integration if an official API is unavailable). The solution should be reliable, secure, easy to maintain, and designed with future expansion in mind. --- ## Functional Requirements ### 1. Code Activation Users should be able to submit a UC code to the bot. The bot should: * validate the code format; * send a request to the integration layer; * process the returned response; * display the result to the user. Supported activation statuses include: * Successfully activated * Already used * Invalid code * Error All activation attempts must be recorded. --- ### 2. Code Validation & UC Value Detection Users should also be able to check a code without activating it. The system should return: * UC denomination (if available); * current code status (Valid, Used, Invalid); * any additional information returned by the integration (for example, region). This is one of the core features of the application and should be implemented as a first-class workflow. --- ### 3. Code Storage Every processed code must be stored in the database. Codes should never be deleted. Instead, maintain their lifecycle using statuses. Each record should contain at least: * Code value * Current status (`New`, `Checked`, `Activated`, `Invalid`, `Error`) * UC amount * Check timestamp * Activation timestamp * Telegram User ID * Last error (if applicable) The storage should preserve a complete history for auditing and troubleshooting purposes. --- ### 4. Duplicate Handling If a submitted code already exists: * do not create a duplicate record; * return the existing information; * avoid unnecessary API requests. Optionally, support a forced re-check initiated by an administrator. --- ### 5. Telegram Inline Mode Support Telegram Inline Mode so users can check codes directly from any chat. Example: `@bot_username CODE` The inline response should display: * UC amount (if available); * current code status. Requirements: * fast response time; * no unnecessary chat messages; * implementation using Telegram InlineQuery API. --- ### 6. Administration Provide administrator functionality directly through Telegram. Required features: * view all stored codes; * filter by status and date; * bulk import codes from text or file; * view statistics including: * total checked; * total activated; * total invalid; * total errors. --- ### 7. Security & Rate Limiting Implement protection mechanisms including: * per-user rate limiting; * anti-spam protection; * user blacklist; * administrator-only access to management functionality. --- ## API Integration Integrate with Midasbuy. The integration layer should properly handle: * API failures; * timeouts; * service-side limitations; * unexpected responses. If an official API is unavailable, implement an alternative integration approach after discussion and approval. --- # Technical Requirements ## Backend Preferred technology stack: * C# (.NET + Telegram.Bot) **(preferred)** * Python (aiogram) * Node.js (telegraf) The project should follow a clean layered architecture with clear separation of concerns, including: * Telegram Bot layer * Business Logic * API Client * Data Access Layer The codebase should remain clean, readable, and maintainable. --- ## Database Use PostgreSQL (preferred) or an equivalent relational database. Design an efficient schema for storing codes, statuses, operation history, and related metadata. --- ## Infrastructure The application should support deployment on a Linux VPS. Docker support is strongly recommended. Include structured logging for diagnostics and monitoring. --- ## Security * Store configuration in environment variables. * Never expose API keys. * Restrict administrative features. * Avoid logging sensitive information, especially UC codes. --- # Non-Functional Requirements The solution should provide: * stable operation; * fast response times; * scalability; * maintainable architecture; * clear project structure. --- # Deliverables The completed implementation should include: * full source code; * database schema and migrations; * setup and deployment documentation; * API integration documentation; * basic test scenarios; * optional deployment assistance. --- # Nice-to-Have If possible, include support for: * Webhook-based updates instead of polling; * caching validation results; * background job processing (e.g. Redis); * future extension into a web-based administration panel. --- # Notes Keep the implementation modular and extensible so additional integrations, features, or management tools can be added with minimal architectural changes. Please also keep in mind that working with PUBG Mobile in-game currency codes may be subject to platform-specific restrictions, and the implementation should gracefully handle those limitations.