--- title: "October 2022 - Version 5.76" slug: "payments-october-2022" tags: ["Release Notes", "Payments"] updated: 2022-10-04T17:32:14Z published: 2022-10-04T17:32:14Z canonical: "docs.blackthorn.io/payments-october-2022" excludeFromSearch: true excludeFromExternalSearch: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.blackthorn.io/llms.txt > Use this file to discover all available pages before exploring further. # October 2022 - Version 5.76 Once the updates listed below have been reviewed, please follow the [upgrade instructions](/v1/docs/payments-october-2022##upgrade-instructions) to upgrade your Payments application. **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](https://trailblazer.salesforce.com/issues_view?id=a1p4V0000010y6yQAA). ## Upgrade Instructions To upgrade Payments to the newest version, go to the [Blackthorn Candy Shop](https://candyshop.blackthorn.io/products). ## Off-Cycle Releases ### Version 5.75 (September 21, 2022) - Payment Methods created using a Spreedly / Cybersource Payment Gateway in the Virtual Terminal will now successfully capture Transactions. - A new Custom Setting called “Show Address” has been added to the Blackthorn Payments | Virtual Terminal Custom Settings. When the `Show Address` checkbox is enabled, additional address fields (`Street`, `City`, `State`, and `Country/Region`) will be visible on the Payment Method creation page in the Virtual Terminal. - We’ve resolved an issue related to failed Events checkouts when using an Authorize.net Payment Gateway. - Authorize.net users will no longer encounter a failed payment scenario when using the Virtual Terminal on a Contact record where the `Email` field on the Contact is blank. #### Version 5.75.1 (September 28, 2022) **The following update is a Feature Flag.** Users are now able to store a Payment Method created via the Spreedly integration in the Payment Gateway as well as interact with it outside of the Spreedly integration. - Custom Settings: Blackthorn Pay - Trigger Settings - New Field: `Save PM to Gateway Vault From Spreedly` - If `Save PM to Gateway Vault From Spreedly` = “TRUE”, the `Third Party Token` field on the Payment Method record will be populated. - If `Save PM to Gateway Vault From Spreedly` = “FALSE”, the `Third Party Token` field on the Payment Method record will NOT be populated. - Payment Method Object - New Field: `Third Party Token` - API Name: bt_stripe.payment_method.third_party_token ## Bug Fixes - When a Footer image is added to a DocumentLink Template and the Template is related to an Invoice, the downloaded Invoice pdf will display the Footer image correctly. - Clicking the `Deploy Stripe Billing` button on the Blackthorn | Payments Admin tab will successfully deploy the Stripe Billing fields to the Opportunity page layout. - [Custom Metadata](https://docs.blackthorn.io/docs/stripe-metadata) mapped fields in Stripe will now be populated automatically after completing the registration process for a paid Event. - After creating a new Subscription in Salesforce, the text added to the Memo field on the Subscription record will sync to the Memo field on the Invoice in Salesforce and subsequently in Stripe. **If you have any questions about this or need help with testing, please don't hesitate to reach out to [Blackthorn Support](https://community.blackthorn.io/s/support).**