Overview
Velt is a crypto payment gateway you host yourself, and you get the full source code. Merchants sign up, verify their business, and bill customers through invoices, payment links, payment channels and subscriptions priced in fiat. Customers pay on a hosted checkout in BTC, ETH, USDC or USDT. Each checkout gets a one-time deposit address from Velt's own HD wallets and locks the rate for 20 minutes. A scanner credits the payment once the chain confirms it. Every movement is posted to a double-entry ledger that merchants can export and operators can reconcile against the chain.
It suits developers and companies who want to run their own crypto payment service, for themselves or for other merchants, without a third-party processor in the middle. The repository contains a NestJS API, a merchant dashboard, a hosted checkout, an operator console, a marketing site, a separate key-holding signer service, Node and Python SDKs, and a WooCommerce plugin. It runs on testnets by default. Mainnet is a setting you turn on yourself once you have a backed-up vault and the licences a payment business needs.
Features
Getting paid
- Invoices: Bill a named customer with a due date in USD, EUR or GBP. The customer can pay with any accepted asset. Invoices can be voided, and the dashboard shows open, overdue and paid views.
- Reminders (dunning): Unpaid invoices get a bounded series of reminder emails. Each one is sent once, and paid or voided invoices are never chased.
- Payment links: Shareable URLs with a fixed or open amount, single-use or reusable, that you can disable at any time.
- Payment channels: A standing deposit address tied to one customer, for retainers, top-ups or marketplace sellers.
- Subscriptions: Billing every N days, weeks, months or years, with the billing day kept steady across short months. Each period raises an invoice and emails it; nothing is pulled automatically. Subscriptions can be paused, resumed or cancelled.
- Customers and products: A customer list and a simple product catalogue for building invoices.
Hosted checkout
- Asset picker: The shopper chooses an asset and network. The page shows the expected time and the number of confirmations for each.
- Payment screen: Exact amount to send, a QR code, the deposit address with a copy button, a 20-minute rate-lock countdown and a "continue on phone" option.
- Live status: Waiting, confirming and paid states, with underpayment and overpayment handling. A merchant can set a small tolerance that covers underpayments.
- Drop-in script:
velt.js opens the checkout in a modal on the merchant's own page, with an onPaid callback. Full-page redirects also work.
- Light and dark themes and the merchant's brand name on the page.
Merchant dashboard
- Home and reports: Available and pending balances, payment volume, items that need attention, and CSV exports of the ledger, orders, invoices, payouts and refunds by date range.
- Excel-safe exports: Byte order mark, hashes and IDs protected from number conversion, and text neutralised against formula injection. Add
?format=raw for a plain machine export.
- Balances and payouts: Available and pending per asset, a destination address book, and withdrawal requests that operators approve.
- Refunds: Full or partial, capped at what actually settled, paid back in the asset the order was paid in.
- Convert: Quote and convert between assets inside the ledger at the configured price feed rate.
- Verification: A business verification (KYB) form with people and document uploads, reviewed by your operators.
- Team and security: Invites with Viewer, Finance, Admin and Owner roles, TOTP two-factor sign-in, password reset, and a test/live environment switch.
- Developers page: Create and revoke scoped API keys (shown once), register webhook endpoints and view the delivery log.
- Search: A command palette (Cmd+K) across invoices, addresses and customers.
Ledger and money handling
- Double-entry journals: Every journal must balance per asset. Balance checks and the writes that depend on them run in one serializable transaction.
- Exact amounts: Integer smallest-unit amounts and a strict decimal parser. No floating point in money paths.
- Chain reconciliation: Compares the ledger with on-chain treasury balances, and reports negative balances instead of hiding them.
- Reorg handling: Confirmation depth per asset. A payment whose transaction disappears is reversed.
- Fees: Per-merchant fee settings that operators can change.
Wallets and custody
- HD wallets: One encrypted seed derives deposit addresses for EVM, Bitcoin and Tron, with a separate derivation branch for each merchant and environment.
- Separate signer:
apps/signer holds the seed on its own host and signs only transactions that pass its allowlist and per-transaction and daily ceilings. The API holds no keys when a signer is configured.
- Sweeps: Deposit addresses are swept into a treasury for each chain family (EVM, Bitcoin, Tron), automatically after settlement or from the ops console.
- Payout controls: A destination allowlist, a single-payout ceiling, a rolling 24-hour ceiling, and an approval threshold above which several distinct operators must sign.
- Seed backup: Shamir secret sharing for the seed, with a recovery rehearsal command.
Compliance tooling
- Sanctions screening: The OFAC SDN list is fetched from the US Treasury and checked when a destination is added, when a payout is raised and again when it is approved, when a payment settles, and when a business submits verification. A match blocks the action, and operators cannot override it.
- Audit trail: Every screening decision is stored with the list checksum and publication date.
- Optional risk scoring: Hooks for a Chainalysis, TRM or Elliptic key. A high score holds a payment for review.
Operator console
- Overview: Queues waiting on an operator, and the state of custody, chain reads and broadcasting.
- Review queues: Approve or reject merchant verification one document at a time. Approve, reject, sign and mark payouts and refunds as sent. Credit a deposit the scanner cannot see.
- Merchants: Activate live mode, set fees, and freeze or unfreeze a merchant.
- Treasury and ledger: Treasury addresses and balances, manual sweeps, and platform ledger balances.
- On-ramps: Settings for Coinbase Onramp, MoonPay and Transak (sandbox or live keys, stored encrypted) so a payer without crypto can buy it at checkout.
- Webhooks: Recent deliveries and failures across merchants.
Developer tools
- REST API: One list format everywhere (
data, hasMore, nextCursor), idempotency keys, and cursors that keep working when rows change between pages.
- OpenAPI:
openapi.json generated from the same Zod schemas the server validates with.
- Signed webhooks: HMAC-SHA256 over a timestamp and the body, a stable event ID, and up to eight retries with exponential backoff.
- SDKs: TypeScript/Node and Python clients with retries, pagination and webhook verification, each with tests.
- Plugins: A WooCommerce gateway with refund support, and a Shopify helper that redirects to the hosted checkout from your own server. It is not a Shopify Payments app.
- Sandbox tools: Simulate a payment or an underpayment in the test environment. These tools are refused on mainnet.
- Observability: A
/health endpoint, Prometheus-style /metrics behind a token, request IDs and alert webhooks.
Supported assets and networks
- Testnet (default): ETH and USDC on Base Sepolia and Ethereum Sepolia, BTC on Bitcoin testnet, and USDT on Tron Nile.
- Mainnet (opt-in with
VELT_NETWORK=mainnet): USDC and ETH on Base and Ethereum, BTC on Bitcoin, and USDT (TRC-20) on Tron.
- No other chains or tokens are built in, such as Solana, Polygon, BNB Chain or Litecoin.
Good to know
- Verified on testnet: A full funded cycle (payment, detection, credit, sweep and payout) has been run with real transactions on Base Sepolia. Bitcoin and Tron payouts and sweeps are covered by offline tests against mocked nodes and a funded-cycle script you can run yourself. None of the chains has been run with real funds on mainnet.
- Conversion is ledger-only: "Convert" moves balances between assets in the ledger at the price feed rate. It does not trade on an exchange or DEX, so you have to manage the real liquidity behind it.
- Manual business verification: Verification is reviewed by your own operators. There is no identity-verification vendor, transaction monitoring, PEP screening or Travel Rule messaging. Sanctions screening is the only automated compliance check.
- On-ramps need your own accounts: Coinbase, MoonPay and Transak work only after you enter keys from your own accounts with them. They are off by default.
- Self-custody is your responsibility: You hold the keys and therefore the funds. Run the signer on an isolated host and back up the seed.
- Licensing: Running a payment service for other merchants can require money-transmitter, VASP or similar licences in your jurisdiction. Getting them and meeting your compliance obligations is the operator's responsibility.
- Marketing site: The marketing pages are a starting point with Velt branding and example copy. Rebrand them before launch.
Tech stack
- API: NestJS 11 on Node.js 22, TypeScript, Zod validation, Drizzle ORM
- Database: PostgreSQL 16, or embedded PGlite for local development
- Front ends: Next.js 15 and React 19 for the dashboard, checkout, ops console and marketing site
- Chains: ethers v6 for EVM, plus Bitcoin and Tron transaction building and signing
- Tooling: pnpm workspaces, Turborepo, Vitest (offline test suite plus opt-in live testnet checks)
- Deployment: Dockerfile and docker-compose (including the signer), a Render blueprint, Railway config and a Coolify compose file
What's included
- Full source for the API, worker, signer, merchant dashboard, hosted checkout, operator console and marketing site
- Shared packages: ledger, custody and chain partners, compliance (sanctions), UI tokens and generated OpenAPI spec
- Node/TypeScript and Python SDKs with tests
- WooCommerce gateway plugin and Shopify integration helper
- Seed and demo-data scripts, testnet cycle and bridge scripts
- Docker, docker-compose, Render, Railway and Coolify deployment files, and a GitHub Actions test workflow
- README, SECURITY.md (configuration, auth, custody and compliance notes), DESIGN.md and a QA report
Requirements and third-party costs
- Hosting (required): A server or platform that runs Node.js 22 and PostgreSQL for five web services, plus a separate private host for the signer on mainnet. Costs depend on your provider.
- Blockchain RPC and explorer endpoints (required): The defaults are public endpoints (Base and Ethereum public RPCs, mempool.space for Bitcoin, TronGrid for Tron). For production, a paid RPC provider such as Alchemy, QuickNode or Infura, and a TronGrid API key, are recommended. An Etherscan API key is optional.
- Price feed (required): CoinGecko's public API by default. A paid CoinGecko plan or your own price URL is recommended in production.
- Network fees (required): Gas and miner fees for sweeps and payouts are paid from your treasury in ETH, BTC and TRX.
- Email (recommended): Resend, Postmark, SendGrid or your own webhook, for invoices, receipts, invites and password resets.
- Alerting (recommended): Any HTTPS endpoint that receives alerts, such as Slack or a pager service.
- Risk scoring (optional): A Chainalysis, TRM Labs or Elliptic contract.
- Fiat on-ramps (optional): Coinbase Developer Platform, MoonPay or Transak partner accounts.
- Licensing and compliance (required for a live service): Legal advice, licences and any KYC/AML vendors your jurisdiction requires.
The purchase covers the source code only. Service fees are billed by the providers listed above.