December 2024 - Version 6.27

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

Table of Contents

• Bug Fixes

• Enhancement

• Upgrade Instructions

• Important Definitions

Bug Fixes

• Permission Sets: The Blackthorn | Payments (Manager) permission set was updated to give read and write access to the Invoice’s Fee Amount field.

• Transactions: If a disputed Transaction is won, the chargeback reversal Transaction’s Retained Amount will be set to the original Transaction’s Amount. Previously, the chargeback reversal Transaction’s Retained Amount was set to “0.” (Known Issue: 000004103)

• Authorize.net: If a user tries to add a Payment Method for a Contact, Account, or Lead but the Customer Profile (Payment Gateway Customer in Salesforce) has only been deleted in the Authorize.net dashboard, they will get the following message. “The Payment Method could not be registered: Customer Profile could not be found in the Payment Gateway." The error message will also be saved in the Payment Method’s Error Message field. Previously, an error occurred when a user tried to add a new Payment Method from the Virtual Terminal except the Authorize.net Customer Profile was already deleted in the Authorize.net dashboard. (Known Issue: 000003988)

Virtual Terminal

• When creating a New Single Charge payment in the LWC Virtual Terminal, users can only select a Payment Method from the list related to the selected Contact, Account, or Lead record. Previously, users could choose any Payment Method in the org. (Known Issue: 000004186)

• The Virtual Terminal will use the Currency value from the related Invoice Currency ISO field. If the Invoice’s Currency ISO field is blank, the Virtual Terminal will use the Payment Gateway’s Default Currency value. Previously, the Virtual Terminal Currency field defaulted to “Choose One...” and the Payment Gateway’s Default Currency value did not change the value in the Virtual Terminal. (Known Issue: 000004186)

• The following will occur when using the Aura Virtual Terminal with the Experience Cloud. Previously, when a user created a new Payment Method from the Virtual Terminal in an Experience Cloud, the new Payment Method didn’t correctly trigger the matching to or creation of a new Payment Gateway Customer. The newly created Payment Method also didn’t appear in the Virtual Terminal drop-down list. (Known Issue: 000003244)

  • A newly created Payment Method’s Payment Gateway Customer field will be updated with the existing Payment Gateway Customer when there is an existing Payment Gateway Customer record with the same email and Account used to create the new Payment Method.

  • The new Payment Method’s Payment Gateway Customer field will be updated with a new Payment Gateway Customer record when there isn’t an existing one with the same email and Account used to create the new Payment Method.

  • Payment Methods added via the Virtual Terminal in the Experience Cloud will be added to the available Payment Methods for the related Account.

  • When a user logs into the Experience Cloud from a Contact record, the Virtual Terminal will display all available Payment Methods for the Account.

Enhancement

• Transactions: When a Transaction using a Stripe gateway fails, the following occurs.

  • A new Transaction is created. Its Record Type is set to “Refund,” Transaction Status is set to “Failed,” Payment Status field is blank, and the Stripe Fee related to the failure is recorded.

  • The original Transaction’s Transaction Status is changed to “Failed.” (Known Issue: 000002910)

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

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