Email aliasing, self-hostable, crypto accepted.
BTCPay Server
Self-hosted Bitcoin payments. No middleman, no fees, no KYC.
btcpayserver.org
- Zero KYC
- JP
- Evidence and facts →
Self-hosted Bitcoin payments. No middleman, no fees, no KYC.
Evidence and facts
Evidence and facts
Why evidence is 59/100Formula 3.1
- Source coverageSome material claims still need confirmation
- +42
- Review ageOldest recorded check is 163 days old
- +17
Specs
Review analysis, source material, related services, and history
Spend controls and data exposure
Useful as a self-hosted invoice and merchant-payment rail for agent workflows. It avoids platform custody and KYC, but wallet funding, network history, server logs, and merchant order records still need separate controls.
The safer pattern is agent-drafts, operator-or-policy-signs. Do not put seed material or broad wallet keys in the same runtime that browses, prompts, or receives untrusted task input.
- 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 processor that is non-custodial and charges no fees.
Analysis
A self-hosted payment processor: merchants accept Bitcoin and Lightning directly to their own keys, with no fees, no intermediary, and no KYC anywhere in the architecture.
Self-hosting is the cost: server operations, key management, and uptime fall on the merchant, and using a third-party host reintroduces exactly the intermediary the software removes.
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. No KYC of any kind. You run the server. You control the keys.
Which payment methods are accepted?
Please check the provider site for accepted payment methods.
Where is it available?
Recorded availability: GLOBAL.
Is the operator based in a Five Eyes country?
No. The recorded jurisdiction is JP, which is not a Five Eyes country. This is jurisdiction context and does not by itself establish that a service is safer or less safe.
How are identity, operator, and evidence fields reported?
Identity exposure is level 0 of 4. A hosted operator is recorded. Jurisdiction is shown as context, not a safety verdict. Evidence confidence is 59/100 and recorded risk is standard.
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.