June 2022 - Version 5.63

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

Upgrade Instructions

Enhancements

Virtual Terminal

• The Process button on the New Single Charge screen of the Virtual Terminal will remain grayed out until the Payment Method information is added.
• If a user clicks the + Add New button on the Virtual Terminal to create a new Payment Method and then clicks the Add + button on the New Payment Method screen without completing the required credit card fields, they will receive an error message. The error message will display the following message for each corresponding field.
  • “This field is required: Name on card”
  • “This field is required: Card number”
  • “This field is required: Card expiration”
  • “This field is required: CVC”
  • “This field is required: Postal code”
• If a user clicks the + Add New button on the Virtual Terminal to create a new Payment Method and then clicks the Add + button on the New Payment Method screen without completing the required bank details, they will receive an error message. The error message will display the following message for each corresponding field.
  • “This field is required: Name on account”
  • “This field is required: Routing number”
  • “This field is required: Account number”
  • “This field is required: Account holder type”

Donations

• Users can now add Donation’s “Embedded Form Code” as a module on a Hubspot landing page and successfully preview the page.

Candy Shop

• The PayLink package will be installed and the PayLink Admin permission set will be assigned automatically when the Payments app is installed from the Candy Shop.

PayLink

• The PayLink package will be installed and the PayLink Admin permission set will be assigned automatically when the Payments app is installed from the Candy Shop.
• When Bacs Direct Debit is enabled for PayLink w/Stripe Checkout, users can now complete Payment Transactions using a Bacs Direct Debit account.

Bug Fixes

• The following default settings will now install correctly after installing Payments 5.57.
  • The Opportunity and Invoice will now be included in the Transaction Relationships in the Payment Setup Wizard.
  • The Default Relationship Settings record will now be available in the Relationship Settings object.
• If a user tries to enter a card number in the Name on card field when adding Payment Method via the Virtual Terminal, they will now receive an “Adding Payment Failed - Name on card field is not valid” error. Additionally, a customer record in Stripe with the card number as the Name will no longer be created.

Stripe

• Multiple refund Transactions will no longer occur after a single ACH Dispute has been processed in Stripe.
• An error was resolved, preventing mapped Stripe Metadata from syncing automatically from Salesforce to Stripe.
• When a business wins a Stripe Dispute with submitted evidence, the Webhooks will now process correctly to create a new Transaction that shows the funds were reinstated and credited back to the business.
• After winning a disputed charge in Stripe, the correct amount will be credited back to the account and reflected in the Retained Net Amount field.

DocumentLink

• When viewing an Invoice from a DocumentLink, the Phone provided on the DocumentLink Template will now appear in the Company Info section of the Invoice.
• An image added to the Footer section of a DocumentLink Template will no longer cause the Invoice to load incorrectly.

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