August 2021 - Version 5.31

Once the updates listed below have been reviewed, please follow the upgrade instructions to upgrade your Payments application.

Upgrade Instructions

1. Review the Bug Fixes.
2. Install version 5.31 of Blackthorn Payments here.

• Production Install Link
• Sandbox Install Link

3. Navigate to Blackthorn | Payments Setup Wizard, click the PayLink tab, and install the latest PayLink package.

Bug Fixes

• Resolved: Users were noticing that the Transaction workflow email receipts were not sending with Authorize.net as the Provider on Payment Gateway. The workflow rule criteria has been updated to better evaluate Billing Email on Transactions.
• Resolved: Disputed ACH Transactions were resulting in webhook event errors. We've updated our dispute logic to prevent the webhook error and allow for the Dispute record to be created and Transactions to get subsequently updated.
• Resolved: The “New Payment Method” Action was unable to load while being viewed on a Salesforce Community page. This was due to a CSP violation. We've added payments.blackthorn.io to the CSP Trusted Sites in Setup as a packaged item.
• Resolved: A Customer reported hitting a CPU timeout when trying to create a Sales Document from the Opportunity using the Create Invoice button. We found that when you have multiple Opportunity Products with the same Product, Quantity, and Amount that our Create Invoice button on Opportunity starts to loop when creating Line Items and eventually times out. Our logic has been updated to prevent the looping behavior.
• Resolved: Transaction rollups were not being properly calculated after ACH Transactions were processed. We reordered the processing sequence so the rollups trigger would fire at the right time when webhooks are being used.NOTE: Make sure you do not have the Disable Trans Rollup To Parent custom setting enabled.
• Resolved: Some users were reporting seeing errors while processing authorize.net Transactions through Paylink. We've updated our API request to add additional detail to prevent a duplicate error from appearing in the future.
• Resolved: Some Payment Methods were being duplicated and causing errors after being created from the Virtual Terminal. We updated our logic to prevent this from happening in the future.

Stripe Billing

• Resolved: Using the Sync with Stripe button on Payment Gateway was not pulling in Stripe Invoices. We've updated our historical sync service to prevent this from happening in the future.
• Resolved: Using the Sync with Stripe button on Payment Gateway was not pulling in Canceled Subscription data. We've updated our query logic to pass in all statuses.
• Resolved: Users were unable to set the Account Balance to "0" in Salesforce on the Payment Gateway Customer record and see the update in Stripe. We've added logic to check for custom balances even if they equal 0 to ensure the "0" value can be sent to Stripe.
• Resolved: When modifying the Account lookup on an active Subscription the Active Subscription Names field on Account was not being properly updated. We've updated our trigger to fire when the Account lookup on Subscription is changed so the records will stay in sync.

Field Service Lightning

• Resolved: Refund Transactions were created, but not associated to Work Orders. We've made updates so Refund Transactions created via webhooks will automatically relate to the Work Order and trigger the balance rollups.