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: May 28, 2025)
Bug Fixes
Non-Gateway Transactions: After manually refunding a non-gateway Transaction, the refund Transaction’s Retained Amount and Retained Net Amount fields will display the correct amounts. Previously, the fields incorrectly displayed a negative amount equal to the original Transaction’s Amount (20 vs. -20) instead of 0.00. (Known Issue: 000004546)
Codes: When a user enters an “amount-off” Code (Type = “Discount” and applied at the Event level) during checkout, the discount will be calculated correctly. Previously, the discount amount used in the calculation was $3, regardless of the amount configured in the Code.
Enhancements
Payment Intents: The Payment Intent’s Capture Method field now supports the “Automatic Async” (automatic_async) value to align with the latest Stripe Library version. This value is used internally to support Stripe’s required behavior and is not intended for user selection. The new default value for the Capture Method field is “Automatic Async.”
Payments Receipt Emails: The Transaction workflow rules, “Send Blackthorn | Payment Receipt (HTML) and “Send Blackthorn | Payment Receipt (Text),” for the Payments Receipt Email were converted to the “Send Blackthorn | Payment Receipt” flow. Users can now launch the Payments Receipt Email from the flow in the Payments package. The email receipt will be sent when the Transaction is completed/captured and will contain the Transaction’s Description in a merge field. Note: “Send Blackthorn | Payment Receipt (HTML) and “Send Blackthorn | Payment Receipt (Text)” were deprecated.
Spreedly Payment Gateway: The new fields, Spreedly Private Key and Spreedly Certificate Token, were added to the Payment Gateway object to ensure authentication occurs correctly when using iframed components and a Spreedly Payment Gateway.
Field Label: Spreedly Private Key
API Name: bt_stripe__Spreedly_Private_Key__c
Data Type: Long Text Area(4096)
Description: Stores the PEM-formatted private key used for SSL client certificate authentication with Spreedly.
Field Label: Spreedly Certificate Token
API Name: bt_stripe__Spreedly_Certificate_Token__c
Data Type: Text(255)
Description: Stores the Spreedly certificate token used for payment gateway routing. Auto-generated by Spreedly and used to reference the stored certificate securely.
Permission Set Updates for Both Fields
Read/Edit: Blackthorn | Payments (Admin)
Read: Blackthorn | Payments (User), Blackthorn | Payments (Manager), Blackthorn | Payments (Community/Platform User), Blackthorn | Payments (Site Guest User), and Blackthorn | Payments (Lite User)
No Access: Blackthorn | Payments (Stripe Billing)
Field/Layout Updates
New
Object: Payment Gateway
Field Label: Spreedly Private Key
API Name: bt_stripe__Spreedly_Private_Key__c
Data Type: Long Text Area(4096)
Description: Stores the PEM-formatted private key used for SSL client certificate authentication with Spreedly.
Field Label: Spreedly Certificate Token
API Name: bt_stripe__Spreedly_Certificate_Token__c
Data Type: Text(255)
Description: Stores the Spreedly certificate token used for payment gateway routing. Auto-generated by Spreedly and used to reference the stored certificate securely.
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.