Please review the updates below and follow the upgrade instructions to upgrade your Payments application.
Table of Contents
(Release Date: February 18, 2026)
Bug Fixes
Stripe Metadata Mappings: If a user creates Stripe metadata mappings with the Transaction object (source object), future Transaction records created by registering for an Event will automatically send all metadata in the mapped fields to Stripe. Previously, only the metadata from the Transaction Payment Method Billing Email was sent to Stripe. The metadata from the other mapped fields was not sent. (Known Issue: 000005024)
Transactions: If a user partially captures an authorized Transaction that uses a Payment Method on a Stripe gateway, the Transaction will be partially captured after clicking the Capture button or checking the Capture field. The Transaction’s Transaction Status will change from “Process” to “Completed,” and the Payment Status will be set to “Partially Captured.” Previously, the Payment Status remained set to “Authorized.”
LWC Virtual Terminal: When using the LWC Virtual Terminal component inside a Salesforce Flow, declined transactions will now properly display error messages and "card declined" notifications instead of automatically advancing to the next screen. The component will now correctly handle transaction failures and provide clear feedback to users about the transaction status. This fix ensures proper error handling in Flow implementations where users need to see transaction results before proceeding. When a payment is declined with error code 2 or other failure responses, the Virtual Terminal will display appropriate error messages and wait for user acknowledgment rather than progressing automatically through the flow. Previously, when a transaction was declined using the LWC Virtual Terminal inside a flow, the component failed to display error or "card declined" messages and instead automatically advanced to the next screen as if the transaction was successful. This behavior mirrored issues from the existing PaymentChargeFlow component where success messages appeared regardless of actual transaction results.
Enhancements
Spreedly: When the tokenization option is enabled for Spreedly Payment Gateways in production, users can successfully create a Payment Method in the Virtual Terminal or via a PayLink. The tokenizer iframe URL now includes the necessary Spreedly authorization components. Previously, authentication issues were caused by Spreedly's enhanced security “Enable Secure Tokenization” setting. The system returned a 401 error and a generic "failure to create payment method" message.
Accessibility
Updates were made to the LWC Virtual Terminal to enhance the user experience, especially for keyboard navigation and assistive technologies.
When a user tabs to the Related To field, it will be announced. Once in the field’s lookup, the user can tab through or use the down/up arrows to navigate the list. Each option will be announced as it is selected.
The information announced for the Description field’s tooltip now matches what a user hears when accessing the field’s tooltip from a community page, a record page, or screenflow.
Fields with a red asterisk will include “star” when the fields are announced.
When a success or error message occurs, it will be announced.
If a lookup field includes the option to create a new Account, Contact, Lead, or Payment Method, and a user tabs or uses the keyboard to navigate to the Create New option, a new window will open, allowing the user to create the new record. Afterwards, the user is returned to the field where it was created.
When creating a new Payment Method, a user can also press Shift-TAB to navigate through the fields in reverse order.
Known Issues
Events Salesforce – Issue with Processing Fees and the Invoice: Although a user has paid the full amount due and the checkout process is complete, the related Invoice shows a Balance Due of the amount in the Fee Amount field, while the Status field is set to “Ready To Bill,” and the Payment Status field is set to “Partially Paid.”
PayLink - Accessibility Issue: Users cannot switch between the Card and Bank (ACH) tabs when navigating with the Space and Enter keys on a keyboard. This will be fixed in the April 2026 PayLink Webapp release.
Upgrade Instructions
To upgrade Payments to the newest version, go to the Blackthorn Candy Shop.
Important Definitions
Breaking Change
A breaking change is a significant change that requires a package upgrade to see the update.
Off-Cycle or Hotfix Release
A hotfix is a release that corrects a problem that impacted extensive functionality.
If you have any questions, please don't hesitate to contact Blackthorn Support.