Deploy & Connect a Python Telegram Bot + Stripe Payments, Railway, PostgreSQL, Nod/Netlify Functions

MINASTANY GLOBAL LLC UPWORK JOB POST JOB TITLE Deploy & Connect a Python Telegram Bot + Stripe Payments (Railway, PostgreSQL, Node/Netlify Functions) CATEGORY / SETTINGS TO CHOOSE ON UPWORK Category: Web, Mobile & Software Dev → Scripts & Utilities (or Back-End Development) Project type: One-time project Experience level: Intermediate to Expert Budget type: Fixed-price (recommended) — ask for milestone-based payment JOB DESCRIPTION (paste this whole block) I have a complete Python codebase for a financial-education Telegram bot with a companion web app, and I need an experienced developer to deploy it to production and connect payments. WHAT IS ALREADY BUILT (by me): - ~23 Python modules: Telegram bot (python-telegram-bot), FastAPI backend, SQLAlchemy models, scheduled jobs, signal logic, and Stripe subscription scaffolding - Dockerfile, docker-compose.yml, requirements.txt, and a startup script - .env.template listing all environment variables - A live marketing website hosted on Netlify (static HTML) WHAT I NEED YOU TO DO: 1. Deploy the existing Python codebase to Railway (advise if you recommend Render instead) and get it running stably 24/7 2. Provision and connect a PostgreSQL database 3. Configure environment variables (I will provide TEST credentials only) 4. Get the Telegram bot responding to /start, /prices, and /signal using a TEST bot token I provide 5. Get the FastAPI dashboard serving correctly 6. Build the payment flow: a Netlify serverless function (Node.js) that listens for Stripe's checkout.session.completed event, verifies the webhook signature, generates a SINGLE-USE Telegram invite link (member_limit = 1) via the Telegram Bot API, and emails it to the customer via a transactional email provider (Resend, SendGrid, or Postmark) 7. Provide a short written handoff: how to redeploy, where logs live, how to restart, and how to switch from test mode to live IMPORTANT TERMS: - You will work with TEST/placeholder credentials only. I retain all production keys and accounts. - You must sign an IP Assignment Agreement and an NDA before starting (standard documents I will provide). - All code you write or touch becomes the exclusive property of my company. - No external services, telemetry, hidden access, or 'phone-home' calls may be added without my written approval. - I may have the final code independently reviewed before going live. IDEAL CANDIDATE: - Strong Python; proven Railway or Render deployments; python-telegram-bot experience - Comfortable with PostgreSQL, Docker, Stripe webhooks, and Node.js serverless functions - Reads and works within an existing codebase rather than rewriting it - Clear communicator who explains steps in plain language BUDGET & TIMELINE: Fixed-price, milestone-based. Please propose your price and a realistic timeline to get (a) the bot live and stable, and (b) the Stripe-to-Telegram payment flow working end to end. TO APPLY — please answer briefly: 1. Describe a Telegram bot you deployed to Railway or Render (a @username or repo is ideal). 2. Have you connected Stripe webhooks to an automated delivery before? Describe it. 3. Confirm you are willing to sign an IP assignment + NDA and to work with test credentials only. 4. Your fixed price and timeline. Applications that do not mention Telegram and Railway/Render specifically will not be considered.