Once the below updates have been reviewed, please follow the upgrade instructions to upgrade your payments application from the AppExchange.
If you are currently using the custom setting
Terminal Related To Default Objectfrom the Blackthorn Pay - Trigger Settings you need to switch to the new custom setting
Related To Default Objectnow located under Blackthorn Payments | Virtual Terminal. The custom setting
Terminal Related To Default Objecthas been removed.
Important upgrade note for all
Starting with the June 2021 release, we will require all customers to be no more than 3 versions behind the latest version. We'll start reaching out to customers this month that are more than 3 versions behind.
Salesforce Release Update Known Issue
Enable Secure Static Resources for Lightning Components is a Salesforce Release Update that will be enforced in Summer '21.
Test Runon this Release Update should remain disabled in order to use our Virtual Terminal components. This is due to a Salesforce Known Issue.
Review the Bug Fixes and Enhancements.
Install version 5.20 of Blackthorn Payments here:
- Navigate to Blackthorn | Payments Setup Wizard, click the PayLink tab, and install the latest PayLink package.
We have removed the "terminal" logo and
Clearbutton from the Virtual Terminal. This will allow the component to seamlessly appear on the record page without it looking out of place.
The Virtual Terminal now displays a spinner while loading on the page. This will help users know when the Virtual Terminal component has fully loaded so they don't input data into the wrong field.
Updated the Payments Setup Wizard Paylink step so that it loads the latest version of Paylink (v1.20).
Removed the Custom Setting labeled
Terminal Related To Default Objectfrom Blackthorn Pay - Trigger Settings. This was a cleanup item as this setting has moved to the Custom Setting group labeled Blackthorn Payments | Virtual Terminal.
Added the ability to modify the
recordIdassociated with the
Related Tofield on Virtual Terminal. We also added the ability to modify the
Parent Objectat the same time. This will give customers more flexibility when customizing the Virtual Terminal in a flow or in another custom component.
Virtual Terminal will now have the ability to capture success or failure responses from Transactions. We're adding code that can be reused by customers in custom components for this feature. Additionally, we're adding a code mechanism for disabling the success pop up that occurs after capturing a Transaction in Virtual Terminal.
We added additional global variables for the Virtual Terminal that will control which type of Payment Method form in displayed inside custom components. This variable, when used in a custom component, will also have the ability to filter stored Payment Methods by type.
Added an update to our Payments REST API so the Account and Contact IDs can be accepted when working with Authorize.net requests.
If you would like to bypass Stripe's fingerprint logic and use our legacy logic for ACH Payment Methods do the following:
Navigate to Custom Settings -> Blackthorn Pay - Trigger Settings ->
Disable Fingerprint Matching (ACH)set to 'TRUE'.
Resolved: When a Payment Method resulting in an "Invalid"
Payment Method Statuswas added from the Virtual Terminal users were seeing a success message. This was because the logic was noting whether or not the Payment Method was saved. We've updated the logic to throw a failure message when a Payment Method is saved, but invalid. This will be more intuitive for users.
Resolved: The custom setting labeled
Hide Parentwas hiding the
Parentfield on the Virtual Terminal, but also it was preventing the parent record value from populating on Transactions captured from the Virtual Terminal. The logic has been updated so users will now see the parent ID on Transactions captured from Virtual Terminal regardless of if the field was hidden or not.
Resolved: The field text for
Card Expirationon the Paylink form was not intuitive to users and needed to match the UI for Virtual Terminal. This field has been modified so instead of saying
Card Expiryit now says
Resolved: Users noticed that when creating a graduated Price in Stripe with a large unit value ( 999,999,999,999,999 ) a BT Log with an exception was created and the Price was not being synced in Salesforce properly. We have updated our logic to allow for the larger value to prevent this exception. Users will now be able to create Prices in Stripe within Stripe's value limits and sync with Salesforce.
Resolved: When the Custom Setting
Disable Trans Rollup Parentwas set to "True" there were instances of the Transaction rollup logic still being triggered. We've made an update so whether the scheduled batch
TransactionRollupToParentServiceruns automatically or whether the user manually triggers
TransactionRollupToParentServicethe logic will not be executed if the Custom Setting is checked.
Resolved: The proration behavior logic for Subscription Schedules was not matching the behavior users came to expect after using prorations with Subscriptions. The logic has been updated so
Backdate Start Datevalues on Subscription Schedules entered from Salesforce should sync with Stripe. This will allow Subscription invoices to be created appropriately.
Resolved: Blackthorn Log records were being generated when Transactions were being updated from Stripe. We've added logic to prevent the null pointer error that was being presented in the Blackthorn Log.
Resolved - When creating Subscription Schedules there were instances where duplicate Subscription records were being created after the webhook processed. We updated the logic to add the Subscription ID to the active Subscription Schedule Phase to prevent a duplicate Subscription record from being created.
Resolved - Government Cloud orgs were reporting that they were seeing errors when attempting to use the Payments Setup Wizard. Users will now be able to navigate through the wizard without errors. Additionally, they will notice that the Relationship step now adds a record to the Transaction Parent Custom Setting as expected.
- Added a Custom Setting labeled
Disable Fingerprint Matching (ACH)- This custom setting can be found under Blackthorn Pay - Trigger Settings. When enabled Stripe ACH Payment Methods will bypass the fingerprint logic that Stripe has implemented and use a custom matching logic we developed before Stripe fingerprints were implemented.
Updated about 1 year ago