February 2023 - Version 5.93
  • 11 Apr 2023
  • 1 Minute to read
  • Dark

February 2023 - Version 5.93

  • Dark

Article Summary

Once the updates listed below have been reviewed, please 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.

Upgrade Instructions

To upgrade Payments to the newest version, go to the Blackthorn Candy Shop.

Off-Cycle Release

Events Version 3.89

January 31, 2023

Updates were made to the backend Attendee registration process to prevent duplicate charges and duplicate ERS records. To resolve this issue, customers MUST upgrade both packages to the latest Events (3.89) and Payments (5.92) versions.

Payments Version 5.92

January 31, 2023

The following updates were made to prevent a Coupon on the first (prorated) Invoice from being applied to the entire Invoice as well as individual prorated Line Items when Proration Behavior = “Create Prorations” on a Subscription using a percentage off Coupon.

  • New Field
    • Location: Line Item object
    • Field Label: Is Not Discountable
    • API Name: IsNotDiscountable__c
    • Added to Stripe Billing permission set
  • Functionality
    • The default setting for this field is “False”.
    • Users must set Is Not Discountable = "True" on any Line Item records that should not be discounted.

Bug Fixes

  • When using Stripe, the Captured Amount on an authorized Transaction record will be captured even if the amount is less than the authorized Transaction.
  • If a Stripe Billing Subscription Proration Behavior = “--None--” or is left blank, any changes made to the Subscription will no longer be prorated.
  • Previously, the trigger that summed the total Transactions related to an Account and populated the Historical Account Value field caused failures. The occurred during Check and Money Order scans for Check 21 and Mobile Payments users when more than 50,000 Transactions were related to a single Account. To prevent this from occurring, a new custom setting in Blackthorn Pay - Trigger Settings was created. The new Disable Trans Rollup To Account custom setting will disable the trigger.

If you have any questions about this or need help with testing, please don't hesitate to reach out to Blackthorn Support.