Deploy Outpay Payment Infrastructure: Web and Worker Services
Deploy the Outpay web application and payment workers with the required environment, health checks, migrations, and graceful shutdown controls.
Before you begin
The application is a Next.js app with Bun-based background workers, PostgreSQL, Redis, Alchemy/Chainstack provider routing, and Railway configuration files. A deployed payment pipeline needs the web service and the payment, reconciliation, and webhook workers to share the same database and queue.
Release steps
- Run migrations and validate the schema.
- Confirm every worker service is deployed with its required environment variables.
- Verify the provider webhook signing key and the merchant-webhook encryption configuration.
- Confirm private Redis networking and database connection ceilings.
- Run the test suite and
bun run build. - Exercise checkout creation, detection, webhook delivery, and failure recovery in a controlled environment before opening the release to real merchants.
Database backup and restore is unverified
Database backup and restore is explicitly recorded as unverified in the deployment record. Treat a completed, tested restore as a release blocker before this deployment handles real customer funds.
Related documentation
- Environment variables — every variable referenced above.
- Operational troubleshooting — diagnosing a failed deployment step.
- Production checklist — the integration-level counterpart to this checklist.
Outpay Environment Variables: API, Database, and Worker Configuration
Configure Outpay application URLs, API settings, database, Redis, blockchain providers, webhook signing, and deployment secrets.
Outpay Operations Security: Payment Workers and Secrets
Apply operational security controls to Outpay deployments, API credentials, databases, queues, blockchain providers, and payment workers.