November 2020 - Version 5.7


November Payments Webinar

Our November Payments Webinar has been pre-recorded! Register for the webinar here. Once registered, you will receive an email with a link to watch!

Once the below updates have been reviewed, please follow the upgrade instructions to upgrade your payments application from the AppExchange.

Salesforce Winter '21


Salesforce Winter '21 Update

By now most customers might have noticed that Salesforce released their Winter '21 update. This update affects how we use the Site Guest User and has restricted permissions to that user. You'll notice enhancements below that were put in place to address these changes. You can read more about the Winter`21 update, here.

Upgrade Instructions

  1. Review the new enhancements and bug fixes.

  2. We added a few new fields to this package. If you are using custom permission sets/profiles, please see the new fields section below to update your profile and or permission sets.

Upgrading via the AppExchange Video

  1. Log into the AppExchange -

  2. Install the latest version of Payments(v5.7) from here.

  3. Install the latest version of Paylink(v1.19) from here.


From now until 11/30/2020, the below directions will teach you how to test the new features until they are automatically pushed.
This includes Plaid and Spreedly with PayLink

To Do
You will need to replace the PayLink URLs '' domain to a test domain.


For example, when you create your Transaction record, a PayLink URL is generated with the "" domain like this one:

You'll then click on the PayLink URL so it opens up in a new page. Remove "" and replace it with "" so it looks like this:

If you have any questions about this or need help with testing, please don't hesitate to reach out to us through our community.



In order to use Plaid and Spreedly with Paylink, customers will need to make sure they upgrade to this November Payments package(v5.7) and the latest Paylink(v1.19) package.

Paylink with Plaid - Watch Video

  • Customers will now be able to use their Spreedly Payment Gateway in conjunction with Paylink!

Spreedly for PayLink - Watch Video


  • Added additional validation messaging to the New Customer button on the Contact object. This will help customers resolve any data entry mistakes they may have made.

  • Tightened up security for how Spreedly and Payment Methods are created in Virtual Terminal.

  • Added a Custom Setting under Blackthorn Pay - Transaction Validations called TR Currency Validation . If this is enabled a validation rule will check to see if the currency on a Transaction matches the currency on the corresponding Payment Gateway. Read more about custom settings here.

  • We are now prepopulating address fields in the form presented when clicking New Payment Method on Account, Contact, and Payment Gateway Customer. Additionally, we've added the ability to pre-populate Holder Name, Email, and Postal Code when adding a new Payment Method from the Virtual Terminal.

  • The Virtual Terminal New Payment Method form has been updated when selecting or Spreedly as the Payment Gateway. The updated form falls in line with the styling of the Lightning Design System.

  • Relabeled and enhanced one of our Permission Sets to now be named Blackthorn | Payments (Site Guest User). This was previously labeled Blackthorn | Payments (Webhook Event Admin). This change will align with the latest security update from Salesforce Winter `21. Customers using webhooks and our Payments REST API will need to use this permission set. Read more here.


REST API Users - Please Read!

The updated Blackthorn | Payments (Site Guest User) permission set does not include access to the standard Account and Contact objects per Salesforce design. If you need to access the REST API be sure to grant access to the Account and Contact object via the guest user Profile. Read more here.

  • Added the field Mobile App Version to the Transaction object. This will help our customers know where Transactions originated for troubleshooting purposes.

  • Updated Payment Method logic for ACH methods to avoid Stripe Errors and instead use existing Payment Methods when making requests to the Payments REST API.

  • Simplified the Payments Setup Wizard by removing the configuration step.
    Note: Users will need to enable My Domain to go through Payments Setup Wizard

  • Stripe Billing: When pushing an Opportunity Line Item with Product Type = 'Do not Include' validation messaging is now included.

Bug Fixes

  • Resolved: SOQL error that was presented when adding a Coupon to Opportunity and pushing to Stripe using the Create Subscription button.

  • Resolved: A bug where the Default Payment Method on Contact was not always being updated.

  • Resolved: An issue where a user was unable to authorize a PayPal account on the Payment Gateway object.

  • Resolved: Occurrences of Blackthorn logs generating when Payment Schedules were being created.

New Fields/Layouts

  • Plaid User ID and Plaid Secret have been added to the Payment Gateway object.
  • Mobile App Version has been added to the Transaction object.

Did this page help you?