December 2022 - Version 5.85
  • 06 Dec 2022
  • 3 Minutes to read
  • Dark

December 2022 - Version 5.85

  • 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.


  • Plaid users can now add a customer’s name and email to the Bank section of the PayLink form.
  • To ensure new Payment Methods created via a Cybersource (via Spreedly) Payment Gateway are created with all mandatory fields, validations have been added to ensure users fill in the Street, City, Country/Region, and State fields.

Bug Fixes

  • New installations of the Payments app will successfully complete the “Setup Payment Jobs” step and the overall installation process.


  • When Work Order Line Items are deleted from a Work Order, the amount of the related Transaction record will update accordingly.
  • Resolved an issue preventing Payout records from being created after Transaction records were synced via the Historical Sync feature.
  • Corrected an issue that was causing multiple changes to the Net Payment Gateway Fee field on Disputed Transaction records.
  • Chargeback Transaction records (refunds) are now properly relating to Payout records in Salesforce, as they are in Stripe.


  • Coupons (Amount Off and Percentage Off) applied to prorated Subscriptions in Stripe will be applied only at the Invoice level and not at the prorated Line Item level.
  • Coupons cannot be applied on a Stripe Invoice Line Item; they can only be applied on the Invoice itself.
  • When a Stripe Invoice Line Item is changed in Salesforce, the update will be pushed to the Invoice in Stripe.
  • After completing an ACH Transaction using a Stripe Payment Gateway via PayLink, the micro-deposit prompt will no longer be visible since Stripe waives micro-deposits.
  • Additional updates have been made to prevent the micro-deposit message from appearing when Stripe has waived the micro-deposit requirement, the Skip ACH Validation custom setting is enabled, and a Transaction with an ACH Payment Method is being processed via PayLink.
  • When a Stripe Payment Gateway that was set up with Plaid is used to complete a Transaction via PayLink, the Customer Name & Email will be captured correctly, populated on the Payment Gateway Customer record, and sent to Stripe.

  • An error was resolved that occurred when using and PayLink which caused the Bank Account Type selector to appear inactive when a user tried to make an ACH payment.
  • To prevent incorrect duplicate Transactions when using, a new custom setting labeled “Duplicate window” was added to ”Blackthorn Pay - Trigger Settings”. The new custom setting includes the following functionality.
    • The user is UNABLE to capture the duplicate Transaction when
      • the Transaction is within the time mentioned in the Duplicate window custom setting
      • the Duplicate window = “NULL” in Custom Settings
    • The user is ABLE to capture the duplicate Transaction when
      • the time is after the time set in the Duplicate window custom setting
      • running the Batch Job


  • If the Street 2 (Bill To) field in the address is populated on the Invoice, the second line of the address will now be visible on the DocumentLink.
  • Changes made to the Invoice’s Compact Layouts will be retained after upgrading the Payments app.
  • ​​After an ACH payment is made via a DocumentLink, the Balance Due field on the Invoice will update to zero and the PAY button will no longer be visible.

Virtual Terminal

  • When using the Virtual Terminal to create a new Payment Method, users must populate the Related To field in order to save the new Payment Method. This is to ensure the Payment Gateway Customer and Payment Method are linked to an existing Contact or Account.
  • Updated the Virtual Terminal to ensure the “New Payment Method” action loads properly after Salesforce orgs are upgraded to the Winter ‘23 release.

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