November 2021 - Version 5.41

We've expanded our Support Community! :clap: :clap:

We just rolled out two great features in our Support Community to help take the stress out of success!

  • Salesforce Knowledge: Visit our Support Community and search our Knowledge articles for helpful troubleshooting tips, FAQs, and current issues before opening a case.

  • Known Issues: We pulled data directly from our engineering tools to create a current list of Known Issues. Use our Knowledge articles to learn more and subscribe to an issue to track its progress without opening a case.


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


📘

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

  1. Review the Bug Fixes.

  2. Install Version 5.41 of Blackthorn Payments here.

Upgrading via the AppExchange Video

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

Enhancements

  • Blackthorn's previous logo and watermark has been removed from PayLink and DocumentLink.

  • The optimization of existing functionality with our Mobile Payments app for Android will allow the user to successfully process manually entered card, ACH, and card reader transactions.

Stripe Billing

  • Changing the Price on the Subscription / Subscription Item is no longer possible as the change isn't accepted/reflected in the Stripe Billing Dashboard. If you try to change a Price on the Subscription / Subscription Item, you will receive this error message. "Price cannot be updated for a Subscription Item. Please delete this Subscription Item and add a new Subscription Item to update the Subscription." For specific instructions, please click here.

  • There are several important updates to the Stripe Billing app.

    • On the Blackthorn | Payments Admin page, the Deploy Stripe Billing, Assign Stripe Invoice Record Type, and Assign Subscription Record Type buttons have been combined to create a new Deploy Stripe Billing button.

    • The DocumentLink Template, Payment Methods, and Company Info tabs have been removed.

    • On all Stripe Billing objects, the buttons in the top right corner have been updated to Edit, Push To Stripe, Delete, and Clone.

    • "Stripe Invoice" is now the default Sales Document record Type for all Standard Users.

    • The following tabs have been relabeled.

      • Coupons —> Stripe Coupons
      • Prices —> Stripe Prices
      • Gateway Orders —> Stripe Gateway Orders
  • A new field, Enable Payment Methods, has been added on the Subscription object. The following Values in the multi-select picklist are now available for the user to select.

    • ACH Credit (pushed by them)
    • ACH Debit (pulled by you)
    • Canadian pre-authorized debit
    • BECS Direct Debit
    • Bacs Direct Debit
    • Bancontact
    • Boleto
    • Card
    • EPS
    • FPX
    • giropay
    • iDEAL
    • Przelewy24
    • SEPA Direct Debit
    • SOFORT
    • Wechat Pay

Bug Fixes

  • When a generated Transaction fails and the Payment Schedule's Recurrence Method is set to "Keep One Open", two transactions will be created — one for a reattempt Transaction that has a due date set according to your Reattempt Settings and one with a due date set for the next billing frequency.

Stripe Billing

  • The Description field of a Transfer Transaction will no longer be incorrectly cleared by the processing of a related Webhook Event.

  • If a Transaction in Stripe fails, the Charge.failed webhook will process as expected and create the failed Transaction rather than causing the webhook to fail with the "Unable to find Payment Gateway with ID = null" error.

  • When Transactions fail for Stripe customers using the Transaction Reattempt feature, a duplicate reattempt Transaction will no longer be generated when Charge.Failed webhooks process.


Compliance

  • Users will see the following updated names for Blackthorn Compliance

    • Blackthorn Compliance (previously PCIFY)
    • SecureAttachment for Blackthorn Compliance (previously SecureAttachment for PCIFY)
    • Blackthorn Compliance-Email2Case (previously PCIFY-Email2Case)
    • Blackthorn Compliance-Chatter (previously PCIFY-Chatter)
    • Blackthorn Compliance-Chat (previously PCIFY-Chat)

Donations

🚧

Donations Package Installation

If you are installing the Donations package for the first time, you will automatically see the field donation360Picklist_Valuesc on the Form Question page layout.

If you have previously installed the Donations package and are upgrading it, you will need to manually update the page layouts to remove donation360Picklist_Values_Longc and add donation360Picklist_Valuesc.

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


Did this page help you?