BT
← All projectsBTCPay Server

BTCPay Server

Free, open-source, self-hosted Bitcoin payment processor supporting on-chain and Lightning payments.

BitcoinLightning NetworkPayment infrastructureNormal
Repository coverage

977 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

125security candidates288second-pass queue413AI analyses
168commits · 30 days
317commits · 60 days
557commits · 180 days
897commits · 365 days
Backfill bands
Aug 8 → Feb 9247 seen22 candidatesComplete
Feb 9 → Jun 9197 seen39 candidatesComplete
Jun 9 → Jul 954 seen0 candidatesComplete
Jul 9 → Aug 865 seen16 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

53/100 average clarity
90Strong · 80–100
213Adequate · 60–79
480Thin · 40–59
194Opaque · 0–39
10security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Nicolas Dorier676793111048
Cerberus622290
Andrew Camilleri (Kukks)2233148
Andrew Camilleri1325160
ndeet111133
Chukwuleta Tobechi33714066
rockstardev33612049
Abhijay Jain26610087
thgO.O32512066
dstrukt726061
Tim522074
tumutech222067
Analysis record

Published AI watches

Last scanned 1 minute ago

Informational 15 AI analysisMessage 18 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Rename attribute

This commit is a simple rename of a code attribute from UseStoreLanguageAttribute to StorefrontRouteAttribute. It only changes the name used in source files and does not alter any program behavior, security settings, or access controls.

