June 2024 - Version 6.19

Please review the updates below and follow the upgrade instructions to upgrade your Payments application.

Table of Contents

• Bug Fixes
• Enhancement
• DocumentLink
• PayLink
• Field Updates
• Upgrade Instructions
• Important Definitions

Bug Fixes

• The default Payment Method will be set correctly when using the Virtual Terminal to create more than one Payment Method with a Spreedly payment gateway. Previously, all added Payment Methods were automatically set to be the default Payment Method. (Known Issue: 000003129)

Authorize.net and Flow Screen Charge Component

To enable CVV validations when using an Authorize.net gateway and the PaymentChargeFlow component, check the new Live Validation Mode (Authorize.net) field on the Payment Gateway record and add the Show Address field to the PaymentChargeFlow component.

When both are enabled, additional address fields (Street, City, State, and Country) will be visible and required, and the validation process will occur.

• Object: Payment Gateway
  • Field Label: Live Validation Mode (Authorize.net)
  • API Name: Live_Validation_Mode__c
  • Data Type: checkbox
  • Default Value: False (unchecked)
  • Description:
    • If checked, the Payment Method will use the "liveMode" to submit a zero-dollar or one-cent Transaction (depending on the card type and the processor support) to confirm the card number belongs to an active credit or debit account.
    • If unchecked, the Payment Method will use the "testMode" to perform a Luhn mod-10 check on the card number without further validation.

Enhancement

• The Invoice record has a new field called Dynamic Fee Name. The field is populated when an Invoice related to an Event with an associated tax Fee is created or updated. The field’s value will then be used in DocumentLink’s Invoice to override the Tax column’s label. This update is related to the foundational development of the Tax/GST feature and is not functional.
  • Field Label: Dynamic Fee Name
  • API Name: bt_stripe__Dynamic_Fee_Name__c
  • Data Type: Text
  • Description: The name of the label used to display the tax Fee on an Invoice. For Events, it is the Fee Name of the Fee associated with the Event.

DocumentLink

Bug Fix

• When a user downloads an Invoice pdf from DocumentLink, the date format will remain the same as the browser locale format. Previously, the date changed to the US date format after downloading the Invoice pdf. (Known Issue: 000002642)

Enhancement

• Line Item names, descriptions, and other content will now wrap correctly when a user views a DocumentLink Invoice. Previously, the text was cut off, preventing users from viewing the entire amount.

PayLink

Enhancement

Users can now translate button labels and other static text on PayLinks. The Data Dictionary provides multilingual support, allowing Admins to establish a default language that serves as the primary language for all users. Admins can also override the default language and customize users' language experiences when specific predefined criteria are met.

The Transaction object now includes two new fields; the Data Dictionary Group field and the PayLink Display Language field.

• Field Name: Data Dictionary Group
  • API Name: bt_stripe__Data_Dictionary_Group__c
  • Data Type: Lookup(Data Dictionary Group)
  • Description: Select the Data Dictionary Group that contains the translated override values (Data Dictionary Entries) for the chosen Display Language.
• Field Name: PayLink Display Language
  • API Name: PayLink_Display_Language__c
  • Data Type: picklist
  • Description: List of supported display languages for PayLink. This field is set to English by default.

The following logic describes how the Data Dictionary Group/Data Dictionary Entry records interact with the PayLink Display Language field.

• PayLink labels are displayed in English, the default language, when either of the following is true.
  • The Transaction’s PayLink Display Language and Data Dictionary Group fields are blank.
  • The Transaction’s PayLink Display Language field is blank, and the Data Dictionary Group does not have a Data Dictionary Entry for English.
• PayLink labels use a Data Dictionary Entry’s values if the attached Transaction’s Data Dictionary Group has a Data Dictionary Entry record that uses the same language as the Transaction’s PayLink Display Language.
• PayLink labels are displayed in the selected Transaction PayLink Display Language if a Data Dictionary Group does not include a Data Dictionary Entry record for the selected PayLink Display Language.
• PayLink labels are displayed in English if a Data Dictionary Group has a Data Dictionary Entry record with Language / Locale = “English,” and the Transaction’s PayLink Display Language field is blank.
• PayLink labels are displayed in the selected Transaction’s PayLink Display Language when the Transaction’s Data Dictionary Group field does not have a value.

Click here for more information about translating PayLinks.

Field/Layout Updates

New

• Object: Invoice (This update is related to the foundational development of the Tax/GST feature and is not functional.)

  • Field Label: Dynamic Fee Name
  • API Name: bt_stripe__Dynamic_Fee_Name__c
  • Data Type: Text
  • Description: The name of the label used to display the tax Fee on an Invoice. For Events, it is the Fee Name of the Fee associated with the Event.

• Object: Transaction

  • Field Name: Data Dictionary Group
    • API Name: bt_stripe__Data_Dictionary_Group__c
    • Data Type: Lookup(Data Dictionary Group)
    • Description: Select the Data Dictionary Group that contains the translated override values (Data Dictionary Entries) for the chosen Display Language.
  • Field Name: PayLink Display Language
    • API Name: PayLink_Display_Language__c
    • Data Type: picklist
    • Description: List of supported display languages for PayLink. This field is set to English by default.

Upgrade Instructions

Important Definitions

Breaking Change

A breaking change is a significant change that requires a package upgrade to see the update.

Off-Cycle or Hotfix Release

A hotfix is a release that corrects a problem that impacted extensive functionality.

If you have any questions, please don't hesitate to contact Blackthorn Support.