Please review the updates below and follow the upgrade instructions to upgrade your Payments application.
Salesforce Release Update Known Issue
Enable Secure Static Resources for Lightning Components is a Salesforce Release Update that has been postponed indefinitely. Test Run on this Release Update should remain disabled in order to use our Virtual Terminal components. This is due to a Salesforce Known Issue.
Table of Contents
(Release Date: July 1, 2025)
Bug Fixes
TouchNet Gateway: Users can now register for an Event with a TouchNet payment gateway on an Experience Cloud site. The payment page will open in a new pop-up window, allowing users to complete the registration process. Previously, users intermittently got the following error, which prevented them from registering for the Event. "We're sorry, a system error occurred. Please try again later." (Known Issue: 000004680)
Transactions: Users can now select any Payment Method type and Payment Gateway (Stripe, AuthNet, or Spreedly) to capture a Transaction or cancel a Payment Schedule. Previously, they got the following error message when trying to capture a Transaction or cancel a Payment Schedule: "duplicate field selected: bt_stripe_Sales_Document_c Error is in expression '{!charge}' in page bt_stripe:transaction_charge: (bt_stripe)"
Reattempt Transactions: Transaction reattempts work correctly for Stripe, Spreedly, and Authorize.net credit cards, as well as for ACH Transactions on Spreedly and Authorize.net gateways. Previously, reattempts for Transactions with a failed card or ACH Payment Method would not work even though the Blackthorn Pay – Reattempt Settings custom setting was enabled.
Authorize.net Transactions
If a user processes a refund for a Transaction that used an Authorize.net payment gateway, none of the fields on the Invoice will be updated. Previously, after performing a full or partial refund on a Transaction that used an Authorize.net gateway, several Invoice fields were changed, including the Payment Status field, which changed from “Paid” to “Unpaid.” (Known Issue: 000004647)
Transactions using an Authorize.net gateway that are scheduled to auto-process will now process correctly on the scheduled date. Previously, when a user clicked the Process Scheduled Charge Transactions Now button to schedule Transactions using an Authorize.net gateway, the webhooks were not created, and the Transactions were not captured.
Enhancement
Payment Methods: The iOS Mobile Payments app’s user interface now includes a “Save card for future payments” checkbox. When submitting a payment via a card reader on the app, users can check the checkbox to allow their card information to be saved and reused for future payments. A message will appear in Stripe indicating the user has given consent for the card’s information to be stored and used for future payments. If the checkbox is not checked, no card information will be saved.
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.