Task

Ps Payment Bot addresses a practical need: a Telegram bot for payment scenarios (digital goods / PlayStation). Python, secure callbacks, and clear messages.

The project is part of commercial development and is actively being developed. It is related to services: Development and integration of solutions for 1C, Chatbots, and process automation.

The case demonstrates the approach to tasks in the area of "Development and integration of solutions for 1C": from requirements gathering to delivery with a clear module structure.

Before starting, we established readiness criteria: a clear first screen, predictable form errors, and the ability to enhance without rewriting half of the codebase.

Solution

A training but fully functional implementation has been made with an emphasis on code readability and reproducible builds.

The scenarios are designed so that the main actions fit within one or two screens: fewer switches, fewer input errors. Navigation and field labels are aligned with familiar patterns—users do not need to "learn the interface".

Particular attention is given to loading states and empty lists: skeleton/spinner where data arrives asynchronously, and clear empty-state texts instead of an empty table.

Architecture and stack

Server and data: Python.

Infrastructure and utilities: Telegram, Payments.

Language distribution in the repository: Python (79%), Shell (20.7%), Dockerfile (0.3%).

Layers are separated so that the UI does not know the details of the transport: API/storage adapters, domain types, presentation components. This simplifies backend replacement and targeted UX adjustments.

Key features

• Python — used in product logic: reduces the amount of custom code and speeds up the addition of new screens.
• Telegram — used in product logic: reduces the amount of custom code and speeds up the addition of new screens.
• Payments — used in product logic: reduces the amount of custom code and speeds up the addition of new screens.

Additionally:

• Integration and use of Python in product logic and interface.
• Integration and use of Telegram in product logic and interface.
• Integration and use of Payments in product logic and interface.

Result

The MVP already covers the key scenario; next steps include expanding reporting, tests, and monitoring.

The source code is open: https://github.com/astropsy999/ps-payment-bot — you can evaluate the module structure and commit style.

What I would improve

The next step is observability (logs/metrics), regression tests, and API documentation for integrators. For high-load scenarios, profiling bottlenecks and caching reference data.