A previous release had provenance metadata, but this release does not. View details.
AutopayBot
A powerful, automated payment gateway bot for Telegram.
AutopayBot provides an end-to-end framework to process, track, and manage Telegram-based payments easily. It connects seamlessly to multiple merchant accounts, offering rich features like webhooks, automated receipt tracking, and admin management.
🚀 Features
- Multi-Merchant Support: Connect multiple Telegram bot sessions to act as payment gateways simultaneously.
- Automated Webhooks: Instant and reliable callbacks for successful payments.
- Built-in Admin Dashboard: Rich UI for managing merchants, tracking revenue, and broadcasting messages.
- Database Flexibility: Supports PostgreSQL and SQLite (via SQLAlchemy).
- Interactive CLI: Built-in commands for quick deployments, database migrations, and testing.
🛠 Installation
Install directly via pip:
pip install autopaybot
Note: Requires Python 3.11 or higher.
⚙️ Quick Start
AutopayBot comes with an interactive CLI to get you started in seconds.
1. Initialize Configuration
Run the init command to generate your .env configuration file interactively:
autopay init
2. Setup the Database
Run migrations to set up the default database (SQLite out of the box, configurable via .env):
autopay upgrade
3. Start the Server and Worker
Boot up the REST API and the background Telegram userbot workers simultaneously:
autopay start
🔧 Environment Variables
You can configure the bot by editing the .env file generated by autopay init:
| Variable | Description |
|---|---|
TELEGRAM_API_ID |
Your Telegram App API ID (from my.telegram.org) |
TELEGRAM_API_HASH |
Your Telegram App API Hash |
MANAGEMENT_BOT_TOKEN |
The @BotFather token for your central admin/merchant bot |
ADMIN_TELEGRAM_IDS |
Comma-separated Telegram User IDs for system administrators |
DATABASE_URL |
Database connection string (e.g., sqlite:///payment_system.db) |
API_KEY |
Secret key used to secure incoming REST API requests |
🌐 Production Deployment
AutopayBot provides an automated wizard to generate a docker-compose.yml stack, including an Nginx reverse proxy and Cloudflare Tunnel configuration.
Run the deploy command in your target directory:
autopay deploy
Then start the stack:
docker compose up -d
📄 License
This project is licensed under the MIT License - see the LICENSE file for details.
Metadata
Release files for autopaybot 0.1.32
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| autopaybot-0.1.32.tar.gz | 51.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autopaybot-0.1.32-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 115.6 kB
Release files / autopaybot-0.1.32.tar.gz
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | autopaybot-0.1.32.tar.gz |
|---|---|
| Size | 51.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9d9bbcf6a571b53753e45ff57802f200b8b0bbd667daf2735c93a35c05ae4e55
|
|
BLAKE2b-256 checksum How to use checksums |
eb3e2ed58b257eb59a4cd07d10de13bf0456c03d9ea7878fe42b22cb370b59dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Release files / autopaybot-0.1.32-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | autopaybot-0.1.32-py3-none-any.whl |
|---|---|
| Size | 64.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b8c862496b4e6564ff2bee8a182355953d0a1bed1e9b09ccde6648d795b7a78a
|
|
BLAKE2b-256 checksum How to use checksums |
c152caa2943724807746b7bb790195e1bbea42327930fa1f1a02380398e9346a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Security for autopaybot 0.1.32
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 0.1.31 2 files With provenance
- Added 0.1.32 2 files Without provenance
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.