November 2024 - Version 6.26

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

Table of Contents

• Bug Fixes

• Enhancement

• DocumentLink

• Field/Layout Updates

• Upgrade Instructions

• Important Definitions

Bug Fixes

• Payment Method: When a user creates a card or ACH Payment Method with a Spreedly Payment Gateway from the Virtual Terminal, the Payment Method’s Payment Method Status will be set to “Valid.” Previously, the Payment Method Status field was blank after the Payment Method was created.

• Transactions: When a partial refund is issued for a Transaction, the refunded Transaction’s Amount reflects the correct amount, and the Transaction's Payment Status is set to "Partially Refunded." Previously, a refund Transaction was created for the full amount of the original Transaction, and the original Transaction's Payment Status was incorrectly set to "Refunded."

• Virtual Terminal: When users click the Reset button in the Virtual Terminal, previously populated fields will be emptied. Previously, clicking the Reset button caused nothing to happen. (Known Issue: 000003098)

• Authorize.net: If a user tries to save a new Payment Method with an incorrect zip code on an Authorize.net gateway, they will receive an error message letting them know that the Address Verification Security (AVS) failed and the Payment Method will not be saved. Previously, users received the following, confusing error message. "The element 'getCustomerPaymentProfileRequest' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd' has invalid child element 'unmaskExpirationDate' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'. List of possible elements expected: 'clientId, r" (Known Issue: 000003902)

• Disputes: When a Stripe dispute Transaction creates a refund Transaction, the refund Transaction’s Payment Status is set to "Refunded." Previously, when a Transaction was disputed and won, the refund Transaction did not have a value in the Payment Status field. (Known Issue: 000003522)

• Subscriptions: When a user manually pushes a Stripe Billing Subscription to Stripe, the Subscription Item will be updated with the Stripe ID. Previously, after the webhook occurred, a second Subscription Item with the correct information was created instead of the original Subscription Item being updated. (Known Issue: 000003035)

Enhancement

• The new custom checkbox field, Enable Authorize.Net CVV Filter, on the Payment Gateway allows users to require Attendees to re-enter their CVV code for Transactions using an Authorize.net gateway.

  • Field Label: Enable Authorize.Net CVV Filter

  • API Name: Enable_Auth_Net_CVV_Filter__c

  • Data Type: Checkbox

  • Help Text: When checked, transactions using an Authorize.net gateway will require the user to re-enter the CVV code for the card being used.

DocumentLink

Accessibility Enhancements

• The Download button on the Invoice now has a label that is readable by screen readers, improving accessibility.

• Duplicate content was removed from Invoices, stopping screen readers from reading all content twice.

• The contrast between an Invoice’s text and background was improved, improving the Invoice’s readability and ensuring it meets accessibility standards.

Field/Layout Updates

New

• Object: Payment Gateway

  • Field Label: Enable Authorize.Net CVV Filter

  • API Name: Enable_Auth_Net_CVV_Filter__c

  • Data Type: Checkbox

  • Help Text: When checked, transactions using an Authorize.net gateway will require the user to re-enter the CVV code for the card being used.

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.