July 2024 - Version 6.20

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

Table of Contents

• Bug Fixes

• Enhancements

• Upgrade Instructions

• Important Definitions

Bug Fixes

• Fees: The Fee object’s Type field is now required to create a Fee record from an Event record. Previously, creating a Fee record with the Type field left blank resulted in Blackthorn Logs and errors.

• Virtual Terminal: A user with a non-admin profile and a Blackthorn | Payments (Admin), Blackthorn | Payments (Manager), or a Blackthorn | Payments (User) permission set can now create a Payment Method from the LCW and Aura Virtual Terminal. Previously, a user with a non-admin permission set would see an error when creating a Payment Method using the Virtual Terminal. (Known Issue: 000002947)

• Transactions: If a user enters an invalid Payment Method for a Transaction and then enters a valid Payment Method, the Transaction will be processed successfully without updating the Transaction Status and Payment Method fields multiple times. Previously, the Transaction’s Transaction Status changed from “Completed” to “Failed” and back to “Completed,” and the Payment Method changed from the original value to the new value and back to the original value. (Known Issue: 000003409)

• PaymentChargeFlow: To improve the user experience, the PaymentChargeFlow now includes logic to validate the input length for the Card Number, CVV, Exp Month, and Exp Year and will display an error message as a user enters incorrect information. Previously, the PaymentChargeFlow did not include validation and waited for information to get to the gateway before notifying the user of an incorrect character length. (Known Issue: 000003796)

• Payment Method: If a user enters incorrect Payment Method information and receives an error, they can now click the X to close the error message, enter the correct information, and successfully process the payment. Previously, dismissing the error message prevented the user from completing their payment Transaction.

Enhancements

• Fees: The Fee object’s page layout was updated to make the Type field required to create a Fee record.

• Spreedly: If a Spreedly Transaction fails, the Transaction will now contain the following information describing the reason for the failure.

  • If the response includes an error code, it will be stored in the Transaction’s Error Code field.

  • The Transaction’s token will be stored in the Transaction’s Spreedly Transaction Token field.

  • The date the Transaction was processed will be stored in the Processed Date field.

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.