This is a list of every change made in the Summer '26 Seasonal Release of Nimble AMS.
Nimble AMS Staff View
Defects Fixed
Payment Fails in Auth.net when Account Name Exceeds 50 Characters
When an account name is longer than 50 characters, the payment flow fails for Auth.net. This occurs during one-payment processing and the processing of Pro forma Orders. Users received a Payment Failed error, which prevented the payment from completing.
Your association may be affected if you:
-
Use Auth.net
-
Use Pro forma Orders
Original System Design: Payments should be processed successfully even when the account name exceeds 50 characters.
Solution: The billing first and last names are now truncated before being sent to the payment gateway, allowing payments to complete successfully.
Module(s) impacted: Auth.net, Pro forma Orders
Fixed Revenue GL Override Value Validation Restrictions
The GL Account Revenue Override Wizard incorrectly restricted values to less than $100. Now, the Create/View Revenue GL Override flow allows Revenue GL Value fields to be amounts greater than $100.
Your association may be affected if you:
-
Use GL Override/Split Revenue feature
Original System Design: The Revenue GL Value fields should support higher dollar amounts.
Solution: Resolved the GL Account Revenue Override Wizard issue where Revenue GL values were restricted. Users can now enter values greater than $100 for Revenue GL fields.
Module(s) impacted: GL Override/Split Revenue
Cancel Membership Mid-Term refund incorrect amount
An issue was identified in the Cancel Membership Midterm refund process where refunds for whole-dollar amounts (for example, $45.00) were processed incorrectly while using the CardPointe gateway. In these cases, the system refunded the cent-equivalent amount ($0.45) through the Payment Processor, while Nimble AMS recorded and displayed the refund as the full amount ($45.00).
Your association may be affected if you:
-
Use Cancel Membership Mid-Term
-
Use CardPointe
Original System Design: Cancel Membership Midterm refunds should refund the correct amount and in the correct currency format including decimals.
Solution: Updated the Cancel Membership Mid-Term refund process to round the refund amount to the cent before sending it to the Payment Processor, ensuring the correct refund value is processed.
Module(s) impacted: Cancel Membership Mid-Term, CardPointe
Membership Flow Down Batch Processing Improvements
Membership information from Company Accounts was not consistently flowing down to affiliated Individual Accounts. The flowdown process depends on Flowdown Queue records, and processing could stop when a single queue record encountered an error. If a queue record referenced a deleted, merged, or otherwise invalid Account, or a deleted Membership, the entire batch job would fail — preventing subsequent records from being processed and leading to significant queue backlogs and delayed Membership updates.
Your association may be affected if you:
-
Use Information Flow Down
-
Use Membership Flow Down
Original System Design: The flowdown process should not stop the processing of the entire batch.
Solution: Converted the Flow Down update process to be asynchronous, preventing a full transaction rollback in the event of a partial failure. Records that process successfully are trimmed, while failed record IDs are retained in the Data field of FlowDownQueueDetails records to facilitate troubleshooting and tracking of partial failures.
Module(s) impacted: Information Flow Down, Membership Flow Down
Refund fails with “Above Max Amount” Error for Orders with Multiple Payments
When multiple payments exist for an order, attempting to process a refund results in the error message, "Above max amount." The system appears to select only the first payment and attempts to apply the entire refund against that payment, rather than evaluating all associated payments. As a result, the refund amount exceeds the selected payment amount, causing the error.
Your association may be affected if you:
-
Use Stored Payment Method
-
Use Refunds
Original System Design: The refund amount should be distributed across the payment ling sequentially, respecting the remaining refundable balance for each payment line.
Solution: Updated logic to pull all the payment lines associated with the Order. Now staff will pick the original Stored Payment transaction from the dropdown (filtered by product), and the remaining refundable amount is tracked per transaction.
Module(s) impacted: Stored Payment Method, Refunds
Refund Processing Error for Apple & Google Pay Support Transactions
Staff users receive an error in the Order Processor when attempting to refund payments originally made via Apple & Google Pay Support. The issue occurs despite selecting Credit Card as the refund method.
Your association may be affected if you:
-
Use Apple & Google Pay Support
-
Use Refunds
Original System Design: Refunds should be successfully processed when the original Order is paid with Apply & Google Pay Support.
Solution: Now, the digital wallet payment lines are included in the refundable Credit Card dropdown when the original Order is paid with Apple & Google Pay Support.
Module(s) impacted: Apple & Google Pay Support, Refunds
Member Portal
Defects Fixed
Join Now Button Displays on Personal Snapshot page for Active Members
On the Member Portal Personal Snapshot page, users with active memberships continue to see the Join Now button despite already being active members. Their account also has the Member flag set to Yes.
Your association may be affected if you:
-
Use Member Portal
Original System Design: Users with an active membership should not see the Join Now button.
Solution: The Member Portal Personal Snapshot page will not display the Join Now button for active members.
Module(s) impacted: Member Portal
Express Payment Error When Processing Non-Self-Service Pro Forma Orders via Experience Cloud Checkout
Some Member Portal users received an error message indicating that non-Self-Service Products could not be processed through Express Payment. This issue occurs when a Pro Forma Order is created in Staff View for a non-Self-Service Product, and the user then opens the Experience Cloud Checkout URL in a new browser window to complete payment. Instead of the Order being processed successfully, the user receives an error message during checkout.
Your association may be affected if you:
-
Use Member Portal
-
Use Express Payment
Original System Design: Pro forma Orders for a Self-Service disabled product in Staff View should process and the user should receive the Order Summary screen.
Solution: Users will be able to make payments for Staff View generated Pro forma Orders using Express Payment, even when the associated Product is not Self-Service enabled.
Module(s) impacted: Member Portal, Express Payment
Nimble Create Extension
Defects Fixed
Entity Organization-Wide Email Address Not Overriding Template Email for Order Confirmation/Invoice Emails
In Staff View, when sending an Order Confirmation or Invoice email, the email address specified in the template should be overridden by the Entity Organization-Wide Email Address. However, the template email address is being used instead of the Entity Organization-Wide Email Address.
Your association may be affected if you:
-
Use Nimble Create Extensions - Email Functionality
Original System Design: Entity Organization-wide email address should override the template Email From field when Staff users send the Order Confirmation or Invoice.
Solution: Updated the logic to a global setting to be used when the entity-level and template-level OWEA are not configured.
Module(s) impacted: Nimble Create Extensions - Email Functionality
Seasonal Permission Changes
See the Winter '27 Seasonal Release Permission Changes in the Security section.