Skip to content

Create btcpay-server-2-4-0.md - #76

Merged
pavlenex merged 11 commits into
masterfrom
2-4-0
Jun 25, 2026
Merged

Create btcpay-server-2-4-0.md#76
pavlenex merged 11 commits into
masterfrom
2-4-0

Conversation

@pavlenex

Copy link
Copy Markdown
Contributor

This PR is ready to be reviewed by contributors. I'd appreciate 👀 eyes on features you were particularly in charge of. Please make a direct suggestion to the text, so we can move faster with the review.

To-do:

  • Add details around translations
  • Add featured image
  • Embed videos
  • Plugin updates section (if there are any notable updates cc @TChukwuleta)

@netlify

netlify Bot commented Jun 23, 2026

Copy link
Copy Markdown

Deploy Preview for btcpayserver-blog-preview ready!

Name Link
🔨 Latest commit e6accd3
🔍 Latest deploy log https://app.netlify.com/projects/btcpayserver-blog-preview/deploys/6a3d234569df08000824dc8a
😎 Deploy Preview https://deploy-preview-76--btcpayserver-blog-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Comment thread blog/_posts/btcpay-server-2-4-0.md

Passkeys work alongside existing login methods, so you can adopt them gradually. Users who prefer traditional login flows can continue using them, while those with modern devices and browsers can switch to a smoother passwordless experience.

## 🛡️ Guided Multisig Wallet Setup

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@thgO-O Please review this section for accuracy and let me know what's missing by making an direct suggestion.


This is a major usability improvement for teams, organizations and businesses that want shared custody without relying on a third-party coordinator. BTCPay can now help coordinate the setup flow while keeping the signing model self-custodial.

## 🔑 Granular Wallet Permissions

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@thgO-O Please review this section for accuracy and let me know what's missing by making an direct suggestion.

Comment thread blog/_posts/btcpay-server-2-4-0.md
Comment thread blog/_posts/btcpay-server-2-4-0.md
Comment thread blog/_posts/btcpay-server-2-4-0.md Outdated
Comment thread blog/_posts/btcpay-server-2-4-0.md
@TChukwuleta

TChukwuleta commented Jun 23, 2026

Copy link
Copy Markdown
Member

Hey @pavlenex

Regarding plugin update there are three notable ones

Two new integration for this release:
LightSpeed point of sale and Jumpseller e-commerce integrations

Plugin update:
Satoshi Tickets now supports API access and discount codes (discount codes requested by Adopting Bitcoin in Arnhem).

I can add the following directly if it sits well:

New E-commerce & Point of Sale Integrations
BTCPay Server's reach continues to grow with two new integrations that bring Bitcoin payments to more merchants where they already sell.
The new Lightspeed integration lets merchants accept Bitcoin and Lightning payments directly at the Lightspeed Retail point of sale. For physical shops already running one of the most widely used retail POS systems, this means adding Bitcoin at the counter without changing how they operate, and with funds settling straight to their own wallet.

The new Jumpseller integration brings the same to online stores. Merchants running a Jumpseller storefront can now accept Bitcoin through BTCPay Server. This extends BTCPay's e-commerce coverage to another established storefront platform and the merchants who rely on it.

Satoshi Tickets: API Access and Discount Codes
Satoshi Tickets, the Bitcoin-native event ticketing plugin, adds two features that make running an event with it more flexible.
The plugin now exposes a full API. Organizers can programmatically manage events, ticket tiers, and orders, making it possible to sync ticketing with an existing website. All endpoints are authenticated with the standard BTCPay Greenfield API key.
Satoshi Tickets also adds discount codes, letting organizers offer promotional or tiered pricing on their tickets. This makes the plugin a better fit for events that run early-bird pricing, community discounts, or partner promotions.

@TChukwuleta

Copy link
Copy Markdown
Member

@pavlenex

Plugin Builder & Directory

The Plugin Builder has grown over the past few months.

You can now build plugins straight from GitLab. Until now the plugin builder was GitHub-only; GitLab is now a supported source provider, so authors hosting their plugins there can publish through the builder just like everyone else.

The Plugin Builder now has a documented API, with a full OpenAPI spec and browsable Redocly docs, plus new endpoints for managing version releases and listing builds, and a health endpoint for monitoring. If you've ever wanted to build tooling around the plugin ecosystem, there's now a real surface to build against.

Plugins can now specify the range of BTCPay Server versions they support. The directory shows this on each plugin's page, so before you install you can check whether a plugin works with the version you're on or download the specific version that does.

Plugin authors can now add videos and screenshots to their listings, write a short description that appears on the main directory page, and upload SVG logos that stay sharp at any size giving people a clearer view of what each plugin actually does.

pavlenex and others added 2 commits June 24, 2026 18:14
Co-Authored-By: Chukwuleta Tobechi <47084273+TChukwuleta@users.noreply.github.com>
Comment thread blog/_posts/btcpay-server-2-4-0.md Outdated
@pavlenex
pavlenex merged commit 78f6483 into master Jun 25, 2026
5 checks passed
@pavlenex
pavlenex deleted the 2-4-0 branch June 25, 2026 12:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants