November 2025 - Version 6.49

Please review the updates below and follow the upgrade instructions to upgrade your Payments application.

Table of Contents

(Release Date: November 19, 2025)

• Bug Fixes

• Enhancements

• Upgrade Instructions

• Important Definitions

Bug Fixes

• Stripe Transaction: A user can capture a Transaction (payment) when the Name or Description fields are mapped from the Transaction via Stripe Metadata Mapping, and the Transaction’s status fields will be updated accordingly. Previously, when a user clicked the Capture button on the Transaction, they got an error. (Known Issue: 000004947)

• Invoices: When applying/removing a discount Code to/from an Invoice after an Event registration, the related Line Items will reflect the correct amounts, and the Invoice’s Fee Amount will be recalculated. Previously, the Invoice’s Fee Amount value was not recalculated.

• Virtual Terminal: If the Blackthorn Payments | Virtual Terminal’s Hide Bank Tab or Hide Card Tab custom setting is enabled, then the Payment Method labels (“Name on Card,” “Card Number,” “Name on account,” and “Account holder type“) will be fully visible. Previously, the labels were cut off on the Payment Method page in Virtual Terminal.

Authorize.net Transaction

If the values in a captured Transaction match or exceed the Authorize.net fraud detection settings, the Transaction’s Transaction Status field will update to “On Hold.” The “On Hold” value prevents a reattempt Transaction from being created before the Transaction can be reviewed and approved or declined.

• If an “On Hold” Transaction is voided or declined, the Transaction Status will be updated to “Failed” and no reattempt Transaction will be created.

• If the Transaction is approved, the Transaction Status will be changed to “Completed.”

Transactions that fall outside the Authorize.net fraud detection settings and do not require review will not have their Transaction Status set to “On Hold.” Instead, a reattempt Transaction will be created. Previously, failed Transactions were reprocessed and charged, even though the initial and the reattempt failed. (Known Issue: 000004119)

Enhancements

• Payment Gateway Customers: When a user creates a new Payment Method, one of the following scenarios will occur. Previously, when a new Payment Method without an existing Payment Gateway Customer (PGC) was created, the Payment Method was incorrectly associated with an existing PGC from the same Account rather than creating a new PGC.

  • Scenario 1: A Contact exists on the Payment Method, and the Contact is associated with an Account. If Salesforce finds a PGC where both the Contact and Account match, then the new Payment Method will be linked to that PGC.

  • Scenario 2: A Contact exists on the Payment Method. The related Account and Contact do not have a matching PGC. Salesforce searches for an existing PGC with a billing email address that matches the email address associated with the Payment Method. If the resulting PGC has the same Account, then the Payment Method will be linked to that PGC.

  • Scenario 3: A Contact exists on the Payment Method, and the Contact is associated with an Account. Salesforce cannot find a matching PGC by searching Contact and Account records, nor by searching by the billing email address. Therefore, Salesforce creates a new PGC for the Payment Method. A new PGC will be created even if another PGC is related to the Account that is associated with the PM. If they do not match, they should not get associated.

• Error Tracking: We enhanced our system's ability to track and diagnose payment processing issues, enabling our Support team to identify and resolve problems more quickly. The changes include:

  • Better error tracking across payment processing components

  • Capturing more detailed information when payment issues occur

  • Improved system monitoring to catch problems faster

DocumentLink

Enhancements

• The color palette used for DocumentLink has been updated to use neutral colors instead of the traditional Blackthorn palette.

• The following updates were made to DocumentLink to remove accessibility-related errors.

  • Increase the color contrast ratio between text and background.

  • Remove redundant alternative text.

  • Define page regions using semantic HTML elements (header, nav, main, footer) or appropriate ARIA roles.

Known Issue

Users must have Read access to any fields added to the “Blackthorn Pay - Transaction Parent” custom setting. If Read access isn’t granted, users will receive an ‘insufficient permissions’ error when using the Mobile Payments app. This issue is scheduled to be fixed in early 2026.

Upgrade Instructions

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 impacts extensive functionality.

If you have any questions, please don't hesitate to contact Blackthorn Support.