Skip to content
CUNICULA

BTCPay Server

Self-hosted Bitcoin payments. No middleman, no fees, no KYC.

btcpayserver.org

Self-hosted Bitcoin payments. No middleman, no fees, no KYC.

Common useMerchants accepting BTCMerchants / Privacy ToolsOperator dataHosted
Identity checksZero KYCNo document check recorded · identity exposure level 0/4
Evidence and riskPartial evidenceStandardSome material claims still need confirmation.; no material risk recorded in them.
Last reviewedReviewed 5 Jul 2026KYC checked 13 Mar 2026 · inferred jurisdiction · Source → older source, not independently verifiedHow to cite this pageEvidence confidence59/100
Evidence and facts

Evidence and facts

JURISDICTIONJP
AUDITED BYNo audit listed
OPERATOR DATAHosted operator recorded
EVIDENCE CONFIDENCE
SELF-REPORTED3/3
Why evidence is 59/100Formula 3.1
Source coverageSome material claims still need confirmation
+42
Review ageOldest recorded check is 163 days old
+17

Full scoring method

LAST CHECKED2026-06-24
LAST UPDATED2026-03-13

Specs

DOCUMENT CHECKNone recorded
IDENTITY EXPOSURELevel 0/4
KYC TRIGGERSNo KYC of any kind. You run the server. You control the keys.
FEEFree
CATEGORIESMerchants, Privacy Tools, Agent Money
COMMON USESMerchants accepting BTC, Self-sovereign payments, No-fee transactions
FEATURESSelf-hosted, Open source, Lightning, No fees, No KYC, Non-custodial, Merchant payments, WooCommerce plugin, +1 more
TORNot listed
REGIONSGlobal availability
Review analysis, source material, related services, and history
Agent payments

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.

Protocols
Merchant APIManual
Autonomy1 / agent drafts
CustodySelf-custody
Approval
Human approvalPolicy engineWallet grant
Controls
APIDashboardManual approval
Limits
Spend limitsNo
Merchant lockYes
Category lockNo
Pause / closeYes
WebhooksYes
Privacy
SettlementCrypto / Lightning
FundingSelf-hosted wallet
IdentityNo identity claim
Logging riskMedium
RevocationStrong

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.

Where payment data goes
  1. 1AI agent
  2. 2approval wallet or operator
  3. 3BTCPay Greenfield API invoice
  4. 4self-hosted BTCPay server
  5. 5Bitcoin or Lightning network
  6. 6merchant order record

About

Self-hosted open-source Bitcoin and Lightning payment processor that is non-custodial and charges no fees.

Analysis

OVERVIEW

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.

LIMITS

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.

USEFUL FOR

Merchants who want direct crypto acceptance and are prepared to run infrastructure for it.

Sources · reviewed 2026-07-16

We wrote about this

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.

Related Services

Compare

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.