March 2024 - Version 6.16

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

Upgrade Instructions

Bug Fixes

• Payments made with an Authorize.net Payment Gateway via a DocumentLink will now process correctly. Previously, Invoices were not always created, forcing users to update the Transaction with the Invoice manually. Users also received the following error. "The provided key 'sk_live_********************uNhC' does not have access to account 'xxxxx' (or that account does not exist). Application access may have been revoked.", "type": "invalid_request_error", "code": " (Known Issue: 000003170)
• Opportunity Products with Product Type = “One-Time” will only be added to the first Invoice. They will not be added to the Subscription. Previously, editing a Subscription with a regular Opportunity Product and an Opportunity Product with Product Type = “One-Time” caused the one-time Opportunity Product to be incorrectly added to the Subscription in Stripe. (Known Issue: 000003150)
• A Payment Gateway Customer (PGC) record will be created if an email address is valid. Previously, the PGC validation rule prevented PGC records from being created if the email address domain had more than four characters. (Known Issue: 000003258)
• When the Relationship Settings’ Contact Account Rule field is set to “Bucket Account,” a new Contact record without a matching Account will be added to the “Bucket Account.” Previously, the Account matching rules incorrectly added the new Contact record to the “Basic Bucket” Account.
• When processing Invoice webhooks asynchronously, the Invoice will include the relevant information from the associated Account, Contact, and Payment Method records. Previously, the Invoice was missing information from the Account, Contact, and Payment Method records. (Known Issue: 000003266)
  • The guest user must also be assigned a custom permission set in addition to the Blackthorn | Payments (Site Guest User) permission set to have Read access to several standard objects to process the webhooks. The custom permission set must include the following object permissions:
    • Account - Read
    • Opportunity - Read
    • Product2 - Read
  • NOTE: When webhooks are processed via batch or manually, sharing rules apply. Using a custom trigger will allow webhooks to be processed in system mode, bypassing sharing rules. You may experience limitations for use cases, depending on your specific scenario.

Enhancement

High Volume Batch Processing

High volume batch processing enables the scalability of our batch processes. The new logic queries high volumes of Transactions, splits the results, and invokes concurrent batches. Previously, the batch processes were limited to one record at a time to ensure that Payments was compliant with Salesforce's limits.

Opt-In Instructions: If you want to enable this feature, please contact Blackthorn Support. There is no additional cost. Support will guide you through testing in a sandbox before determining the final value for the batch size setting. The value is based on the specific customizations in your org.

DocumentLink

Bug Fix

• The contact email in the DocumentLink error message has been updated to the Blackthorn Support contact link. (Known Issue: 000003061)

Base Package

Enhancement

• The Smart Scheduler (Blackthorn Base package) was added to the Blackthorn Candy Shop. Messaging customers can now use Smart Scheduler without downloading the Events or Storefront apps.

If you have any questions about this or need help with testing, please don't hesitate to reach out to Blackthorn Support.