October 2024 - Version 6.25

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

Table of Contents

• Bug Fixes
• DocumentLink
• Upgrade Instructions
• Important Definitions

Important Note

Blackthorn customers will not be impacted by the most recent Authorize.net change. Recently, Authorize.net contacted many of their customers to let them know they are updating their SSL/TLS certificates. Based on information provided by Authorize.net, Blackthorn products will not be affected by this change.

Bug Fixes

• Custom Settings: When the Blackthorn Pay – Trigger Settings custom setting Enable Payment Intents for ACH PMs = “True” (checked), hidden fields remain hidden, and mapping works as expected. Previously, if the custom setting was checked, hidden fields were visible, mapping broke, and users received a Terminal Data Initialization Error. (Known Issue: 000003932)
• Transactions: When using an Authorize.net Payment Gateway, the Transaction’s Payment Status will change to “Captured” once the Transaction is processed. Previously, the Payment Status was set to “Authorized” instead of “Captured” after the Transaction was processed. (Known Issue: 000003818)
• Field Service Lightning (FSL): If a user adds a long Transaction record Description to the Work Order’s Offline Mobile Pay URL field, the text will remain within the character count limit and no longer generate an error. Previously, this caused some required parameters to be omitted from the URL, which generated Blackthorn Logs with the following error message. “Update failed, Offline Mobile Pay URL: data value too large”. (Known Issue: 000003840)

Payment Schedules

• When a Transaction’s Transaction Status is set to “Failed,” the related Payment Schedule field Schedule Status will be set to "Failed," and Payment Status will be set to "Overdue." Previously, the Schedule Status was set to “Future,” and the Payment Status was set to “Scheduled.” Click here for more information about the statuses and their definitions. (Known Issue: 000002805)
• If a Contact cancels their Payment Schedule (Schedule Status = “Canceled” or “Canceled and Refunded”), a new Transaction will not be automatically generated. Previously, when the Payment Schedule’s Schedule Status was set to “Canceled,” a new Transaction was automatically generated, and the Schedule Status was changed back to “Active.” (Known Issue: 000003787)

Virtual Terminal

• Users searching for a Payment Method in the LWC Virtual Terminal will see identifying information such as the Payment Method’s Holder's Name, Email, or Last 4 Digits, depending on the Payment Method type and available information. Previously, the user saw the Payment Method’s numeric Salesforce name (E.g., PM0000001, PM0000002, etc.), making it difficult to locate the correct Payment Method. (Known Issue: 000003097)
• When using the “New Single Charge” action in the LWC Virtual Terminal, users will see only those Payment Methods related to the selected Contact, Account, or Lead. Previously, the list of available Payment Methods included ones unrelated to the selected Contact, Account, or Lead. (Known Issue: 000003144)
• When using the LWC Virtual Terminal from an Invoice record, the Description field on the LWC Virtual Terminal will have the same value as the Invoice’s Subject field. Previously, some fields configured using the Custom Metadata Types mapping feature were incorrectly mapped when loading the LWC Virtual Terminal. (Known Issue: 000003273)

DocumentLink

Bug Fixes

• When using the Data Dictionary with DocumentLink, users will see the value in the Invoice’s Dynamic Fee Name field replace the Line Item row label for "Tax." Previously, the Line Item row label for "Tax" did not display the Dynamic Fee Name value, even though the Dynamic Fee Name value replaced “Tax in the totals section.
• Formatting changes (italic, bold, etc.) made to the Invoice’s DocumentLink Field 1, DocumentLink Field 2, and DocumentLink Field 3 fields will appear as they were formatted on the DocumentLink. Previously, formatting changes were not applied to the DocumentLink. (Known Issue: 000003693)

Upgrade Instructions

Go to the Blackthorn Candy Shop to upgrade Payments to the newest version.

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.