Practical overview
When it fits
Use Walty when a business needs self-custodial stablecoin checkout together with cashier operations, payment reconciliation and refund workflows in a self-hosted web application.
Who it is for
- Businesses accepting stablecoin payments
- Merchant teams operating multiple cashiers
- Developers adapting a TypeScript, MIT-licensed crypto POS
Documented uses
- Create USD-denominated USDC or USDT payment requests
- Share checkout through QR codes and payment links
- Track payment status through on-chain reconciliation
- Handle split payments and refunds
- Assign cashier wallets and collect funds into an owner wallet
Requirements & limits
Walty is presented as a public MIT-licensed repository. The documented deployment options include local development with Docker and a production-style application container using an external PostgreSQL database.
- The default environment exposes Polygon, while the codebase supports Ethereum, Arbitrum, Base, Optimism and Polygon.
- Blockchain-enabled usage requires Alchemy API keys.
- Payment reconciliation requires PAYMENTS_RECONCILE_SECRET.
- The wallet model uses 2-of-3 MPC key generation and transaction-signing ceremonies.
- The local development compose file provides PostgreSQL; the production-style container expects an external PostgreSQL database.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up a local Walty development instance
Prepare the documented local application and PostgreSQL development environment.
Before you start
- Git
- Docker
- pnpm
- A copy of the Walty repository
- Values for DATABASE_URL and JWT_SECRET in the environment configuration
Steps
Clone the Walty repository and change into its directory.
Copy .env.example to .env.
Start the local PostgreSQL service with docker compose -f compose.dev.yml up -d.
Install dependencies with pnpm install, run pnpm db:migrate, and start the development server with pnpm dev.
Open the documented local address, http://localhost:3000.
Expected outcome
A locally running Walty development instance with its database migrations applied.
Guide limitations
- The development compose file starts PostgreSQL only.
- Blockchain-enabled usage additionally requires ALCHEMY_API_KEY and NEXT_PUBLIC_ALCHEMY_API_KEY.
- Payment reconciliation additionally requires PAYMENTS_RECONCILE_SECRET.
- This is a development setup and does not establish production deployment suitability.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 3 October 2026
- Original website title
- ignaciogarcia-dev/walty · Official homepage title · retained in its source language

