--- title: "May 2024 - Version 6.18" slug: "payments-may-2024" tags: ["Payments", "Release Notes"] updated: 2024-05-28T15:54:09Z published: 2024-05-28T15:54:09Z canonical: "docs.blackthorn.io/payments-may-2024" --- > ## 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. # May 2024 - Version 6.18 Once you have reviewed the updates listed below, please follow the 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). ## Bug Fixes - After a payment is captured, the webhooks are processed, and the Transaction is refunded, the **Payment Status** will be set to “Refunded”. Only failed refunds will trigger an update to the Transaction’s **Payment Status**, **Retained Amount**, and **Retained Net Amount** fields. Previously charge.refund.updated webhooks would incorrectly update successfully refunded Transactions to **Payment Status** = "Captured". (Known Issue: 000003377) - When using Stripe Checkout for payments, the resulting **Transaction Status** will be correctly updated to “Completed,” and the related Payment Intent **Status** will be set to “Succeeded.” Previously, the **Transaction Status** was set to “Failed Payment Intent.” (Known Issue: 000003449) - When creating a new Payment Method in a Spreedly gateway, Payment Methods with either a 2 or 4-digit value in the card’s **Expiration Year** field will be correctly stored and synched to the Payment Gateway. Previously, 2-digit values in the **Expiration Year** field caused the Payment Method to be rejected. (Known Issue: 000003214) - After completing the checkout process via a TouchNet gateway, the related Payment Method’s **Holder's Name** field will populate correctly. Previously, the **Holder's Name** field remained empty. ## Enhancements - The **Chat** button on the Blackthorn | Payments Admin and Blackthorn | Payments Setup Wizard tabs has been deprecated. - The Payments app will now include the Event’s **Tax Fee** and Event Item’s **Tax-Exempt** fields in the Invoice/Transaction processing. This update is related to the foundational development of the feature and is not functional. **If you have any questions or need help with testing, please contact [Blackthorn Support](https://community.blackthorn.io/s/support).**