February 2020 release is here!
Once the below updates have been reviewed, please upgrade your payments app from the appexchange:
Click here to upgrade your payments app from the appexchange.
Install the latest version from the link above.
Visit the Blackthorn | Payments Admin tab, navigate to Scheduled Jobs and click "Schedule recommended payment jobs" button. You can see our scheduled jobs in Setup - Jobs - Scheduled Jobs. We have updated our schedule jobs based on the transaction type.
- We have made updates to our Virtual Terminal. For this reason, you'll need to allowlist your domain to support inline frames in a Visualforce page. This is critical for your Virtual Terminal to work with no issues.
Go to Setup > Session setting. Under the section Whitelisted Domains for Visualforce Inline Frames - Click Add Domain.
- For Stripe Billing users ONLY, we have new Invoice record types. Please navigate to the Blackthorn | Payments Admin tab and under the Stripe Billing section, click the "Deploy Stripe Billing" button.
**If you have any custom permission sets, you'll need to update them with the new record types.
Check21 - Blackthorn supports Check21 integration by utilizing Check21 technology into the Blackthorn Mobile Payments iOS and Salesforce.com applications. You can take check and money order payments onsite via your mobile phone through check capture. For more information, see here.
For Stripe Billing customers, we have a new Record Type for Stripe Billing Line Items on the Sales Document. Stripe Line Item is for Stripe Billing. To activate, please follow the upgrade instructions for setting these record types. Click here for more info.
Salesforce to Stripe Metadata feature > Blackthorn Payments now supports the ability to configure the Salesforce field/data to be mapped to stripe metadata key/value for Payment Gateway Customer, Payment Method, Transactions, Sales document, and Subscription objects.
List view capture - You can capture multiple transactions at one time using a salesforce List View.
While creating a Transaction or a Payment Method, if the user who triggered the flow doesn’t have access to the standard fields (like Lead/Contact) it will not set the lookup value to this field, but save the record successfully. To know more, click here.
Support included for the latest Stripe API Version. You can find the Stripe upgrade notes here.
Auto process/capture job updates - This new upgrade brings 4 separate batch jobs replacing the old
Blackthorn | Payments Daily Capturesfor each type of transaction like authorized captures, payouts, transfers, etc. This enhancement improves the processing time of these jobs making it more robust. To reschedule the new jobs, please follow the upgrade instruction 1.
To know more about these scheduled jobs, click here.
- Post-installation, you can find the help doc link in our package details. For this, navigate to Setup -> Installed Packages and click on the package name. There you should see a link populated in the Post Install Instructions field.
- Following the Salesforce critical update, we have packaged the Custom Metadata Types and Custom Settings Definitions in all the Payment permission sets as below.
- Prior to version 4.152, the payouts did not include the disputed refunds. So now if your payout includes a dispute, these refund transactions originated from disputes will set all lookups to the original payout.
Support included for the webhook event
- When a Payment Method is created in SF the webhooks are processed correctly preventing any duplication.
- When the invoice webhook is processed in Salesforce, it looks up the subscription and sets the correct account on the Sales document.
- When the transaction is captured via paylink, the Default Payment Method/Source on Contact/Payment Gateway Customer is updated immediately.
- The Payment webhooks processed from Authorize.net were erasing the Expiration Month/year and Postal Code on the Payment Method preventing any further updates to it which is now fixed.
- When the Payment Method is created from the Payment Gateway Customer record, set the lead lookup correctly.
- Users using the Rest API were facing an error: bt_stripe.SObjectSelector.FLSException: You do not have permission to read the field OtherStreet: (bt_stripe). This will be fixed with the upgrade.
- Users with Blackthorn | Payments (User) permission set were facing below error on the Virtual terminal.
We have included the missing field access for the Gateway Token and Gateway Refresh Token field on the Payment Gateway and that resolves the error.
Please make sure your custom permission set (if any) cloned from Blackthorn | Payments (User) includes the field access from point 7.
Error fixed > Content Security Policy error on Virtual terminal.
Stripe Billing Fixes:
a. The Payment Gateway record will successfully set the Country when pushed to Stripe.
b. When a plan is created with a currency in Salesforce, it will be set correctly in Stripe.
Updated 12 months ago