Adamant-im/adamant-payment: aDAMANT Payment (adamant-payment) is a self-hostable platform that combines

Universal crypto-first platform for payments, subscriptions and software license management.

ADAMANT Payment (adamant-payment) is a self-hostable platform that combines authentication, billing, crypto payments, subscriptions, license management, a customer portal, and an operator admin console — in one product-neutral solution.

No need to stitch together Stripe, a licensing SaaS, and custom auth. Built for Web3 projects, trading bots, desktop apps, and SaaS products that sell to a global audience and accept Bitcoin, ADAMANT, and other cryptocurrencies.

Note: This repository is the public home for the project overview, roadmap, and community discussion. The application source code is maintained in a private repository and is not open source.

Interested in using ADAMANT Payment? Contact us

Related: Community discussion · Release tracking (#1)

Why ADAMANT Payment

Crypto-first by design

Cryptocurrency payments are a first-class feature — not a bolt-on. BTCPay Server (BTC), ADM-native on-chain deposits, and extensible payment providers fit naturally into checkout and settlement flows.

All-in-one platform

Auth, billing, payments, subscriptions, license management, user portal, and admin panel in one stack. One deployment, one data store, one integration surface for your product.

Built-in licensing for software

Licenses are issued automatically after payment. Manage expiration, plans, trials, and promo codes. External apps — bots, relays, desktop clients — validate access through a dedicated API.

Flexible sign-in: email or crypto-only

Users sign in with email + password, ADM message code, or Ethereum wallet (SIWE). Web3-friendly flows without mandatory email identity.

Included frontend and admin panel

Customers manage payments, licenses, and subscriptions. Operators manage accounts, orders, plans, wallets, and access rights from a separate admin console.

Universal and product-independent

Not tied to ADAMANT Messenger or any single app. White-label branding via environment configuration. Generic product slugs in the data model.

API-first architecture

REST API under /v1/... for bots, SaaS backends, relays, and desktop applications. Check license status, subscription validity, and user access programmatically.

Self-host friendly and data-controlled

Deploy on your own infrastructure (PostgreSQL, Node.js). Full control over users, payment logic, licenses, and business data.

No dependence on closed platforms

Unlike Stripe, Paddle, Lemon Squeezy, or traditional licensing SaaS, ADAMANT Payment adapts to your crypto payment flows, pricing models, and product rules.

Security built in

Separate user and admin surfaces, protected authentication, secure license validation APIs, optional ADM 2FA and ETH 2FA for operators, captcha, rate lockout, and audit logging.

User portal

Sign in with email, ADM, or Ethereum wallet. Browse plans, pay with crypto, and manage scoped licenses.

Sign-in screen: email, ADM message code, or Ethereum (SIWE) wallet authentication.

Ethereum sign-in via SIWE — connect wallet and sign a challenge message.

Product catalog with configurable paid plans and exchange / trading-pair scope.

Customer view: active licenses, trial claims, and subscription status.

Crypto checkout via BTCPay Server — BTC invoice linked to license issuance.

Operator admin console

Full operator dashboard for accounts, licenses, invoices, and payment wallets. Deploy on a separate origin in production.

Admin dashboard: revenue metrics, license counts, and ADM/BTC wallet balances.

Operator license list with filters, manual issuance, and payment metadata.

Paid and pending invoices across accounts and payment providers.

Use cases

First production integration: ADAMANT Tradebot WebUI subscription (adamant-tradebot).

v1.0 highlights

Full scope and release checklist: Issue #1.

Contact

Planning to integrate ADAMANT Payment into your product, bot, or SaaS?

Get in touch → adamant.business/contact

We welcome feedback on payment providers, licensing models, and integration scenarios in the community discussion.

Technical overview

adamant-payment/
├── apps/
│   ├── api/          # Fastify 5 + Prisma + PostgreSQL — source of truth
│   ├── web/          # End-user UI (login, plans, checkout, licenses)
│   └── admin/        # Operator UI (separate deploy / IP allowlist)
├── packages/
│   └── shared/       # Zod schemas, types, API client, i18n
└── config/           # Hot-reloaded paid plans, promo codes, exchanges