5854d8a3by Nicolas Dorier+24−2411 files
No security note in commit
Informational 19 AI analysisMessage 58 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Use server translations on the invoice checkout page (#7828)

This commit changes how the invoice checkout page is translated. Instead of loading translations from separate JSON files in the browser based on a language the customer picks, the page now uses the store's own server-side translation sett…

Removal of client-side language selection reduces attack surface for language-related query-string manipulation (e.g., lang=...)Server-side rendering of checkout strings may reduce exposure to DOM-based XSS via translation files, but no specific vulnerability is shownLarge deletion of locale files and i18next vendor scripts is a cleanup, not a patch
bb14f177by Chukwuleta Tobechi+219−585290 files
No security note in commit
Informational 12 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Update dependency and .NET 10 servicing images (#7831)

This commit updates two .NET runtime/SDK Docker images to newer patch versions and bumps a third-party library (CsvHelper) from 34.0.0 to 34.1.0. These are routine maintenance updates. The commit message does not say any of the updates fix…

Patch-level .NET runtime/SDK image update (potential servicing fixes, unspecified)Patch-level third-party NuGet package update (CsvHelper 34.0.0 -> 34.1.0, unspecified reason)
d5ecad56by Nicolas Dorier+4−43 files
No security note in commit
High 78 AI analysisMessage 45 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Harden account and payment handling

This is a large hardening patch for BTCPay Server that fixes several security weaknesses around account handling, payments, refunds, and plugins. Key changes include: preventing Blazor circuits from staying authenticated after a user's adm…

Blazor circuit principal revalidation against live user stateCookie principal rejection when user is administratively restrictedRefund creation serialized with SELECT FOR UPDATE and single open refund enforcement
20ae3337by Andrew Camilleri (Kukks)+1310−41655 files
Vendor flagged security relevance
Informational 19 AI analysisMessage 58 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Translate remaining public pages and remove invoice checkout language option (#7815)

This commit removes a per-invoice checkout language option and translates more public-facing text so it can be localized. It is a feature-cleanup and internationalization change, not a security fix. There is no evidence of a vulnerability …

1ab0a206by Chukwuleta Tobechi+122−9819 files
No security note in commit
Low 47 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Merge pull request #7780 from tumutech/fix-inventory-counts

This commit fixes a bug where BTCPay Server's Point of Sale and Crowdfund inventory counts could become wrong after unpaid or expired invoices. Previously, the system could add inventory back multiple times for the same invoice, making it …

Business-logic flaw: inventory counts could be inflated by duplicate restocking eventsState-machine fix: previous status now tracked to prevent double-countingRace/ordering concern mitigated by deterministic event-barrier for tests
0ba97eacby Nicolas Dorier+187−1611 files
No security note in commit
Low 44 AI analysisMessage 83 · Strong
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix duplicate inventory returns when expired invoices are marked invalid

This commit fixes a bug in BTCPay Server where marking an already-expired invoice as 'invalid' could cause the app inventory to be restocked twice. The fix tracks each invoice's previous status during status transitions and skips the inven…

Business-logic bug causing duplicate inventory restockingStatus-transition event missing prior-state contextInventory manipulation possible through invoice state changes
6d4beac4by tumutech+187−1611 files
No security note in commit
Informational 24 AI analysisMessage 58 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Apply store’s language on customer-facing pages (#7656)

This commit adds a new store-level setting that lets merchants choose which language customers see on public pages such as invoices, payment requests, and pull payments. It also marks more text on those pages as translatable. There is no d…

New per-request language scoping via AsyncLocal with explicit BeginRequest/Restore disposalSignalR hub now applies store language to controller calls that bypass MVC filtersRouteStoreResolver centralizes route-value-to-store-id lookup with 10-minute sliding memory-cache
55d71e89by Chukwuleta Tobechi+449−10422 files
No security note in commit
Low 29 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Merge pull request #7810 from efeesrefinal/fix/wallet-transaction-filters

This commit fixes two bugs in BTCPay Server's wallet transaction API. First, when users filtered transactions by both status (confirmed/unconfirmed) and label, the same transaction could appear twice in the results because the filtering lo…

Fixes duplicate entries in API query results due to incorrect filter compositionReplaces unsafe uint256.Parse with uint256.TryParse to prevent unhandled exceptions on malformed inputAdds server-side input validation returning structured 404 API error for invalid transaction IDs
867209d1by Nicolas Dorier+27−93 files
No security note in commit
Informational 15 AI analysisMessage 38 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Bump LND to v0.21.8-beta

This commit only updates the version tag of the LND (Lightning Network Daemon) Docker image used in test environments from v0.21.7-beta to v0.21.8-beta. It does not change any production application code, configuration logic, or runtime be…

4bcdc689by r1ckstardev+8−84 files
No security note in commit
Informational 11 AI analysisMessage 35 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Update NuGet dependencies

This commit simply bumps the version numbers of three NuGet packages: a test reporting helper and two FIDO2 authentication libraries. There is no indication in the commit itself that these updates fix a security problem, and no external re…

9951be68by AlfredTheBot69+3−32 files
No security note in commit
Low 34 AI analysisMessage 45 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Update NuGet dependencies and compatibility

This commit updates many third-party software libraries (NuGet packages) to newer versions and makes small code adjustments so BTCPay Server stays compatible with those updates. The most notable security-relevant change is a rewrite of the…

Dependency version bumps for libraries with known security maintenance value (HtmlSanitizer, Fido2, MailKit, Microsoft.AspNetCore, System.Security.Cryptography.Pkcs)Manual CSV field escaping added to prevent formula/CSV injection in wallet transaction exportsFido2 configuration/AppID handling changed during Fido2 library upgrade
bef0935cby Alfred+55−4411 files
No security note in commit
Informational 24 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Merge pull request #7795 from tumutech/fix-api-key-permission-usage-analysis

This commit fixes a crash in BTCPay Server's admin page that shows how an API key has been used. The crash happened when an API key had permissions tied to more than one store. The fix also corrects how usage counts are recorded and displa…

Fixes a UI crash in an administrative API-key usage pageCorrects aggregation of permission usage records when permissions are scoped to specific storesChanges database upsert to persist full permission string including store scope
c9a45b12by Nicolas Dorier+128−484 files
No security note in commit
Informational 22 AI analysisMessage 50 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix API key View Usage crash with multi-store permission usage

This commit fixes a crash in BTCPay Server's admin page that shows how an API key has been used. The crash happened when the same permission (like 'view invoices') was used for more than one store. The fix also corrects how usage counts ar…

Fixes a runtime crash in an administrative API-key usage viewCorrects aggregation of permission usage records that previously could duplicate or conflate store-scoped entriesChanges upsert to persist full permission string including scope, preventing legacy-style policy-only rows from overwriting each other
0ade56dfby tumutech+128−484 files
No security note in commit
Moderate 51 AI analysisMessage 81 · Strong
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix RoundToSignificant for negative amounts (#7782)

This commit fixes a math bug in how BTCPay Server rounds very small negative amounts. Previously, a helper called RoundToSignificant divided by the signed value instead of its absolute value, so negative numbers behaved differently from po…

Rounding/truncation bug in financial amount handlingNegative-amount handling asymmetry that could alter displayed or computed balancesFee-bump calculation could fall below Bitcoin incremental relay fee requirement
6899974aby Amartya Vikram Singh+30−23 files
No security note in commit
Low 49 AI analysisMessage 50 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix missing command in API key authorization

This commit fixes a crash in the API key authorization page. When a user submits the form without clicking either the 'Authorize' or 'Cancel' button, the server tries to read a missing command value, which could cause an error. The fix saf…

Null dereference in request handling pathUnhandled exception could lead to error disclosure or availability impactDefensive null-safety hardening in controller action
0f31ef51by Nicolas Dorier+1−11 file
No security note in commit
Moderate 59 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Merge pull request #7610 from TChukwuleta/ft/manifest-redirect-bcp47

This commit hardens how BTCPay Server downloads translation files from GitHub. It adds checks so the app only fetches files from the project's own trusted GitHub organization, blocks automatic web redirects, and supports a new optional red…

Server-side request forgery (SSRF) protection added: URI host/path validation before outbound fetchAutomatic HTTP redirects disabled for translation update clientManifest redirect field introduced with same-origin/org trust validation
381ad1f0by Nicolas Dorier+223−393 files
No security note in commit
Moderate 60 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Support translation repository redirects and BCP 47 identifiers

This commit hardens how BTCPay Server downloads translation files from the internet. It adds checks so the server only fetches language packs and manifest redirects from the trusted btcpayserver GitHub organization, turns off automatic HTT…

Server-side request forgery (SSRF) hardening: URI scheme, host, and path prefix are validated before outbound fetchOpen-redirect / HTTP redirect abuse mitigation: AllowAutoRedirect set to false on the translation HttpClientPath traversal mitigation: pack file paths resolved as relative URIs and validated against trusted org prefix
896299cdby Chukwuleta Tobechi+223−393 files
Vendor flagged security relevance
Low 29 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Merge pull request #7781 from NicolasDorier/cleanup-pre-1.12-migrations

This commit removes old database upgrade scripts (migrations) from before BTCPay Server version 1.12.0 and replaces them with a single consolidated starting schema. It also trims the startup migration task by deleting obsolete data-convers…

Large-scale deletion of database migration historyConsolidation of cumulative schema into a single init SQL scriptRemoval of legacy data-migration logic from startup task
9fbfc6c5by Nicolas Dorier+542−275243 files
No security note in commit
Low 34 AI analysisMessage 45 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Remove migrations prior to BTCPay Server 1.12.0

This commit is a large database cleanup: BTCPay Server removed all old EF Core migration files before version 1.12.0 and replaced them with a single consolidated SQL script that creates the current schema from scratch. It also trims the st…

Large schema consolidation could silently drop or alter constraints/indexes compared to the incremental migration historyRemoval of legacy migration executors means installations upgrading from very old versions must rely on the consolidated init script and any remaining IMigrationExecutor implementationsNo explicit security claim or CVE reference in commit message or diff
57234d0eby Nicolas Dorier+542−275243 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Security candidateEnsure the seed isn't leaking to user with can sign permission (#7354)by Nicolas Dorier · dffdda64 · May 7, 2026 · 12 filesMessage 58 · ThinHigh 70Details
Commit message · Nicolas Dorier

Ensure the seed isn't leaking to user with can sign permission (#7354)

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
credential or privilege stateseed or entropy pathsigning or wallet pathparser or protocol path
AI analysis · High 70/100

This commit fixes a permission leak in BTCPay Server's hot wallet handling. Previously, users who only had permission to sign transactions ('can sign') could also see the wallet's secret seed phrase, which should be restricted to store administrators. The change introduces a new 'HotwalletSafe' gatekeeper that separates 'can sign' from 'can see seed' and stops the seed from being passed through web forms or displayed to lower-privileged users.

Security candidateAdd granular wallet permissions and move wallet to plugin (#7329)by thgO.O · 1e1d2514 · May 7, 2026 · 70 filesMessage 58 · ThinLow 45Details
Commit message · thgO.O

Add granular wallet permissions and move wallet to plugin (#7329)

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
credential or privilege stateseed or entropy pathsigning or wallet pathparser or protocol path
AI analysis · Low 45/100

This is a large refactoring commit that splits BTCPay Server's wallet functionality into a separate plugin and introduces finer-grained wallet permissions (view, create transactions, sign, broadcast, manage settings, etc.). It also adds new tests that verify users with only wallet permissions can access wallet pages and cannot perform actions outside their role. The change is primarily a security-hardening/permission-separation feature, not an obvious vulnerability fix, though it does include one small bug fix for pending-transaction broadcast matching.

Security candidatefeat: add separate CanSendStoreEmail permission for store email API (#7345)by Abhijay Jain · d64288f1 · May 1, 2026 · 3 filesMessage 85 · StrongLow 32Details
Commit message · Abhijay Jain

feat: add separate CanSendStoreEmail permission for store email API (#7345)

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
credential or privilege state
AI analysis · Low 32/100

This commit introduces a new, more narrowly-scoped permission called 'CanSendStoreEmail' and applies it to the store email-sending API. Previously, sending store emails required the broader 'CanModifyStoreSettings' permission, which also allows changing many other store settings. This change follows the security principle of least privilege: it lets administrators grant API keys or users the ability to send emails without giving them full power to change store configuration. It is a hardening improvement rather than a fix for an active exploit.

Security candidateRefactor: Add btcpay.impersonation.canimpersonate permission (#7327)by Nicolas Dorier · b21a3dd7 · Apr 21, 2026 · 26 filesMessage 70 · AdequateLow 49Details
Commit message · Nicolas Dorier

Refactor: Add btcpay.impersonation.canimpersonate permission (#7327)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
credential or privilege state
AI analysis · Low 49/100

This commit refactors an existing "login code" feature into a new optional plugin called Impersonation. The feature lets an already-logged-in user generate a short-lived QR code/login code that can be used on another device to sign in as the same user. The commit adds a new permission, btcpay.impersonation.canimpersonate, and rules that try to limit impersonation: a user can impersonate themselves, and server admins can impersonate non-admin users but not other admins. The code is a refactor rather than a reported vulnerability fix, but it moves a sensitive authentication capability behind a plugin and a permission check, which is a security-relevant design change.

Security candidateRemove support for importing keys to RPC (#7307)by Nicolas Dorier · 5f64c13a · Apr 11, 2026 · 16 filesMessage 53 · ThinLow 34Details
Commit message · Nicolas Dorier

Remove support for importing keys to RPC (#7307)

53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Low 34/100

This commit removes a feature that let BTCPay Server import wallet addresses and private keys into the Bitcoin node's own wallet ("Import keys to RPC"). The change deletes the user-facing option, the API field, the server policy setting, and all related permission checks. It is a hardening/removal change rather than a fix for an active bug, and the commit message does not describe it as a security vulnerability.

Security candidateAdd LUD-21 (LNURL-pay Verify) support (#7250)by Roxanne · 9ff59327 · Apr 11, 2026 · 8 filesMessage 100 · StrongLow 41Details
Commit message · Roxanne

Add LUD-21 (LNURL-pay Verify) support (#7250)

* Add LUD-21 (LNURL-pay Verify) support

Implements the LUD-21 verify endpoint for Lightning Address payments,
enabling external services to verify payment settlement without
authentication.

Changes:
- New GET /lnurlp/{username}/verify/{paymentHash} endpoint
- Callback response includes verify URL when LUD-21 is enabled
- Payment hashes indexed in search data for efficient lookup
- LUD21Enabled toggle in LNURL payment method config (default: true)
- Settings UI toggle matching LUD-12 pattern
- Swagger API docs updated

Closes #7248

* Use case-insensitive comparison for payment hash in LUD-21 verify

* Address Nicolas review: use AddressInvoices instead of AdditionalSearchTerms

- Replace AddSearchTerms with AddAddressInvoice for payment hash indexing
- Replace TextSearch lookup with GetInvoiceFromAddress in verify endpoint
- Add storeId validation on verify endpoint (cross-store isolation)
- Add payment hash to TrackedDestinations in LightningLikePaymentHandler
- Add rate limiting (ZoneLimits.Verify) to verify endpoint
- Add integration test for LUD-21 verify endpoint flow

* Remove rate limiting from LUD-21 verify endpoint

Rate limiting will be discussed and added in a follow-up.

* Fix verify endpoint: idempotent AddAddressInvoice, normalize payment hash

- Make AddAddressInvoice upsert to avoid duplicate key violations
on (Address, PaymentMethodId)
- Normalize payment hash to lowercase for consistent DB lookups
(store, query, and verify URL generation)

* test(LUD-21): properly exercise cross-store isolation in CanUseLUD21VerifyEndpoint

The previous storeId-isolation assertion did not actually validate the
intended behavior. store2 only had a Lightning Address configured, but
no Lightning node / LNURL payment method. The verify endpoint bails out
with 404 "Not available" at UILNURLController.cs:487-489 before
reaching the invoice-lookup / store-isolation check at L492-494, so the
old assertion would pass even if the isolation logic were broken.

Fix:
- Configure BTC-LN and BTC-LNURL (LUD21Enabled = true) on store2 via
UpdateStorePaymentMethod, mirroring what RegisterLightningNodeAsync
does for store1.
- Strengthen the assertion to also verify the response body's reason
is "Not found" rather than "Not available", proving the request
reached the actual store-isolation branch.

* feat(LUD-21): validate paymentHash is 64 hex chars before lookup

LnurlPayVerify previously accepted any non-empty paymentHash string and
only normalized casing. A Lightning payment hash is exactly 32 bytes /
64 hex characters, so reject anything else up front to avoid pointless
DB lookups on garbage input and return a consistent "Not found"
response shape.

* fix(LUD-21): standardize LnurlPayVerify not-found reason to "Not found"

LnurlPayVerify previously returned three different reason strings for
not-found cases ("Unknown username", "Not available", "Not found"),
which leaks information about which lookup branch failed and was flagged
in CodeRabbit review.

Collapse the username/store-resolution branches to a single "Not found"
reason. The LUD-21 feature-disabled branch keeps its distinct "Not
available" reason because that's a genuinely different operational
condition (feature off vs resource missing) and the new test relies on
the distinction to validate the cross-store isolation path.

* test(LUD-21): fix LN Address fetch path to use /.well-known/lnurlp/{username}

CanUseLUD21VerifyEndpoint was calling /lnurlp/{username} to fetch the
LNURL-pay request, but that path has no route. The actual LUD-16
Lightning Address resolver is published at /.well-known/lnurlp/{username}
(see ResolveLightningAddress in UILNURLController.cs and existing usage
in PlaywrightTests / TestAccount). The wrong path made the test fail at
the very first GET with 404, before the verify endpoint logic could be
exercised at all.

* fix(LUD-21): close TOCTOU race in AddAddressInvoice + harden preimage assertion

CodeRabbit followup:

1. AddAddressInvoice was check-then-insert, so two concurrent LNURL
callbacks for the same (Address, PaymentMethodId) could both observe
existing == null and both attempt to INSERT, causing the second one
to throw on the unique-key constraint. Wrap the insert path in
try/catch (DbUpdateException) and swallow the violation - both
writers are inserting identical data, so the operation is naturally
idempotent under contention. The update branch is kept on its own
SaveChangesAsync so failures there still propagate.

2. The preimage assertion in CanUseLUD21VerifyEndpoint was
Assert.Null(verifyResult["preimage"]?.ToString()), which depends on
how the global JSON serializer handles null values - if the field is
serialized as JSON null instead of being omitted, ToString() returns
the empty string and the assertion fails. Compare against the
JTokenType.Null sentinel directly so the test is robust to either
serializer mode.

* refactor(LUD-21): flush tracked payment hash via UpdatePrompt overload

Consolidates the two-call sequence in the LNURL callback (UpdatePrompt
followed by a separate AddAddressInvoice) into a single UpdatePrompt
call that accepts an optional trackedDestinations list and flushes
AddressInvoices rows inside the same DbContext transaction.

- Ensures the payment-hash index row is written atomically with the
prompt update so a crash between the two calls can no longer leave
the prompt persisted without its verify-lookup row.
- Keeps idempotency under concurrent LNURL callbacks (existing row
check + DbUpdateException swallow, matching AddAddressInvoice).
- Controller no longer reaches into the repository twice for a single
logical state transition.

No behavior change for existing UpdatePrompt callers (trackedDestinations
defaults to null).

* fix(LUD-21): split SaveChanges in UpdatePrompt, exclude concurrency from inner catch

Addresses both items from coderabbit review on dcfdf88:

1. DbUpdateConcurrencyException is a DbUpdateException subtype, so the
inner catch in the trackedDestinations flush would have silently
swallowed concurrency conflicts on the invoice row, breaking the
outer retry loop. Narrowed the inner catch with
'when (ex is not DbUpdateConcurrencyException)'.

2. Batching the prompt blob update and the AddressInvoices insert into
a single SaveChangesAsync meant a unique-key violation on the
tracked destination would roll back the entire unit of work and
silently drop the prompt blob update. Split into two
SaveChangesAsync calls: the blob update runs first and any error
propagates (concurrency still retries via the outer catch); the
tracked-destination flush runs after with its own scoped,
unique-key-only swallow.

* test(LUD-21): cover repeat-callback idempotency and hash validation

Adds three assertions inside the existing CanLNURLPayVerify integration test
to illustrate and guard the UpdatePrompt(trackedDestinations) refactor:

- Repeat LNURL callback with the SAME amount: exercises the idempotent
flush path where the AddressInvoices row for the payment hash already
exists. The second callback must return 200 and the verify endpoint
must still resolve the hash afterward (no duplicate row, no throw).

- Repeat LNURL callback with a DIFFERENT amount: a new payment hash is
minted. The new verify URL must resolve, proving the new hash is
indexed in AddressInvoices and the prompt blob transition persists.

- Verify endpoint with a malformed (non-hex / wrong-length) paymentHash
segment must return 404 with Reason 'Not found' at the 64-hex guard
before any DB lookup is performed.

* Address NicolasDorier review feedback on LUD-21

- Remove username from verify route (/lnurlp/verify/{paymentHash}),
look up store from invoice instead; enables verify for all LNURL,
not only Lightning Address
- Replace EF check-then-act in AddressInvoices with SQL INSERT ON
CONFLICT DO NOTHING (single roundtrip, no partial-dup DbContext
corruption)
- Remove IgnoreAntiforgeryToken on GET route
- Remove payment hash tracking from LightningLikePaymentHandler
(only needed for LNURL path, already handled in UILNURLController)
- Standardize all error responses to "Not found"
- Simplify tests: drop cross-store-via-username and unknown-username
checks (no longer applicable without username in route)

* Address NicolasDorier review: guard trackedDestinations on LUD21Enabled, deduplicate AddressInvoices upsert

- trackedDestinations is now null when LUD21 is not enabled, preventing
unnecessary AddressInvoices rows for stores that don't use verify.
- Extract UpsertAddressInvoice helper to eliminate the duplicated INSERT
SQL across AddAddressInvoice, UpdatePrompt, and NewPaymentPrompt.

---------

Co-authored-by: r1ckstardev <r1ckstardev@users.noreply.github.com>
Co-authored-by: r1ckstardev <me@r0ckstar.dev>

100/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
access controldefensive validation
AI analysis · Low 41/100

This commit adds a new public feature to BTCPay Server called LUD-21, which lets anyone check whether a Lightning Network payment has settled by knowing its payment hash. The feature is enabled by default. The code went through several review rounds that fixed information-leakage issues, race conditions, and input-validation problems. The final version appears reasonably hardened, but because it intentionally exposes invoice settlement status and the payment preimage to unauthenticated callers, it carries a real privacy and operational risk if a merchant does not realize it is on by default.

Security candidatePoS: Any store users can now generate a login QR any other store user (#7303)by Nicolas Dorier · 5062be43 · Apr 9, 2026 · 8 filesMessage 58 · ThinModerate 66Details
Commit message · Nicolas Dorier

PoS: Any store users can now generate a login QR any other store user (#7303)

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · Moderate 66/100

This commit changes how login QR codes are generated for BTCPay Server's Point of Sale (PoS) feature. Previously, only store owners or admins could generate login codes, and there was a warning when selecting a store owner. After this change, any store user can generate a login QR code for any other store user, including store owners, without the previous confirmation step. The commit title itself says this is intentional: 'Any store users can now generate a login QR any other store user.' This appears to be a deliberate feature change, but it weakens access controls around sensitive login credentials.

Security candidatePoS: Unpermissioned store users can browse login links and invoices from Update PoS page (#7305)by Nicolas Dorier · 910cc48b · Apr 9, 2026 · 4 filesMessage 58 · ThinModerate 68Details
Commit message · Nicolas Dorier

PoS: Unpermissioned store users can browse login links and invoices from Update PoS page (#7305)

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
credential or privilege stateboot or update path
AI analysis · Moderate 68/100

This update fixes a permissions issue in BTCPay Server's Point of Sale (PoS) settings page. Previously, store users who only had permission to view settings—but not modify them—could still load the 'Update Point of Sale' page and see sensitive things like invoice lists and login links. The fix makes the page read-only for those users by disabling or hiding edit controls unless the user has modify-permissions. The same permission helper was also extended to cover more HTML elements (buttons, inputs, divs), and a small navigation markup cleanup was done for Crowdfund and PoS menus.

Security candidatefeat: add manual subscription date editing for admins (#7257)by Abhijay Jain · 8ceb55cd · Mar 31, 2026 · 9 filesMessage 100 · StrongLow 30Details
Commit message · Abhijay Jain

feat: add manual subscription date editing for admins (#7257)

* feat: add manual subscription date editing for admins

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: Address code review feedback on subscription date editing

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: Use DateOnly params and normalize to UTC for date editing

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: added tests and API route

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: addressed coding suggestions

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: added null check

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* docs: updated swagger todocument manual subscription date editing

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* Slight adjustment

---------

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>
Co-authored-by: Nicolas Dorier <nicolas.dorier@gmail.com>

100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
boot or update path
AI analysis · Low 30/100

This commit adds a new admin-only feature that lets store administrators manually edit subscription start and expiration dates for subscribers, both through the web interface and the API. It is a normal feature addition, not a vulnerability fix. The code includes basic validation (expiration must be after start) and is restricted to users who already have permission to manage subscribers. There is no direct evidence in the commit that this introduces a security bug, but any date-editing feature could theoretically be misused by a compromised admin account or through authorization bugs.

Security candidateDev: Helps Rider to find Layouts properly (#7283)by Nicolas Dorier · c0e58290 · Mar 27, 2026 · 21 filesMessage 53 · ThinInformational 15Details
Commit message · Nicolas Dorier

Dev: Helps Rider to find Layouts properly (#7283)

53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit is a developer-experience tweak. It changes how Razor view files reference their page layouts so that the JetBrains Rider IDE can find them more reliably. It also updates a test assertion style and bumps the C# language version from 12 to 14. There is no security-relevant change.

Security candidatefix(email): skip SMTP AUTH when Login and Password are empty (fixes #7267) (#7269)by Drake Thomsen · 94320733 · Mar 25, 2026 · 1 fileMessage 98 · StrongInformational 22Details
Commit message · Drake Thomsen

fix(email): skip SMTP AUTH when Login and Password are empty (fixes #7267) (#7269)

When SMTP is configured via IP relay (e.g. Google Workspace relay) without
login credentials, BTCPay still calls AuthenticateAsync if the server
advertises AUTH capability, causing 535 errors.

Skip authentication when both Login and Password are empty.

Co-authored-by: Storm Knight <storm-knight@openclaw.ai>

98/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
access controlcredential or privilege state
AI analysis · Informational 22/100

This commit fixes an email-sending bug in BTCPay Server. When an administrator configured an SMTP relay that does not require a username or password, BTCPay was still trying to log in if the server said it supported authentication. That caused unnecessary 535 authentication errors and prevented emails from being sent. The fix simply skips login when both the Login and Password fields are empty. There is no security vulnerability here; it is a reliability/configuration fix.

Security candidateAllow upgrade/downgrade of a subscription at period endby Chukwuleta Tobechi · ea7bb40b · Mar 22, 2026 · 12 filesMessage 50 · ThinInformational 20Details
Commit message · Chukwuleta Tobechi

Allow upgrade/downgrade of a subscription at period end

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
update trust
AI analysis · Informational 20/100

This commit adds a new feature to BTCPay Server's subscription plugin that lets users schedule a plan upgrade or downgrade to take effect at the end of their current billing period, instead of happening immediately. It also lets users cancel a scheduled change. The change is a normal feature addition and does not appear to fix or introduce a security vulnerability based on the code shown.

Security candidatefix: Cross-store privilege escalation to approved pull payments/payouts in GreenfieldPullPaymentController (#7244)by Cerberus · 3c839152 · Mar 15, 2026 · 1 fileMessage 90 · StrongHigh 81Details
Commit message · Cerberus

fix: Cross-store privilege escalation to approved pull payments/payouts in GreenfieldPullPaymentController (#7244)

Co-authored-by: Cerberus Merlin <merlin@cerberus.security>

90/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
credential or privilege state
AI analysis · High 81/100

This commit fixes a privilege escalation bug in BTCPay Server's Greenfield API. Two authorization checks were passing 'null' instead of the actual store ID when verifying whether a user could auto-approve pull payments or payouts. In BTCPay Server's authorization system, a null resource likely causes the check to fall back to a global permission evaluation, meaning a user who only had permission on one store could potentially approve or auto-approve pull payments/payouts for other stores where they should have been denied. The patch simply passes the correct storeId so the permission is scoped properly.

Security candidatefix: Broken Access Control: Private form access and invoice creation on other stores via unscoped authorization check (#7236)by Cerberus · e7cd630b · Mar 13, 2026 · 1 fileMessage 90 · StrongHigh 74Details
Commit message · Cerberus

fix: Broken Access Control: Private form access and invoice creation on other stores via unscoped authorization check (#7236)

Co-authored-by: Cerberus Merlin <merlin@cerberus.security>

90/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
access control
AI analysis · High 74/100

This commit fixes a broken access control bug in BTCPay Server's form feature. Previously, when checking whether a user could view a private form, the system asked 'Is this user allowed to view store settings anywhere?' without specifying which store. That meant any user with store-settings permission for any store could see private forms belonging to other stores, and could potentially create invoices against those stores. The patch changes the authorization check to include the specific store ID of the form, so users must have permission for that exact store.

Security candidateInclude API key - permission analysis for improved security (#6771)by Chukwuleta Tobechi · b253df29 · Mar 10, 2026 · 11 filesMessage 96 · StrongInformational 21Details
Commit message · Chukwuleta Tobechi

Include API key - permission analysis for improved security (#6771)

* Include API key - permission analysis for improved security

resolve codderbyte

Remove designer class

fix review feedback

include text translate

avoid string parsion and use Permission directly

use permission against string

include translation and update selecte stores

Include tests for api key permission edit and usage

.Update api key analysis page

include test

delete key usage when deleting api key

* update layout and delete query

96/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
credential or privilege state
AI analysis · Informational 21/100

This commit adds a new feature that tracks which permissions each API key actually uses and shows the owner a dashboard of used, unused, and stale permissions. It is a security-hardening and visibility improvement, not a fix for an active vulnerability. The change also deletes usage records when an API key is removed.

Security candidateCleanup unused namespacesby Nicolas Dorier · 1633275d · Mar 8, 2026 · 372 filesMessage 35 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Cleanup unused namespaces

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet pathboot or update pathauthentication pathparser or protocol path
AI analysis · Informational 15/100

This commit removes unused C# 'using' statements (imported namespaces) and one unused Razor view import across 372 files. It is a code-cleanup change with no functional modifications. The only non-cleanup hunk is a tiny refactor in GreenfieldInvoiceController.UpdateInvoice that reorders an existing null check and variable assignment without changing behavior.

Security candidateRefactor: User User.GetId instead of using the UserManagerby Nicolas Dorier · be7f3f04 · Mar 8, 2026 · 44 filesMessage 62 · AdequateLow 34Details
Commit message · Nicolas Dorier

Refactor: User User.GetId instead of using the UserManager

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Low 34/100

This is a large internal code cleanup that replaces calls to ASP.NET Core's UserManager for getting the current user's ID with a new direct helper that reads the value from the user's identity claims. Most changes are mechanical refactors across many controllers and views. There are a few small behavior changes worth watching: the new helper returns an empty string instead of "???" for missing users, some places now treat a missing user ID as a validation failure rather than passing it through, and a couple of user-not-found cases now return NotFound instead of throwing an exception. The commit does not describe itself as a security fix and no external advisory is provided.

Security candidateFix PermissionTagHelper to behave in the right scope when in nav barby Nicolas Dorier · d6bec86c · Mar 7, 2026 · 14 filesMessage 50 · ThinLow 49Details
Commit message · Nicolas Dorier

Fix PermissionTagHelper to behave in the right scope when in nav bar

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
credential or privilege stateauthentication path
AI analysis · Low 49/100

This commit fixes how BTCPay Server's navigation bar decides which store's permissions to use when showing or hiding menu items. Previously, the permission checks inside the navigation bar could accidentally use the store from the main page (for example, the server settings page) instead of the store selected in the navigation bar. This could cause menu items to be shown or hidden incorrectly. The change makes the navigation bar temporarily switch to the correct store context while it renders, and removes a caching shortcut that could reuse the wrong permission result. There is no direct evidence in the commit message or diff that this was exploited or reported as a security vulnerability.

Security candidateDo not add claims twice for cookie authby Nicolas Dorier · e34d8d7d · Mar 6, 2026 · 1 fileMessage 50 · ThinLow 26Details
Commit message · Nicolas Dorier

Do not add claims twice for cookie auth

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Low 26/100

This commit fixes a small bug where a special permission claim was being added to a user's identity every time it was transformed, instead of only once. Repeated claims are harmless in most cases, but could in theory cause the identity to grow unexpectedly or lead to subtle authorization behavior. The fix checks whether the permission claim already exists before adding it again.

Security candidatePluginize permissionsby Nicolas Dorier · 14837e6c · Mar 6, 2026 · 70 filesMessage 18 · OpaqueModerate 51Details
Commit message · Nicolas Dorier

Pluginize permissions

18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
credential or privilege stateauthentication path
AI analysis · Moderate 51/100

This is a large refactoring commit that reworks how permissions are defined and enforced in BTCPay Server so that plugins can register their own permissions. It moves the permission hierarchy out of a hard-coded static class into a runtime service, changes how store context is tracked during requests, and updates authorization handlers. The change is architectural rather than a targeted security fix, but any mistake in the new permission logic could allow users to access stores or functions they should not.

Security candidateDecrease logs about challenged authentication schemesby Nicolas Dorier · 54056a40 · Mar 2, 2026 · 2 filesMessage 55 · ThinInformational 15Details
Commit message · Nicolas Dorier

Decrease logs about challenged authentication schemes

55/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
access control
AI analysis · Informational 15/100

This commit simply turns down the volume on log messages coming from BTCPayServer's security components. It changes the logging level from the default (likely Information/Debug) to Warning, so routine 'authentication scheme challenged' messages no longer fill the logs. There is no code behavior change, no bug fix, and no security vulnerability being patched.

Security candidateRefactor: Move Bitpay stuff in its own pluginby Nicolas Dorier · 39d99f0b · Feb 27, 2026 · 55 filesMessage 57 · ThinLow 35Details
Commit message · Nicolas Dorier

Refactor: Move Bitpay stuff in its own plugin

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Low 35/100

This commit is a large code refactor that moves BTCPay Server's Bitpay-compatible API from the core application into a separate plugin. It relocates controllers, authentication, models, views, and middleware into a new Plugins/Bitpay folder, updates tests and dependency injection, and replaces the old middleware-based Bitpay API detection with a new endpoint selector policy. The change itself is structural rather than a targeted security fix, but any large refactor of authentication and routing code carries a risk of accidentally changing access-control behavior.

Security candidateRefactor: Move translations classes in its own pluginby Nicolas Dorier · 64d5a893 · Feb 20, 2026 · 26 filesMessage 62 · AdequateInformational 15Details
Commit message · Nicolas Dorier

Refactor: Move translations classes in its own plugin

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · Informational 15/100

This commit is a routine code reorganization: it moves BTCPay Server's translation/localization code from the core server project into a dedicated 'Translations' plugin. The same dictionary-management features, language-pack download, and localization services are preserved, just relocated. There is no indication of a security fix or vulnerability being addressed.

Security candidateFix: Can't upgrade/downgrade a Lifetime subscription (#7194)by Nicolas Dorier · 41295c17 · Feb 19, 2026 · 2 filesMessage 70 · AdequateInformational 20Details
Commit message · Nicolas Dorier

Fix: Can't upgrade/downgrade a Lifetime subscription (#7194)

Fix #7193

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
update trust
AI analysis · Informational 20/100

This commit fixes a JavaScript crash in the subscription portal. When a user had a lifetime subscription, the page did not show an auto-renewal checkbox, but the script still tried to attach an event listener to it. That caused a browser error that blocked the rest of the page's JavaScript, making it impossible to upgrade or downgrade the subscription. The fix simply checks whether the checkbox exists before attaching the listener. There is no direct security vulnerability here; it is a functional bug with a minor denial-of-service-like effect on the UI.

Security candidateMerge pull request #7185 from Abhijay007/feat/updateTranslationsby Abhijay Jain · 0df82d8a · Feb 16, 2026 · 6 filesMessage 73 · AdequateLow 29Details
Commit message · Abhijay Jain

Merge pull request #7185 from Abhijay007/feat/updateTranslations

feat: added ability to update translations

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
boot or update pathmerge-commit duplicate discount
AI analysis · Low 29/100

This commit adds a feature that lets BTCPay Server administrators download and update language translation packs from a GitHub repository. The code fetches JSON translation files over the internet, stores them in the server's database, and tracks whether a newer version is available. There is no clear security bug in the diff, but the design introduces a supply-chain and server-side request risk that should be reviewed carefully.