Winter '26 Seasonal Release
This is a list of every change made in the Winter '26 Seasonal Release of Nimble AMS.
Nimble AMS Staff View
What's New?
Enhancement: Hosted Payment Forms now support Credit Card Refund functionality
This update extends the Refund functionality to Hosted Credit Cards. Now, Orders purchased with a Hosted Credit Card can be refunded error free.
Your association will benefit if you allow:
Use of Hosted Payment Forms
Enhancement: Payment IP address tracking updates
To provide better security for our customers, there are several payment IP address tracking updates made to Community Hub and New Member Portal.
Added an IP Address field to the Payment sobject which will contain the IP Address of the user who made a credit card or ACH payment.
Added a toggle, ‘On’ by default, to send IP Addresses to Authorize.net.
Your association will benefit if you allow:
Use of Community Hub
Use New member Portal (built on Experience Community Hub)
Enhancement: Carts or Pro Forma Orders containing products with Deferred Revenue now process in bulk
Carts and Pro Forma Orders are the Invoice or Quotation Orders that do not create any transactions (no accounting impact) until they are processed. This improvement allows for Staff Order Entry process to submit a Cart with 200 items and the One Payment module to process and pay up to 200 Pro Forma Orders in bulk. The update also reduces the likelihood of exceeding the Salesforce governor limits while processing bulk Orders.
Your association will benefit if you allow:
Use Pro Forma Orders
Use Carts
Use One Payment
Defects Fixed
One Payment wizard opens to load Orders
The One Payment wizard fails to open when users click the OnePay button on the account page. The wizard spins but does not load Orders.
Your association may be affected if you:
Use One Payment
Original System Design: The One Payment wizard should open and load orders for selection.
Solution: Updated the One Payment wizard to open and display orders.
Module(s) impacted: One Payment
Existing Orders with added Chapter products create Account Affiliation record
In Staff View, while editing an existing Order, which already has 3 products ('Regular Membership,' Chapter product, required product) plus a MPTL donation for $1, the Account Affiliation record for newly add Chapter product is not created.
Your association may be affected if you:
Use Chapters
Original System Design: When an existing Order is edited by adding a Chapter product, the Account Affiliation record should be created.
Solution: When a Chapter product is added to an Order, the Account Affiliation record is created for added Chapter product.
Module(s) impacted: Chapters
reCAPTCHA displays on the first interaction of the Donate Now page
The reCAPTCHA prompt appears repeatedly when Logged-in users attempt a donation on the Donate Now page.
Your association may be affected if you:
Use reCAPTCHA
Original System Design: reCAPTCHA should only display once during the first donation interaction.
Solution: Now, reCAPTCHA will display on the first donation interaction for Logged-in users.
Module(s) impacted: reCAPTCHA
OnePay button opens One Payment wizard
In Staff View, on an account page the OnePay button is clicked but the One Payment wizard does not open, and the page continues processing without displaying Order details.
Your association may be affected if you:
Use One Payment
Use Pro Forma Orders
Original System Design: The OnePay button should open the One Payment wizard and load the Orders.
Solution: Misconfigured Orders will be prevented from displaying in the Orders list.
Module(s) impacted: One Payment, Pro Forma Orders
Membership Reinstatement dates now display correctly
In Staff View a Membership with a 999 month Reinstate Period and no Grace period is configured, which allows the purchase of a past or expired Membership for 1/1/2024 to 12/31/2024. The same constituent then Renews a Membership from Community Hub on July 22, 2025, this produces a Reinstated Membership with incorrect dates of 1/1/2025 to 12/31/2025. The Reinstated Membership dates should be 8/1/2025 to 7/31/2026.
Your association may be affected if you:
Use Membership Reinstatement
Original System Design: The Start Date of the Membership should be a future date rather than past dates.
Solution: Reinstatement Membership terms calculate correctly.
Module(s) impacted: Membership Reinstatement
Renewal Carts no longer include Join products
Renewal carts are included in the join MTPLS when the Renewal Carts are generated by Billing History. These products are specifically configured for Join but are included during the renewal process.
Your association may be affected if you:
Use Billing History
Use MTPLs
Original System Design: when billing History runs only products with a stage set to Renew MTPLs should be added to the Cart.
Solution: Renewal Carts now contain only renewal specific products.
Module(s) impacted: Billing History, MTPLs
Recurring Schedule cancelations successful
Sometimes Recurring Schedule cancelations, from the Order Item detail page, are prevented because the Order Item is edited to cancel the child Order Item lines, such as, removing or changing optional membership products. When this happens the Recurring Schedule Status component considers the Status value of the child Order Item line regardless of the active Status value of the Order Item.
Your association may be affected if you:
Use Recurring Schedules
Original System Design: The Recurring Schedule Status component should check the Status field against the Order Item.
Solution: Now, Recurring Schedules can be canceled when the Order Item Status is active even if it contains an inactive Order Item line such as a child Order Item.
Module(s) impacted: Recurring Schedules
Membership field now populates on Account Affiliation record
when a Membership is set to auto-renew and the original Order has a Chapter Membership, the renewal triggers the creation of the new Account Affiliation record. Once created the Membership field is not populated however, the OIL field is on the Account Affiliation record.
Your association may be affected if you:
Use Chapters
Use Recurring Schedules
Original System Design: Purchased Chapter Memberships should trigger the creation of Account Affiliation records including the new Membership’s term dates with the OIL and Membership fields populated.
Solution: Now, Membership records link with the Account Affiliations records populating the OIL and Membership fields.
Module(s) impacted: Chapters, Recurring Schedules
Recurring Schedules now respect Membership Start Date
Recurring Schedules force the Membership renewal start date to be the first of the month, rather than starting the day after the previous membership ends.
Your association may be affected if you:
Use Recurring Schedules
Original System Design: Recurring Schedules should set the Start Date to the day after the previous Membership date.
Solution: Now, Recurring Schedules respect the Membership Start Date
Module(s) impacted: Recurring Schedules
Credit Card information now saved in Payment record
When completing a payment using a Stored Payment Method through One Payment in Staff View, the Credit card related fields in the Payment record are not populated.
Your association may be affected if you:
Use One Payment
Use Stored Payment Method
Original System Design: The Stored Payment Method should populate the Credit card information fields in the Payment record.
Solution: Now, users will see the Credit card information saved on the Payment record when using the Stored Payment Method through One Payment.
Module(s) impacted: One Payment, Stored Payment Method
Unnecessary Queue Process records no longer created
For clients using Express Payment page when Guest Users are paying with Hosted Payment Forms in Community Hub, the payments are entered as a ‘SALE’ which triggers the creation of a Queue Process record. This Queue Process record then gets stuck and never processes, creating a need for the payment to be verified and a clean-up of records.
Your association may be affected if you:
Use Hosted Payment Forms
Use Express Payment page
Use BluePay
Original System Design: Payments entered as ‘SALE’ should not trigger the creation of a Queue Process record.
Solution: Updated logic in the payment gateway response to ensure payments with transaction type' SALE' are not marked as pending for capture. This prevents unnecessary Queue Process records from being generated.
Module(s) impacted: Hosted Payment Forms, Express Payment page, BluePay
Cancel Membership Mid-Term no longer adjusts Order Transaction Date
Clients using the Cancel Membership Mid-Term feature see the Transaction Date field updating for the Order, Order Item, and the Order Item Line and also making changes to the Deferred Schedule. This results in creating new Transactions for past periods.
Your association may be affected if you:
Use Cancel Membership Mid-Term
Use Deferred Schedules
Original System Design: The Transaction Date should not change on the Order, Order Item and Order Item Line when mid-term memberships are canceled.
Solution: Canceling a membership no longer modifies the existing Transaction Date on an Order.
Module(s) impacted: Cancel Membership Mid-Term, Deferred Schedules
Order Submission without payment successful with Avalara Tax
In staff View, an error occurs when submitting an Order, without payment, for a Taxable product when Avalara Tax is applied. This error message prevents Order submission and only occurs when Avalara Tax is applied.
Your association may be affected if you:
Use Avalara Tax
Original System Design: The Order should be submitted successfully without payment, even if a taxable product with Avalara Tax applied.
Solution: Updated the Tax calculating query to allow Order submission without payment when using Avalara Tax.
Module(s) impacted: Avalara Tax
Community Hub
What's New?
Enhancement: Capturing funds for failed Orders now prevented
In this update, the transaction type in the Hosted Payment Form request has been changed from SALE to AUTH. This ensures payments are authorized first and can be captured later, only if the Order is successfully processed. Additionally, a corresponding queue process record is now generated to handle the payment capture asynchronously, improving reliability and control over transaction flows.
Your association will benefit if you allow:
Use of Hosted Payment Forms
Enhancement: Server-side validation for credit card security code
Now during checkout, a server-side validation ensures the credit card security code is provided. This improvement increases security against card attacks.
Your association will benefit if you allow:
Use of Community Hub
Defects Fixed
One Payment button label displays ‘Complete Payment’ text
On the My Orders page in Community Hub, the button to launch the One Payment wizard is not labelled with text, ‘Complete Payment’ as in Staff View.
Your association may be affected if you:
Use One Payment
Original System Design: The One Payment button label should display text.
Solution: The One Payment button label in Community Hub now displays ‘Complete Payment’ text.
Module(s) impacted: One Payment
Registration Detail card displays during checkout
During the purchase of an event, the Community Hub My Checkout page does not display the Registration Details card when the Cart Item Lines empty.
Your association may be affected if you:
Use Registrations
Use Events
Original System Design: The Registration Detail card should display on the My Checkout page in Community Hub.
Solution: The My Checkout page now displays the Registration Detail card during checkout.
Module(s) impacted: Registration, Events
My Checkout page loads without error when Collapsible Membership Item Display feature is activated
Issue: Clients with the activated Collapsible Membership Item Display feature experience a My Checkout page loading error. This occurs when the feature consolidates the optional memberships into primary memberships during checkout with Express Payment.
Your association may be affected if you:
Use Collapsible Membership Item Display feature
Use Express Payment
Original System Design: The My Checkout page should load when the Collapsible Membership Item Display feature is active.
Solution: Updated logic to allow the My Checkout page to successfully load while Collapsible Membership Item Display is activated.
Module(s) impacted: Collapsible Item Display feature
Profile and Company Profile photos upload successfully
Community Hub users adding Profile or Company Profile photos experience a silent upload failure and only after the account record page refreshes understand there is no file uploaded.
Your association may be affected if you:
Use Profile photo
Use Company Profile photo
Original System Design: The Profile and Company Profile photo should upload to display on the account record in Staff View.
Solution: Now, Community Hub users are able to upload Profile and Company Profile photos.
Module(s) impacted: Profile photo, Company Profile photo
Invoice Date no longer adjusts on the Order record
When unpaid Orders created from Staff View are paid from the My Orders page in Community Hub, the Invoice Date changes to the day the payment is made. The Invoice Date on the Order record should not change.
Your association may be affected if you:
Use Orders
Use Express Payment page
Original System Design: The Invoice Date on the Order record should not change.
Solution: Now, the Invoice Date on the My Orders page in Community Hub will not change.
Module(s) impacted: Orders, Express Payment page
Member Portal
What's New?
Enhancement: Server-side validation for credit card security code
Now during checkout, a server-side validation ensures the credit card security code is provided. This improvement increases security against card attacks.
Your association will benefit if you allow:
Use of Member Portal
Enhancement: Member Portal sorts Orders in descending sequence by default
The My Orders page in Member Portal now sorts Orders in descending sequence to view the newest Orders at the top of the list by default.
Your association will benefit if you allow:
Use of Member Portal
Enhancement: Increasing credit card security
When Guest and Logged-In users for Member Portal make a donation or checkout, an IP address will be logged to the payment record, increasing credit card security.
Your association will benefit if you allow:
Use of Member Portal
Defects Fixed
Dynamic Filter now supports multi-select picklist
While setting up Dynamic Filter to utilize the multi-select picklist, to filter for categories, an error is displayed. The error displayed is “field<field name> cannot be grouped in a query call.”
Your association may be affected if you:
Use Dynamic Filter
Original System Design: The multi-select picklist field must be used as a filtering parameter and should not display an error message.
Solution: The multi-select picklist field usage as filter categories is now error free.
Module(s) impacted: Dynamic Filter
Now Saved Payment Methods delete as expected
Logged-in Member Portal users add a Saved Payment Method with Credit Card to an account. Then go to the My Payment Methods to delete the same payment method by clicking the trash can icon found on the Credit Card; however, the Saved Payment Method does not delete.
Your association may be affected if you:
Use Member Portal
Use Saved Payment Method
Original System Design: The Saved Payment Method should delete when the user clicks the trash can icon.
Solution: Updated code to delete Saved Payment Methods from the trash icon.
Module(s) impacted: Member Portal
CardPointe
What’s New?
Enhancement: CardPointe delay-capture now prevents failed ACH/eCheck payments from potentially causing further captures.
ACH and eCheck provide a secure and efficient way to make payments. Combining ACH and eCheck with Recurring Schedules allows for consistency when paying for Orders. The delay-capture logic now allows bank payments made by constituents as well as Recurring Schedules configured for ACH and eCheck to avoid duplicate capture attempts by removing the automatic retry for failures.
Your association will benefit if you allow:
Use of CardPointe
Use of ACH
Defects Fixed
CardPointe billing address updated in gateway
CardPointe transactions declined due to no address inside the CardPointe gateway, although the billing address details are filled in Nimble AMS.
Your association may be affected if you:
Use CardPointe
Original System Design: Nimble AMS billing address details should display correctly.
Solution: Now, billing address details are populated correctly in the CardPointe gateway resulting in transactions processing successfully.
Module(s) impacted: CardPointe
Seasonal Permission Changes
See the Winter '26 Seasonal Release Permission Changes in the Security section.