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 52 minutes 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 candidateFix: TOTP 2FA bypass via Greenfield Basic auth (#7491)by Nicolas Dorier · c173a919 · Aug 4, 2026 · 1 fileMessage 75 · AdequateHigh 78Details
Commit message · Nicolas Dorier

Fix: TOTP 2FA bypass via Greenfield Basic auth (#7491)

75/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✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
explicit security languageaccess controlauthentication path
AI analysis · High 78/100

BTCPay Server fixed a bug where accounts protected only by TOTP-based two-factor authentication (the six-digit code from an authenticator app) could log into the Greenfield API using just their email and password, skipping the second factor entirely. The code previously blocked basic login only for users with FIDO2/hardware-key second factors, not for users with app-code (TOTP) second factors. The vendor says this was reported by Ben Carman and shipped as an emergency fix in version 2.4.2.

Security candidateCover all generated witness PSBTsby rockstardev · ede7cc70 · Aug 3, 2026 · 3 filesMessage 45 · ThinModerate 57Details
Commit message · rockstardev

Cover all generated witness PSBTs

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Moderate 57/100

This commit changes how BTCPay Server decides whether a Bitcoin transaction input is a SegWit (witness) type when building PSBTs (Partially Signed Bitcoin Transactions). Previously the code only recognized three specific SegWit formats: native SegWit pay-to-pubkey-hash, native SegWit pay-to-script-hash, and Taproot. The new code uses a broader check that covers any script type classified as a witness script, including possible future SegWit versions. It also adds calls to fill in the 'witness UTXO' field in two wallet controller flows that previously did not do so. The practical effect is to make PSBTs more complete and compatible with future Bitcoin upgrades, and to reduce the chance that a wallet or signer will fall back to less secure non-witness data handling.

Security candidatePreserve imported PSBTsby rockstardev · 31ad661a · Aug 3, 2026 · 1 fileMessage 28 · OpaqueLow 35Details
Commit message · rockstardev

Preserve imported PSBTs

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 35/100

This commit removes a single line that automatically added witness UTXO data to SegWit inputs when decoding a PSBT. The change is titled 'Preserve imported PSBTs,' suggesting the previous behavior was modifying user-supplied transaction data in an unwanted way. Without more context, it is unclear whether this is a security fix or a functional/data-integrity change. The removed operation could, in some PSBT workflows, alter the information a hardware wallet or signer sees, which can affect how transactions are validated or signed.

Security candidateInclude witness UTXOs in SegWit PSBTsby rockstardev · 63236df4 · Jul 30, 2026 · 4 filesMessage 45 · ThinLow 45Details
Commit message · rockstardev

Include witness UTXOs in SegWit PSBTs

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 45/100

This commit changes BTCPay Server so that when it builds or decodes Partially Signed Bitcoin Transactions (PSBTs), it explicitly adds a compact 'witness UTXO' record for any SegWit inputs. Previously, some SegWit PSBTs may only have carried the full previous transaction (non-witness UTXO). Adding the witness UTXO improves compatibility with hardware wallets and signers that require or prefer it, and can reduce the data those devices need to process. The change itself is a correctness/compatibility improvement rather than an obvious vulnerability fix, but the absence of witness UTXOs in SegWit PSBTs can cause signing failures or force fallback behaviour in some wallets.

Security candidateAddress pending signature retry review feedbackby rockstardev · 89b8f49c · Jul 29, 2026 · 2 filesMessage 50 · ThinLow 26Details
Commit message · rockstardev

Address pending signature retry review feedback

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
signing boundarysigning or wallet path
AI analysis · Low 26/100

This commit is a follow-up code review patch for BTCPay Server's pending Bitcoin transaction (multisig) signing feature. It tightens when the service logs a warning versus a debug message after a failed finalization attempt, and it removes an unused optional parameter from an internal helper method. The changes are defensive: they reduce false-warning noise and make the per-input signature tracking more accurate. There is no direct evidence in the commit of an exploitable vulnerability being fixed.

Security candidateBound pending multisig signature historyby rockstardev · eb0f15ca · Jul 28, 2026 · 2 filesMessage 50 · ThinLow 35Details
Commit message · rockstardev

Bound pending multisig signature history

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
signing boundarysigning or wallet path
AI analysis · Low 35/100

This change tightens how BTCPay Server stores signature attempts for multi-signature Bitcoin transactions. Previously, every submitted PSBT (a partially signed transaction file) was kept in history, even if it added no real progress. Now only PSBTs that actually advance signing or successfully finalize the transaction are retained. This prevents unbounded growth of stored signature history, which could waste storage and potentially be abused to clutter or inflate a pending transaction record.

Security candidateFix pending multisig signature retriesby rockstardev · ebeafc5a · Jul 28, 2026 · 2 filesMessage 50 · ThinLow 42Details
Commit message · rockstardev

Fix pending multisig signature retries

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
signing boundarysigning or wallet path
AI analysis · Low 42/100

This commit fixes a bug in BTCPay Server's multisig transaction handling. Previously, the service could get stuck in a 'Pending' state even when enough valid signatures had been collected, because it discarded new signature submissions that didn't immediately improve progress and didn't retry finalizing the transaction. The fix keeps distinct-but-not-yet-helpful PSBTs (partially signed transactions), records them, and retries finalization each time a new PSBT arrives, allowing later valid signatures to complete the transaction.

Security candidateAdd race condition safe InvoiceRepository.UpdateMetadata (#7475)by Nicolas Dorier · 5664bd41 · Jul 22, 2026 · 10 filesMessage 58 · ThinLow 40Details
Commit message · Nicolas Dorier

Add race condition safe InvoiceRepository.UpdateMetadata (#7475)

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 · Low 40/100

This commit changes how BTCPay Server stores invoice comments and metadata. Previously, comments were saved in a separate field and could be updated with a method that was not safe when multiple requests happened at the same time. The patch moves comments into the invoice metadata and uses database-level JSON operations to update only the requested field, reducing the chance that simultaneous updates overwrite each other. It also removes the dedicated 'comment' field from the public API, so comments can only be updated through the UI or via metadata. The commit title explicitly calls this a race-condition safety fix.

Security candidatefeat: embed plugin directory in plugin management (#7381)by thgO.O · 5da26940 · Jul 17, 2026 · 29 filesMessage 70 · AdequateLow 38Details
Commit message · thgO.O

feat: embed plugin directory in plugin management (#7381)

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
boot or update path
AI analysis · Low 38/100

This commit refactors BTCPay Server's plugin management into a dedicated plugin and adds an embedded plugin directory that loads content from an external plugin catalog via an iframe. The change moves plugin URLs from the server settings area to a new plugin area, adds URL sanitization for author and documentation links, and introduces checks to prevent installing mismatched plugin identifiers. It is a feature/refactoring commit rather than a disclosed security fix, though it includes some defensive hardening.

Security candidateAdd BIP-329 wallet label import (#7457)by Atharva Borade · 856967c3 · Jul 16, 2026 · 7 filesMessage 53 · ThinInformational 21Details
Commit message · Atharva Borade

Add BIP-329 wallet label import (#7457)

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
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 21/100

This commit adds a feature that lets BTCPay Server users import wallet labels from a BIP-329 file. The code parses uploaded JSONL files, validates entries, and attaches labels to transactions, addresses, or transaction outputs. The change is a normal feature addition; there is no direct evidence in the commit that it fixes a security vulnerability, but it does introduce a new file-upload and parsing path that should be reviewed for robustness.

Security candidatefeat : add rtl language support with custom css (#7428)by Tim · 8ba284ce · Jul 15, 2026 · 11 filesMessage 58 · ThinInformational 15Details
Commit message · Tim

feat : add rtl language support with custom css (#7428)

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 · Informational 15/100

This commit adds right-to-left (RTL) language support to BTCPay Server. It introduces metadata tracking for whether a language is RTL, fetches that flag from the translation manifest, stores it in the database, and switches the user interface to RTL-specific CSS stylesheets when an RTL language like Arabic is active. There is no security issue visible in the change.

Security candidateRename <vc:breadcrumb> (#7456)by Nicolas Dorier · 7d206d93 · Jul 14, 2026 · 106 filesMessage 43 · ThinInformational 15Details
Commit message · Nicolas Dorier

Rename <vc:breadcrumb> (#7456)

43/100 · ThinMessage clarity
✓ Descriptive subject✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet pathboot or update pathauthentication path
AI analysis · Informational 15/100

This commit is a routine UI refactor: it renames the internal ASP.NET Core view component from <vc:breadcrumb> to <vc:title-header>, updates CSS class names, and standardizes how page titles are set across many Razor views. There is no security-relevant change in behavior—no new endpoints, no permission changes, no input handling changes, and no fixes for injection or bypass issues.

Security candidateRefactor breadcrumb (#7455)by Nicolas Dorier · eac04593 · Jul 14, 2026 · 47 filesMessage 43 · ThinInformational 15Details
Commit message · Nicolas Dorier

Refactor breadcrumb (#7455)

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

This commit is a routine user-interface cleanup. It replaces many copies of hand-written breadcrumb navigation HTML across the application with a single shared 'Breadcrumb' view component. There is no security-relevant change here—only the way page headers and navigation links are rendered.

Security candidateAdd editable invoice comments (#7444)by dstrukt · 4eaae5bd · Jul 13, 2026 · 17 filesMessage 86 · StrongInformational 21Details
Commit message · dstrukt

Add editable invoice comments (#7444)

* Add editable invoice comment metadata and include it in the invoices report export

* Add invoice comment viewing and editing to the details page and invoice list

* Test invoice comment saving, list view, and export

* Use SQL rather than EF

* Add comment to the greenfield API

---------

Co-authored-by: Nicolas Dorier <nicolas.dorier@gmail.com>

86/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathboot or update path
AI analysis · Informational 21/100

This commit adds a new editable comment field to BTCPay Server invoices. Store staff can add private notes to invoices through the web interface or API, and these comments appear in invoice reports. The change is a normal feature addition, not a security fix. There is no indication in the commit that it addresses any vulnerability or security incident.

Security candidateShow missing permission in 403 page (#7387)by Nicolas Dorier · 09493a99 · Jun 3, 2026 · 4 filesMessage 53 · ThinInformational 15Details
Commit message · Nicolas Dorier

Show missing permission in 403 page (#7387)

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
credential or privilege state
AI analysis · Informational 15/100

This change is purely a user-experience improvement: when a BTCPay Server user is denied access to a page, the 403 error page now tells them which specific permission they are missing. It does not alter who can access what, nor does it fix or introduce any security vulnerability. It simply makes the denial message more informative.

Security candidateInclude configuration for tax on tips (#7298)by Chukwuleta Tobechi · 5a025a84 · Jun 2, 2026 · 16 filesMessage 76 · AdequateInformational 19Details
Commit message · Chukwuleta Tobechi

Include configuration for tax on tips (#7298)

* Include configuration for tax on tips

* Ensure null and 0 result in no tip tax

* mirroring tax in tip scenario in CanUsePOSKeypad.

* Format tip tax receipt

* Update

* fix coderabbit suggestion

* Include tip tax to report, and remove tax from product information

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
boot or update path
AI analysis · Informational 19/100

This commit adds a new optional 'tax on tips' feature to BTCPay Server's Point of Sale app. Merchants can now configure a separate tax rate that applies to customer tips, and the receipt/cart display breaks out the tip tax separately from regular item tax. There is no indication this is a security fix; it is a normal business-logic feature addition.

Security candidateRemove recovery codesby Nicolas Dorier · 9010e3bd · Jun 1, 2026 · 14 filesMessage 28 · OpaqueLow 35Details
Commit message · Nicolas Dorier

Remove recovery codes

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Low 35/100

This commit removes the 2FA recovery-code feature from BTCPay Server. Recovery codes are normally printed when you enable two-factor authentication and used as a backup way to log in if you lose your phone. After this change, users can no longer create or use those codes. The commit does not add a replacement backup login path, so anyone who loses access to their authenticator app may be permanently locked out of their account unless they have another login method configured. The change is presented as a feature removal, not as a fix for a specific security bug.

Security candidateAdd loginless and passwordless passkey authenticationby Lucas Cullen · 28604914 · Jun 1, 2026 · 52 filesMessage 55 · ThinModerate 59Details
Commit message · Lucas Cullen

Add loginless and passwordless passkey authentication

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 controlauthentication path
AI analysis · Moderate 59/100

This commit adds passkey (passwordless) and login-code login support to BTCPay Server and rewrites much of the existing two-factor/FIDO2/LNURL-auth login flow. It is a large feature patch, not a documented security fix. The changes introduce several security-relevant design choices: passkeys can bypass the password entirely, session state now carries the login method and return URL, and the migration forces TwoFactorEnabled=true for all users while adding a separate AuthenticatorEnabled flag. Because the patch is broad and partially refactored, there is a non-trivial risk of authentication bugs (e.g., bypasses, session confusion, or incorrect 2FA enforcement), but the supplied diff does not show an obvious exploitable vulnerability.

Security candidatefeat: allow max stores per user (#7320)by Abhijay Jain · e6708c47 · May 19, 2026 · 14 filesMessage 80 · StrongInformational 22Details
Commit message · Abhijay Jain

feat: allow max stores per user (#7320)

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

80/100 · StrongMessage clarity
✓ 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
boot or update path
AI analysis · Informational 22/100

This commit adds a new feature that lets server administrators set a maximum number of stores each non-admin user can create, both globally and per-user. It is a new restriction/control feature, not a fix for an existing vulnerability. There is no evidence in the commit or supplied references that this change addresses a security incident or was disclosed as security-relevant.

Security candidateUnnest UI views of PullRequests, PullPayments, Invoices and Apps (#7368)by Nicolas Dorier · c7c90625 · May 19, 2026 · 24 filesMessage 58 · ThinLow 38Details
Commit message · Nicolas Dorier

Unnest UI views of PullRequests, PullPayments, Invoices and Apps (#7368)

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
authentication path
AI analysis · Low 38/100

This commit restructures several user-interface pages so that payment requests, pull payments, invoices and apps no longer live under a '/stores/{storeId}/...' URL path. Instead they use flatter routes such as '/payment-requests/{id}/edit'. The change also updates the authorization layer so that when a store-scoped route is missing but an object ID is present, the system can fail the request with a 403 rather than letting the action itself silently return a 404. Several tests were updated to expect 403 instead of 404 for missing objects, and some permission-guard tests were removed or changed. The commit is described by the author as a UI route cleanup, not as a security fix, but it does touch access-control code.

Security candidateAllows merchants configure tax inclusion or exclusion (#7290)by Chukwuleta Tobechi · 8da2cad6 · May 18, 2026 · 9 filesMessage 91 · StrongInformational 19Details
Commit message · Chukwuleta Tobechi

Allows merchants configure tax inclusion or exclusion (#7290)

* Allows merchants configure tax inclusion or exclusion

* fix typo

* Include tests plus populate invoice metadata with tax included

* resolve failing test with view model

* fix: Form amount diff is misclassified as tax-included

* rerun build

* removed @ from the tax helper text

91/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
Why it was queued
boot or update path
AI analysis · Informational 19/100

This commit adds a new merchant setting that lets a store choose whether entered prices already include sales tax or whether tax should be added on top. It updates the Point of Sale screens, order calculation logic, and tests. There is no indication in the commit that this fixes a security vulnerability; it appears to be a normal feature addition for tax handling.

Security candidateServer-side translation manager: install, update, and remove language packs from the BTCPay UI (#7347)by Tim · af7f6204 · May 18, 2026 · 21 filesMessage 100 · StrongModerate 60Details
Commit message · Tim

Server-side translation manager: install, update, and remove language packs from the BTCPay UI (#7347)

* refactor : change dictionary/ies to translation/s

* migrate LanguagePackUpdateService to manifest-based fetching

* refactor : translations UI

* test : add tests

* fix : coderabbit comments

* fix(translations): verify downloaded language pack SHA-256 against manifest

LanguagePackUpdateService.FetchLanguagePackFromRepository previously
returned the manifest's Sha field as the version without ever hashing
the downloaded translation content. The manifest's Sha is SHA-256 of
the source file content, but the value was never compared against the
download, allowing a tampered or corrupted file that still parses as
valid JSON to be saved as a valid language pack.

This change downloads the file as bytes, computes SHA-256, and compares
case-insensitive against the expected Sha from the manifest. On
mismatch, throws InvalidOperationException so the controller's existing
error path returns a user-visible failure instead of silently writing
bad data.

Add LanguagePackUpdateService_RejectsLanguagePackOnShaMismatch test
covering the rejection path. Update the existing
LanguagePackUpdateService_FetchesLanguagePackFromManifest test to use
the actual SHA-256 of the test fixture so the happy path also exercises
the new verification step.

* fix(translations): preserve all old /server/dictionaries paths via catchall

The previous backward-compat shim only handled GET /server/dictionaries
with a single redirect; the seven other old routes (create, edit by id,
select, delete, download) returned 404 under the new controller. The PR
description's promise to "preserve existing integrations and prevent
breaking changes for legacy clients" therefore did not match what was
shipped.

Replace the single-route redirect with a catchall route that captures
any /server/dictionaries/* subpath and 308-permanent-redirects to the
equivalent /server/translations/* URL, preserving the HTTP method (so
POST clients re-POST to the new endpoint instead of degrading to GET).
The existing GET /server/dictionaries handler stays for the bare list
URL.

Also remove the redundant DeleteTranslation action: both it and
UninstallLanguagePack POST routes called localizer.DeleteTranslation
with identical TempData; only UninstallLanguagePack is referenced from
the view. Keep the named route the view uses, drop the dead one.

* fix(translations): restore typed-confirmation modal for Uninstall

ListDictionaries.cshtml had a _Confirm modal requiring the user to
type "Delete" to enable the destructive action; the new
ListTranslations.cshtml replaced it with a single-click submit button
that fired immediately on click. Custom translation packs are
irreversible without re-import and may represent hours of user-edited
entries; one accidental click on the wrong row was enough to lose them.

Restore the typed-confirmation modal pattern used elsewhere in
UIServer (LndSeedBackup, ListUsers, SSHService): replace the inline
form with a link that opens #ConfirmModal, supplying the per-row
description and the "Delete" confirm-input. Add the _Confirm partial
at the end of the view.

Restore the corresponding two test steps in the Playwright integration
test: ConfirmInput.FillAsync("Delete") + ConfirmContinue.ClickAsync()
between the row-Delete click and the alert-message assertion.

* fix(translations): manifest fetch back-off, narrow exception, more tests

Three small fixes on the LanguagePackUpdateService surface:

1. Back-off on manifest fetch failure. Under sustained upstream
outage, every translations-page hit was retrying the manifest
URL because FetchManifest only cached on success. Add a 60-second
back-off after any fetch failure: subsequent calls within the
window throw immediately, which the existing GetManifestLanguages
degraded path translates to a graceful empty response. Stops
the retry hammer without changing the steady-state contract.

2. Narrow the catch in CheckForLanguagePackUpdate. The broad
catch (Exception) loses information about why an update check
fails. Narrow to the four exception types we actually expect to
silence: HttpRequestException, TaskCanceledException,
InvalidOperationException (manifest-back-off + missing-Languages),
and Newtonsoft.Json.JsonException. Programming errors and
unexpected runtime faults bubble up instead of silently
producing "no update available."

3. Three more unit tests filling test coverage gaps:
- LanguagePackUpdateService_ReturnsDegradedModeOnMalformedManifest
covers the JsonReaderException path through the degraded mode.
- LanguagePackUpdateService_ReturnsDegradedModeOnMissingLanguagesKey
covers the InvalidOperationException for a manifest payload
without the expected Languages array.
- LanguagePackUpdateService_ThrowsArgumentExceptionForUnknownLanguage
covers the FetchLanguagePackFromRepository unknown-language
path.

All 8 unit tests pass on .NET 10 RC.2; build clean.

* fix(translations): server-side uninstall guards + duplicate-name tolerance + casing

Address CodeRabbit re-review findings on the previous iteration:

1. UninstallLanguagePack endpoint now validates server-side instead of
relying solely on the UI hiding the Uninstall button. A crafted POST
to /server/translations/{translation}/uninstall could otherwise
delete any translation, including built-in defaults or the currently
selected one. Now: NotFound if the translation does not exist; an
error TempData message if Source != "Custom" or if the translation
is currently selected as the server's display language. The localizer
call only fires when all three guards pass.

2. ListTranslations manifest indexing uses TryAdd instead of
ToDictionary. The previous .ToDictionary call would throw
ArgumentException if upstream manifest contained duplicate or
case-variant Name values, breaking the translations page hard
instead of degrading gracefully. First-wins semantics keep the page
functional even on a malformed upstream payload.

3. CheckForLanguagePackUpdate compares the remote and local SHA hex
strings case-insensitively. The corresponding compare in
FetchLanguagePackFromRepository was already case-insensitive; this
aligns the update-check path with the verification path.

4. SetTranslation test helper asserts the translation is non-null
before saving. Failure mode is now local to the helper rather than
surfacing as a confusing NullReferenceException downstream when
fixture setup changes.

Build clean, 8/8 unit tests pass on .NET 10 RC.2.

* fix(translations): NicolasDorier review pass

- Drop the Translator/ URL prefix from RawBaseUrl. The upstream
fix for issue #7341 in btcpayserver-translator removed the
Translator/translations symlink redirect; raw.githubusercontent.com
does not follow symlinks for file requests, so the existing
RawBaseUrl pointed at a 404. Now resolves against
main/translations/<file>.json directly.
- GetManifestLanguages no longer swallows exceptions. Returns the
entry array directly; caller (UITranslationController) wraps in
try/catch and sets degradedMode locally.
- Drop unused server-side GetAvailableLanguages.
- Cache the parsed LanguageManifestEntry[] for 1 hour so repeat
Translations page hits skip both the http call and the JSON
projection.
- Tests updated to match the new signature + URL.

* fix : coderabbit comment

* little UI fix

* fix(translations): NicolasDorier round-2 review - IMemoryCache + Newtonsoft deserialization

Address Nicolas's 5 inline comments on LanguagePackUpdateService.cs
(PR #7347, head d1f8d3c):

- Replace manual JObject field-picking in ToManifestEntry with
Newtonsoft deserialization to a typed DTO (ManifestLanguageDto +
ManifestRootDto). Maintainer "handle|url" split + Updated parse
live in a single static factory LanguageManifestEntry.FromDto.
Public API of LanguageManifestEntry unchanged (Name, Native,
MaintainerHandle, MaintainerUrl, Updated as DateTimeOffset?,
File, Sha) so callers (UITranslationController) need no edit.
- Collapse the two hand-rolled tuple caches (_manifestCache,
_entriesCache), the SemaphoreSlim _manifestLock, and the
_manifestNextFetchAllowedAt failure-backoff field into a single
IMemoryCache entry keyed "translations.manifest" with a 1h
absolute expiration. The per-language _updateCheckCache
ConcurrentDictionary moves to the same IMemoryCache for
consistency, keyed "translations.update.<language>".
- Drop the 60s failure backoff. If GitHub raw is down, surface
the error per-request rather than holding a sticky-error
window. Faster recovery, no fake-error responses when the
remote has already recovered.

Service constructor now takes (IHttpClientFactory, IMemoryCache);
IMemoryCache is already registered globally via
Startup.AddMemoryCache(), so DI wiring needs no change.

File drops from ~200 to ~140 lines. 8/8 LanguagePackUpdateService
unit tests pass; tests updated to pass a MemoryCache instance.

* fix : differentiation between languagepack and custom

* chore : update default translations

* update translation text

---------

Co-authored-by: r1ckstardev <r1ckstardev@users.noreply.github.com>
Co-authored-by: rockstardev <rockstar@btcpayserver.org>

100/100 · StrongMessage clarity
✓ Specific, 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
signing boundarydefensive validationboot or update path
AI analysis · Moderate 60/100

This commit adds a server-side translation manager to BTCPay Server and, in the process, fixes several security-relevant bugs. The most important fix is that downloaded language packs are now verified against a SHA-256 hash from a manifest, preventing a corrupted or tampered translation file from being accepted. The commit also adds server-side guards so built-in or currently-selected translations cannot be uninstalled by a crafted request, restores a typed 'Delete' confirmation before removing custom translations, and redirects old URL paths to new ones so existing integrations keep working. Most of the change is a feature refactor (renaming 'dictionaries' to 'translations' and moving to a manifest-based system), but the security hardening is explicitly described in the commit message and diff.

Security candidateAllow server admin to specify if an invited user subscribes for monetization or not (#7318)by Chukwuleta Tobechi · 53ba1427 · May 11, 2026 · 15 filesMessage 91 · StrongInformational 21Details
Commit message · Chukwuleta Tobechi

Allow server admin to specify if an invited user subscribes for monetization or not (#7318)

* Option for server-invited users to bypass subscription

* fix code rabbit and include tests

* fix coderabbit test suggestion

* allow for skipping monetization on invite

* code rabbit suggestion

* clean up

* resolve redundant code

* remove view data

* resolve feedback from Nicolas

* restore tests that was removed

91/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
Why it was queued
boot or update path
AI analysis · Informational 21/100

This commit adds a new server-admin-only option called 'Bypass monetization.' When a BTCPay Server instance charges users for subscriptions, admins can now mark specific invited or existing users so they do not need a paid subscription to log in. The change is intentional and exposed through the admin UI; it does not appear to be a hidden backdoor. There is no direct evidence in the commit that it fixes a security bug or introduces a vulnerability, but any feature that lets an admin exempt users from billing controls should be reviewed for authorization and audit-trail completeness.

Security candidateAdd granular API permissions for on-chain wallets (#7357)by thgO.O · 4a03202a · May 8, 2026 · 5 filesMessage 81 · StrongLow 40Details
Commit message · thgO.O

Add granular API permissions for on-chain wallets (#7357)

* refactor(wallets): align greenfield routes with wallet policies

* fix(wallets): keep payjoin psbt unfinalized before request

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarycredential or privilege statesigning or wallet path
AI analysis · Low 40/100

This commit introduces more fine-grained permission checks for BTCPay Server's on-chain wallet API. Previously, many wallet operations required broad 'modify store settings' or 'view store settings' permissions. Now, operations are gated by dedicated wallet permissions such as viewing wallet data, managing wallet settings, creating/signing/broadcasting transactions, and managing wallet transactions. The change also fixes a Payjoin bug where the PSBT was finalized before the Payjoin request, which could break Payjoin flows. Overall, this is a hardening/security improvement rather than an introduced vulnerability.

Security candidateMove Wallet ViewModels (#7355)by Nicolas Dorier · 2a9efb52 · May 7, 2026 · 49 filesMessage 43 · ThinInformational 15Details
Commit message · Nicolas Dorier

Move Wallet ViewModels (#7355)

43/100 · ThinMessage clarity
✓ Descriptive subject✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet pathparser or protocol path
AI analysis · Informational 15/100

This commit is a large but straightforward code reorganization: it moves wallet-related view model classes from one namespace/folder (BTCPayServer.Models.WalletViewModels) into a new plugin-specific location (BTCPayServer.Plugins.Wallets.Views.ViewModels) and updates all references accordingly. There is no functional change to how the application behaves, no security fix, and no vulnerability introduced in the diff itself.