“No KYC” sounds simple, but payment processing rarely is. A tool may avoid collecting identity documents while still exposing transaction history, depending on outside infrastructure, or creating legal duties for its operator. For US merchants, the practical question is not merely whether a checkout asks for identification. It is who controls the funds, what records exist, and whether the activity resembles regulated money transmission.
This list mixes self-hosted payment software, privacy-oriented protocols, implementation resources, and US compliance references. Inclusion does not mean a service is anonymous, lawful for every use, or permanently free of verification requirements.
Table of Contents
(Click to Toggle)
- Why No-KYC Is Not a Single Feature
- 1. BTCPay Server : Self-Hosted Checkout
- 2. Bitcart : Multi-Currency Payment Server
- 3. LNbits : Lightning Account Layer
- 4. CypherpunkPay : Minimal Merchant Gateway
- 5. AcceptXMR : Monero Payment Library
- 6. Monero Integrations : Checkout Plugins
- 7. Cashu : Ecash Protocol
- 8. Nostr Wallet Connect : Wallet Permission Protocol
- 9. Payjoin Dev Kit : Transaction Privacy Toolkit
- 10. Breez : Lightning SDK
- 11. Bitcoin Design : Payment UX Reference
- 12. Bitcoin Optech : Technical Operations Briefing
- 13. FinCEN : Federal Compliance Reference
- 14. CSBS : State Regulation Map
- 15. NMLS Consumer Access : License Verification
- Bonus Mentions: Useful Checks Around the Payment Stack
- mempool.space : Network Visibility
- OpenSanctions : Public Risk Dataset
- WalletScrutiny : Wallet Build Reviews
- Privacy Guides : Operational Privacy Basics
- Privacy Without Compliance Blind Spots
Why No-KYC Is Not a Single Feature
KYC is an identity-verification process, not a universal property of a payment method. Self-hosted software may collect no documents because there is no payment company between buyer and seller. A hosted wallet, exchange, node provider, or conversion service can introduce separate verification rules.
Limits may also appear indirectly through withdrawal restrictions, transaction monitoring, banking relationships, sanctions controls, or changing terms. US businesses must additionally consider taxes, recordkeeping, consumer protection, and state money-transmitter rules. Receiving payment for your own goods is different from holding or forwarding funds for other people. Professional legal advice may be necessary when those roles overlap.
1. BTCPay Server : Self-Hosted Checkout
What it is: Open-source software for receiving Bitcoin payments directly.
Category: Payment server
Why it stands out:
- Merchant-controlled deployment
- No mandatory intermediary account
Best for: Technical merchants prepared to manage security, backups, and accounting.
2. Bitcart : Multi-Currency Payment Server
What it is: A self-hosted processor supporting several digital-asset workflows.
Category: Open-source checkout
Why it stands out:
- Modular merchant tools
- Direct infrastructure control
Best for: Developers comparing self-custody with hosted processing models.
3. LNbits : Lightning Account Layer
What it is: Software for creating Lightning wallets and payment extensions.
Category: Lightning infrastructure
Why it stands out:
- Extension-based design
- Works with varied funding sources
Best for: Experiments where operators understand custody and node dependencies.
4. CypherpunkPay : Minimal Merchant Gateway
What it is: A lightweight gateway for direct cryptocurrency acceptance.
Category: Self-hosted payments
Why it stands out:
- Compact software footprint
- Emphasis on merchant control
Best for: Small deployments needing a simpler checkout architecture.
5. AcceptXMR : Monero Payment Library
What it is: Developer software for detecting and managing Monero payments.
Category: Payment integration
Why it stands out:
- Designed for direct acceptance
- Avoids shared payment addresses
Best for: Developers who can handle wallet operations and compliance records.
6. Monero Integrations : Checkout Plugins
What it is: Community-maintained integrations for adding Monero to online stores.
Category: Commerce plugins
Why it stands out:
- Platform-specific options
- Focus on direct settlement
Best for: Store owners evaluating plugin code and maintenance status.
7. Cashu : Ecash Protocol
What it is: A Chaumian ecash protocol built around Lightning-connected mints.
Category: Privacy protocol
Why it stands out:
- Private token transfers
- Open protocol experimentation
Best for: Learning about ecash; mint custody remains a central risk.
8. Nostr Wallet Connect : Wallet Permission Protocol
What it is: A protocol connecting applications to Lightning wallets remotely.
Category: Payment connectivity
Why it stands out:
- Granular wallet permissions
- Separates apps from wallet custody
Best for: Developers reducing direct exposure of wallet credentials.
9. Payjoin Dev Kit : Transaction Privacy Toolkit
What it is: Development tools for implementing collaborative Bitcoin transactions.
Category: Privacy engineering
Why it stands out:
- Reduces common transaction assumptions
- Built for application integration
Best for: Experienced teams improving on-chain payment privacy.
10. Breez : Lightning SDK
What it is: Developer infrastructure for embedding Lightning payment functions.
Category: Payment SDK
Why it stands out:
- App-focused components
- Multiple implementation paths
Best for: Builders who will review liquidity, custody, and service dependencies.
11. Bitcoin Design : Payment UX Reference
What it is: An open design guide for Bitcoin wallets and payments.
Category: Design education
Why it stands out:
- Explains unfamiliar payment states
- Covers privacy-aware interfaces
Best for: Teams preventing confusing or unsafe checkout experiences.
12. Bitcoin Optech : Technical Operations Briefing
What it is: Technical reporting on Bitcoin features, wallets, and infrastructure.
Category: Engineering research
Why it stands out:
- Detailed protocol explanations
- Tracks implementation changes
Best for: Operators verifying what payment software actually does.
13. FinCEN : Federal Compliance Reference
What it is: The US bureau publishing guidance on financial-crime obligations.
Category: Government guidance
Why it stands out:
- Primary federal materials
- MSB registration information
Best for: Checking whether an operating model raises federal compliance questions.
14. CSBS : State Regulation Map
What it is: A resource hub for state financial regulatory information.
Category: Regulatory research
Why it stands out:
- State-focused perspective
- Links regulatory initiatives
Best for: Understanding why US requirements can differ by location.
15. NMLS Consumer Access : License Verification
What it is: A public search tool for participating financial license records.
Category: Registration lookup
Why it stands out:
- Searchable company records
- Shows reported state authorizations
Best for: Checking claims made by prospective payment partners.
Bonus Mentions: Useful Checks Around the Payment Stack
mempool.space : Network Visibility
What it is: An open-source explorer showing Bitcoin transactions and fee conditions.
Category: Network analysis
Why it stands out:
- Clear confirmation data
- Self-hosting is supported
Best for: Investigating delays without relying only on checkout status.
OpenSanctions : Public Risk Dataset
What it is: Structured data covering sanctions and politically exposed persons.
Category: Compliance data
Why it stands out:
- Transparent source references
- Machine-readable datasets
Best for: Understanding screening concepts, not replacing professional controls.
WalletScrutiny : Wallet Build Reviews
What it is: Independent research into whether wallet releases match published code.
Category: Software verification
Why it stands out:
- Reproducibility testing
- Documents verification limitations
Best for: Evaluating wallets before using them in payment operations.
Privacy Guides : Operational Privacy Basics
What it is: Community documentation covering privacy tools and threat modeling.
Category: Privacy education
Why it stands out:
- Threat-model approach
- Explains metadata exposure
Best for: Separating practical privacy from unrealistic anonymity claims.
Privacy Without Compliance Blind Spots
No-KYC processing can reduce data collection, but it does not erase public ledgers, server logs, tax records, counterparty risk, or legal obligations. Self-hosting also transfers responsibility for updates, key security, refunds, transaction monitoring, and business continuity to the operator.
For newcomers, the safest evaluation begins with four questions: who holds the funds, who can freeze them, what information leaves the system, and whether money is being handled for someone else. Those answers reveal more than a “no KYC” label ever can.