Email aliasing, self-hostable, crypto accepted.
BTCPay Server
Self-hosted Bitcoin and Lightning payment processing.
btcpayserver.org
- No routine KYC
- Evidence and facts →
Self-hosted Bitcoin and Lightning payment processing.
Evidence and facts
Evidence and facts
active · medium · recorded 2026-08-24
Upgrade to v2.4.3 or later, especially on shared multi-user servers; the release does not claim a confirmed compromise. This is a security release; updating is recommended for servers shared with many users.
Specs
Review analysis, source material, related services, and history
Spend controls and data exposure
Greenfield supports invoices, webhooks, store-scoped API permissions and revocable keys. Signing and payout approval depend on wallet and server configuration.
Server operators can access invoice records. Hot wallets keep signing material on the server; external-wallet signing follows a different data path.
- 1AI agent
- 2approval wallet or operator
- 3BTCPay Greenfield API invoice
- 4self-hosted BTCPay server
- 5Bitcoin or Lightning network
- 6merchant order record
- BTCPay Server homepageprovider
- BTCPay Greenfield APIcontrols
- BTCPay wallet docscustody
About
Self-hosted open-source Bitcoin and Lightning payment software with no processor fee. Hosting and network costs still apply.
Analysis
Self-hosted open-source Bitcoin and Lightning payment software with no processor fee. Hosting and network costs still apply.
The 2.4.2 advisory confirms stolen funds from exposed LND credentials on older versions. BTCPay on-chain wallets were outside that flaw, but LND's own on-chain funds could be at risk. A software fix does not prove every affected user's funds were recovered.
Merchants who want direct crypto acceptance and are prepared to run infrastructure for it.
Frequently Asked Questions
Is identity verification required?
No identity verification is recorded for typical use. The software has no identity-document requirement. Hosts, merchants and optional payment services can set their own account and verification rules.
Where is it available?
Recorded availability: GLOBAL.
Is the operator based in a Five Eyes country?
The jurisdiction is not publicly confirmed. Check the provider site for incorporation details.
How are identity, operator, and evidence fields reported?
Identity exposure is level 0 of 4. Hosted operator data has not been established. Jurisdiction is shown as context, not a safety verdict. Source coverage is partial evidence, last reviewed 2026-10-25, and recorded risk is caution.
Sources and history
Evidence basis: Claims on this page are linked to published sources for comparison, not certification, audit, endorsement, or recommendation; read the methodology and coverage map before relying on an entry.