Software Update: BTCPay Server 1.0.7.0

BTCPay Server is, as the name suggests, an open source payment processor for Bitcoin and other cryptocurrencies. With this you can easily accept crypto payments in, for example, a webshop. There are several modules available that allow it to integrate into the popular ecommerce packages such as WooCommerce, Shopify, Drupal, Magento, and PrestaShop. For more information, we refer you to the documentation from BTCPay Server. The developers have released version 1.0.7.0 with the following changes:

see blog post for more details.

Features:

• New Wallet Setup UI (see #2164, #2296)
• Greenfield: New on-chain wallet API
• Greenfield: Ability to configure store’s lightning payment methods
• Allow an invoice to be marked invalid/complete even from the new state
• Point of Sale and Crowdfund: Allow custom buy button text (see #2299)
• Specter wallet file import (see #2252)

Improvements:

• Reenabling uppercase BECH32 in QR codes (see #2110)
• If a store is set to internal node, use “Internal Node” as connection string rather than the actual connection string.
• Improve Policies options UX in server settings (see #2307)
• Fix view payment request loading spinner alignment
• Fix cart pay button loading spinner vertical alignment
• Invoices list: Remove icon indicator for onchain (see #2240)
• Login: Improve tab navigation for input fields (see #2258)

Bug fixes:

• Hovering the mouse pointer on invoice logs row would make them unreadable
• Remove exchange rates that lost support in Coingecko
• Get invoice in greenfield was crashing if invoiceId did not exist
• Getting a file from the storage service which did not exist would return http 500 instead of 404
• Fix direct URL for local storage with custom root path #2318
• The pay button would not show up properly on some websites
• Profile email change should check email’s availability
• Fixed mysql/sqlite support
• Checkout: Fix scan/copy tab sizes with varying content (see #2264)
• Greenfield: Lightning API would return HTTP 500 if store owner did not set the connection string
• Point of Sale: The custom price was not properly working (see #2248)