invoices: multi-crypto payment support
All checks were successful
Build and Deploy to Production / test (push) Successful in 18s
Build and Deploy to Production / build (push) Successful in 49s
Build and Deploy to Production / deploy (push) Successful in 31s

One asset per invoice from a registry (lib/crypto_asset.rb): BTC, LTC,
ETH, XMR, SOL, ALGO, USDT/USDC on ERC-20/TRC-20/BEP-20/Solana/Algorand.
Migration 003 generalizes the ltc_* columns to crypto_* + crypto_coin
(existing LTC invoices backfilled). QR payload adapts per asset: BIP21
amount URIs where supported, bare address for tokens with a network
hint on the PDF. Default addresses come from the CRYPTO_ADDRESSES
secret (JSON code=>address); LTC_ADDRESS still works as legacy.
This commit is contained in:
Sergei Poljanski 2026-07-03 02:01:57 +04:00
commit 0fbb6ee809
Signed by: asxpi
GPG key ID: 4F8851660FA4121B
20 changed files with 410 additions and 143 deletions

View file

@ -11,6 +11,9 @@ SMTP_PASSWORD=change-me
MAIL_FROM="IE Sergei Poljanski Contact Form <me@asxp.io>"
MAIL_TO=ie@asxp.io
# Optional: default Litecoin payout address prefilled into the new-invoice form.
# Production sets this from the LTC_ADDRESS Forgejo secret; leave blank locally.
# Optional: default crypto payout addresses prefilled into the new-invoice
# form. JSON object, CryptoAsset code => address (codes in lib/crypto_asset.rb).
# Production sets this from the CRYPTO_ADDRESSES Forgejo secret.
# CRYPTO_ADDRESSES={"BTC":"bc1...","USDT-TRC20":"T..."}
# Legacy: LTC_ADDRESS still fills the LTC default when set.
# LTC_ADDRESS=ltc1...