What's New

Now Available - Amazon Pay

Amazon Pay is now available upon request. To allow your constituents to register, purchase, and donate with Amazon Pay, contact customer support.

 

Version 26.2.1

August 2026

Optimized Forms: Expanded Setup and Configuration COMING SOON!

Optimized Forms include an intuitive wizard to make guided setup flow in the admin interface. Administrators can now more easily choose form type, configure payment behavior, and manage key donation settings from a unified workflow.

With these updates, your team can:

  • Choose Optimized form paths during form creation

  • Select merchant account behavior as part of form setup

  • Create beautiful branding cards to ensure your branding is immediately visible and consistent.

  • Make the donation experience modern and intuitive.

 

These improvements reduce setup friction and help teams move from form creation to launch efficiently.

Learn what makes these forms optimized.

 

Version 26.2

July 2026

Release 26.2 includes product updates that improve form setup, link management, TeamRaiser administration, and reporting visibility.


Link Manager and Bulk Update: Better Control for Large-Scale Link Changes COMING SOON!

Version 26.2 significantly expands Link Manager with stronger Bulk Update capabilities for high-volume link maintenance. Enhancements focus on guided replace workflows, better results visibility, and safer rollback behavior.

Screen capture of Bulk Update options

With these updates, your team can:

  • Run bulk find-and-replace updates from Link Manager with guided confirmation steps

  • Use expanded replacement options, including custom text replacement scenarios

  • Review improved results views and link-level detail outcomes

  • Use enhanced rollback and undo paths for safer large updates

  • Apply updates across additional domain scenarios to support secure link transitions

These enhancements help organizations perform large link cleanup efforts with more confidence, especially when preparing for full HTTPS usage.

Learn more about these features.

 

Nuclavis Text Messaging COMING SOON!

Example branded optimized form

Nuclavis text messaging is now integrated throughout Luminate Online. Reach your constituents where they are for appeals, calls to action, donations, and registrations.

Learn how to set up your mobile-first communications.

 

TeamRaiser Registration Quality: Expanded Spam Detection Tuning COMING SOON!

Building on prior registration protections, version 26.2 adds spam-detection tuning updates for TeamRaiser registration flows. This includes refreshed term handling and additional controls for common name-field edge cases.

With these updates, your team can:

  • Use refreshed spam-term coverage for registration validation

  • Apply improved detection behavior for title and suffix-related edge cases

  • Benefit from configuration updates that support more responsive policy changes

These enhancements help reduce unwanted registrations while preserving a smoother path for legitimate participants.

 

Donation Reporting and Payment Visibility COMING SOON!

Version 26.2 adds reporting and payment-data enhancements to improve operational visibility. Updates include new filtering options and expanded logging fields used for reconciliation and troubleshooting.

With these updates, your team can:

  • Use new payment and gift filters in Donations by Form reporting

  • Review expanded payment logging details for analysis and support workflows

  • Improve visibility into selected digital-wallet transaction details for operations teams

These updates help teams analyze transaction behavior faster and improve day-to-day financial and support workflows.

 

Donation Form Validation Controls COMING SOON!

Version 26.2 introduces stronger visibility and controls around HTML5 donation form validation behavior. Administrators now get clearer warning signals and supporting controls to manage validation strictness where client-side behavior differs by implementation.

With these updates, your team can:

  • Identify HTML5 attribute and validity concerns earlier in form design workflows

  • Review surfaced warnings in donor-screen design contexts

  • Use available controls to align validation behavior with implementation needs

These changes help reduce form friction and improve confidence before publishing donation experiences.

 

Issues Resolved

The following bug tickets were resolved for version 26.2.

1620017 | 2141021 Users saw a Technical Difficulties error when navigating constituents with long transaction histories.
Users can now navigate constituent transaction histories, even with high transaction volumes.
3173378 Users could not return some emails to draft status.
Users can now return emails to draft status.
3255087 Some constituent records did not display modified custom field labels.
Constituent records now display modified custom field labels.
3276101 PayPal transactions sometimes stalled in Pending status.
This fix ensures that completed and pending transactions from PayPal are captured and updated in Luminate Online.
3301720 Auto Login links did not work in Coaching Emails.
Auto Login links now work in Coaching Emails.
3363380 Payment Method sometimes displayed incorrectly as ACH in the service center.
Payment Method now displays correctly in the service center.
3518277 Survey questions did not always save correctly when users submitted responses in languages other than English.
Survey questions now save correctly when users submit responses in languages other than English.
3520191 Users who disabled Facebook Fundraising still saw prompts to fix Facebook fields.
Users who disable Facebook Fundraising no longer see prompts to fix Facebook fields.
3577047 Autoresponders created by API forms sometimes had malformed Forward to a Friend links.
Forward to a Friend links in autoresponders created by API forms now display correctly.
3578267 Administrators sometimes saw unexpected names when managing team donors.
Administrators now see the correct names when managing team donors.
3624667 The system sometimes marked successful recurring gifts as declined and retried them.
The system no longer marks successful recurring gifts as declined or retries them.
3640791 Subsequent recurring gifts sometimes failed when created with S1300.
Subsequent recurring gifts created with S1300 now process correctly.
3644187 Users could enter credit card information into name and address fields during TeamRaiser registration.
Users can no longer enter credit card information into name and address fields during TeamRaiser registration.
3648051 The Page Wrapper did not remain consistent when users moved between pages in the Gift Service Center.
The Page Wrapper now remains consistent when users move between pages in the Gift Service Center.
3657869 RELO sometimes set designation amounts incorrectly.
RELO now sets designation amounts correctly.
3679090 Event Fundraising Totals sometimes displayed Donor Cover fees incorrectly.
Event Fundraising Totals now correctly reflect Donor Cover fees when enabled.
3679807 Users could not navigate through pages when they had more than 20 sustaining gifts.
Users can now navigate through pages even when they have more than 20 sustaining gifts.
3698347 PayPal and Venmo sometimes displayed after users selected a recurring gift.
PayPal and Venmo no longer display as payment options after users select a recurring gift.
3703662 The TeamRaiser Comparison report sometimes returned a blank page.
The TeamRaiser Comparison report now returns results instead of a blank page.
3704558 Receipting did not always calculate secondary registration fees correctly for tax purposes.
Receipting now calculates secondary registration fees correctly for tax purposes.
3896010 RELO ticketed events did not sync donor cover information.
RELO ticketed events now sync donor cover information.
3923811 The getCompaniesbyInfo API method did not allow filtering by event type.
The method now allows filtering by event type.
3924558 Transaction history pagination sometimes skipped pages.
Transaction history pagination now displays all pages correctly.
3930634 The Participant Performance Report did not return the expected information when users applied some filters.
Participant Performance Reports now return the expected information when users apply filters.
3931200 Input tags in the page wrapper head caused content issues.
Input tags no longer appear in the page wrapper head.
3932296 Users did not understand how refunds worked for transactions with cover fees.
New messaging explains how refunds work for transactions with cover fees.
3936082 Administrative actions sometimes disconnected queries from groups.
Administrative actions no longer disconnect queries from groups unexpectedly.
3939956 In rare cases, transactions did not record all form information, which caused errors when users viewed the transaction.
Transactions now correctly record all form information on creation.
3941410 Individuals could download data from the participant center beyond what their role permitted.
Permissions now correctly restrict access to data in the participant center.
3952464 The Event Ticket Purchase autoresponder displayed incorrectly in some email clients.
The Event Ticket Purchase autoresponder now displays correctly across email clients.
3961665 The system sometimes opted new donors out of email when a transaction declined.
The system now correctly handles email preferences after declined transactions.
3984687 Multifactor Authentication messages sometimes included S Tag code.
Multifactor Authentication messages now display correctly.
3987142 Enabling reCAPTCHA could prevent offline TeamRaiser registrations.
Offline registrations now work with reCAPTCHA enabled.
3935050 | 3986992 Constituent merge processing sometimes failed intermittently in specific scenarios.
Constituent merge processing now behaves as expected.
4003115 Post-merge data was sometimes inconsistent.
Post-merge data is now consistent.

 

Version 26.1.2c

June 2026

Enhanced Protections for TeamRaiser Registration Integrity

To continue strengthening protection against unwanted or malicious registrations, this update builds on recent improvements to TeamRaiser validation and spam prevention.

These enhancements refine how registration activity is evaluated, helping detect more sophisticated patterns of suspicious behavior while maintaining a smooth experience for legitimate users. With these updates, you can:

  • Improve detection of evolving spam and automated registration attempts

  • Prevent registrations that contain offensive or inappropriate language, including drug‑related terms, while avoiding false positives on legitimate words

  • Reduce the likelihood of invalid participant and team records entering your system

  • Maintain cleaner participant data for reporting, management, and engagement

  • Better protect your organization’s public‑facing pages and overall reputation

This release also improves how content validation is applied across registration experiences. Rich‑text content, such as personal and team pages, is no longer flagged based on length alone, which helps ensure that valid submissions are accepted without unnecessary interruption.

When the system identifies a registration as potentially invalid, it prevents the submission and prompts the user to enter valid information. These improvements work alongside existing protections to provide broader coverage and more consistent enforcement.

This update reflects a continued investment in registration quality and platform security, with ongoing enhancements to help address emerging patterns while supporting legitimate user activity.

 

Version 26.1.2b

June 2026

Spam Detection for TeamRaiser Registrations

To help protect your organization’s brand and reduce unwanted content, TeamRaiser now includes enhanced validation for registration fields.

This update detects and blocks spam or offensive input during the registration process, preventing submissions that could otherwise appear on participant and team pages or surface in search results. With spam detection:

  • Prevent registrations that contain suspicious or inappropriate names
  • Reduce the creation of spam participant and team pages
  • Help protect your site’s reputation and search visibility

When a registration is identified as potential spam, the submission is blocked and the user is prompted to enter valid information.

Version 26.1.2a

May 2026

Release 26.1.2a addresses an issue with the ReportException error.

Resolved Issues

The following issues have been resolved in this release.

Bug Description

3918093

Donation classic reports return a blank page with ReportException error

You may have been unable to run certain classic donation reports. In some cases, the system returned a blank page with an error indicating an invalid column name.

This issue has been resolved. Classic donation reports now run successfully and return expected results.

 

Non-Release Update

April 2026

End of support for Akamai Identity Cloud Social Login Dashboard

Akamai has announced the end of support (EOS) for the Social Login Dashboard effective March 31, 2026. Customers will no longer be able to access the dashboard to manage or modify their configurations. Existing connections will continue to function, but administrative changes will require contacting Akamai Support. See When is the end of support for Akamai Identity Cloud Social Login Dashboard? for more information.

Luminate Online features that require Akamai open authentication are no longer available.  This includes setting up new social login integrations, monitoring, and reporting.

 

Version 26.1.2

March 2026

Release 26.1.2 includes infrastructure updates to support privacy and security.

 

Version 26.1

March 2026

In addition to the features and resolutions listed below, release 26.1 includes updates to infrastructure and security.

API Login Security Note

To adhere to best practices and security standards, do not pass username and password in URLs. Place those parameters in the body of a POST request. For more information see Parameters and Login in the API documentation.

Amazon Pay

Amazon Pay offers constituents another way to pay for shopping, registration, and donations. When you enable digital wallets with checkout Amazon Pay will automatically display similar to Google Pay. No setup required!

Spots are limited. To participate, contact Customer Support.

Note: Availability is limited for the initial release, but the feature will be released globally at a later date.

Warning: A known issue is currently being resolved. When you use Amazon Pay, the constituent receipt lists Blackbaud instead of the organization that received the donation, gift, registration, or other payment.

Enhance Content Powered by Blackbaud AI

Ready to transform the way you communicate with your fundraisers? Check out the brand-new Gen AI Content Writer & Tone Enhancer, a powerful tool designed to take the guesswork out of crafting effective communications.

This tool can:

  • Save you valuable time by drafting personalized, high-impact messages in minutes

  • Boost engagement with messages that resonate

  • Drive higher fundraising results through smarter, more consistent communication

  • Keep your existing S-tags intact so you can continue to display user data, track interactions, and include widgets.

See how Gen AI can help you work smarter, communicate better, and elevate your fundraising!

Look for Enhance Content in the WYSIWYG Content Editor in:

  • Autoresponders

  • Company pages

  • Donation form designers

  • Email (including New, Classic, and Coaching)

  • Greeting pages

  • PageBuilder

  • Personal pages

  • Team pages

  • TeamRaiser custom pages

  • TeamRaiser customized suggested messages (TeamRaiser)

  • Thank you pages

TeamRaiser Text Messaging with Nuclavis

Set up automated text messaging for TeamRaiser participants with Nuclavis.

Nuclavis Messaging is designed specifically for Peer-to-Peer (P2P) fundraising, transforming how organizations recruit, activate, and support their participants all from the palm of their hand.

With Nuclavis Messaging:

  • Send RCS messages (with fallback to MMS if RCS is disabled on their device) to currently registered participants.

  • Segment messages to team captains, team members & individuals, or target fundraisers based on amount raised.

  • Include personalized information including the fundraiser’s name, team name, event name and more.

  • RCS messages come from your verified brand, not a random short code or unknown number.

  • Include attention-grabbing CTA buttons such as Register Now, Add Calendar Event, or Download the Mobile App

  • Retain s-tags to include constituent names, track interactions, and add widgets.

It’s as easy as 1,2,3.

  1. Create an account with Nuclavis.

  2. Link your Nuclavis and Luminate Online accounts.

  3. Create automated messages to invite, remind, and thank your constituents.

See Nuclavis Text Messaging for more details.

Link Manager for Full HTTPS

Major browsers, such as Chrome, will soon require all public websites to use HTTPS. Starting in October 2026, insecure pages will trigger warnings or may fail to load. To protect your constituents’ experience and maintain trust, we are migrating webpages to full HTTPS. This ensures compliance with browser standards, prevents security risks, and avoids disruptions.

Use the new Link Manager to view a list of all files that contain links stored in Luminate Online. The list shows your sites, their status, and when they were last updated. Review links in active pages to identify any that need to be converted to secure access. Within the Link Manager list, identify HTTP links and select Edit to update them to HTTPS.

Domain Names and SSL Certificates

If you have a custom secure domain that you manage, or if you manage a custom secure domain installed by Blackbaud, use Link Manager to update HTTP URLs to HTTPS URLs.

Note: Blackbaud installed custom secure domains managed by customers prior to 2018. This service is no longer offered.

If you do not want a custom secure domain, your URL will start with secure2.convio.net or secure3.convio.net, and URL branding will be lost. This option is not recommended.

If you want to purchase a new custom secure domain prior to migration to full HTTPS, you need a new sales agreement before URL updates can occur. Blackbaud will purchase and manage the SSL certificate for the domain you provide. Contact your Blackbaud representative or Customer Support to get started.

More Fee Cover Features

Personal Fundraising now includes fee cover. Fee cover data has also been added to reports for monitoring donations, registrations, purchases, and more.

 

Issues Resolved

The following bug tickets were resolved for version 26.1.

Ticket NumberReported IssueResolution
3642184When honoree first name and last name are required some payment methods including PayPal, ApplePay, GooglePay, Credit Card are progressing to the next screen until the request is submitted twice.Payment method window displays after single request is submitted.
3629741Reports Classic Transaction reports include duplicate rows.

Reports Classic Transaction reports render as expected.

3620742Content editor WYSIWYG update prevents navigation to insert/edit image with the image library.Image insert and edit with the image library works with the updated content editor.
3627973S-Tags in autoresponders are not properly calculating and populating when using Fee Coverage options.

S-Tags in autoresponders are properly calculating and populating when using Fee Coverage options.

3629851Session timeout page formatting is wrong.Session timeout page renders correctly.
3309837Direct debit transactions that fail due to security requirements fail in Blackbaud Integrated Payments (no funds collected), but appear as successful in Luminate Online.Transactions that fail due to security requirements are not logged as successful in Luminate Online.
3428521S-120 tag does not include additional gifts in the total amount displayed.S-120 tag does include additional gifts in the total amount displayed.
3518277When multi-locale is enabled, answering some multiple choice questions always return an error. Valid answers to multiple choice questions are accepted regardless of multi-local settings.
3591998The transaction for the first payment made after the credit card updater changes a payment method from digital wallet to credit card does not capture credit card details.The transaction for the first payment made after the credit card updater changes a payment method from digital wallet to credit card captures credit card details.
3619425Donate button is missing on donation forms.Donate button displays as expected.
3626461Attempting to process refunds results in errors.Refund processing proceeds as expected.
3614187Data entered by the user is not stored in valued_transaction or constituent if it is a record created by the transaction.Data entered by the user is not stored as expected.
3553129Multicenter TeamRaiser autoresponders use the site default reply-to email address instead of the specified sender's email address.

Multicenter TeamRaiser autoresponders use the specified sender's email address.

3575593Canadian direct debit PAD confirmations are sent on first and second transactions of recurring payments.Canadian direct debit PAD confirmations are sent on the first payment and updates to recurring payments.
3561086Report results page displayed with errors in highlighting patterns and row and column size.Report results page displays as expected.
3422144API method getTeamMembers returns visible participant pages when the participant has set privacy setting to private.

API method getTeamMembers respects participant privacy setting.

3347937Card holder name appears in the first, but not subsequent, sustaining gift payments.Card holder name appears for all sustaining gift payments.
3349434Refunds for sustaining gifts do not always apply the refund to the most recent transaction.Refunds for a sustaining gift are always applied to the most recent transaction.
3355355Participants are logged out after defined inactivity limit even when F2F_PARTICIPANT_CENTER_COOKIE_LOGIN=TRUE.

Participant sessions remain active until logout when F2F_PARTICIPANT_CENTER_COOKIE_LOGIN=TRUE.

3330107S-48 tags return the value of a delayed self pledge and additional upsell fees.S-48 tags only return the value of the delayed self pledge.
3264754Autoresponder bounce rates logged as hard bounce when soft bounce and vice versa.Autoresponder bounce rates logged correctly.
3388816Company field missing from reports when participants register with an association to a company but without a team.Company field included in appropriate reports regardless of team membership.
3391653When registering participants from the Event Management Center, the minimum fundraising goal always displays $0.When registering participants from the Event Management Center, the correct minimum fundraising goal is displayed.
3423796When using the search feature in Constituent Transactions, the page refreshes and no results are returned.Constituent Transaction searches return results when appropriate.
3424880Uploading TeamRaiser registrations with blank Goal fields results in a value of $0 in the recorded Goal field. Uploaded TeamRaiser registrations with a blank Goal field do not record a goal.
3427921Answers to Yes/No questions on Calendar Events are always saved in English.Answers to Yes/No questions on Calendar Events are saved in the language set in Multi Local configuration.
3504106S-416 tags do not render images correctly.S-416 tags render images correctly.
3505073Starting plain text content of an email message with a URL results in an error.Starting an email message plain text content with a URL works as expected.
3511289Phone numbers collected via API donation forms using donor.phone_type=mobile are recorded as the Primary phone.When donor.phone_type=mobile, phone number is recorded as expected.
3519103

When registering for a TeamRaiser event with multi-locale enabled, selecting next on the Participation Options dialog results in an error.

Regardless of multi-locale settings, selecing next after entering valid Participant Options proceeds to the next step in the registration process.
3520392When some requests are made to a specific servlet the com.convio.exception.CVRuntimeException: no application with servlet name https error is returned.Valid requests to the servlet are processed as expected.
3527453When participants are drafting emails in participant center and are logged out due to inactivity, the email draft is not saved. Email drafts are saved prior to logout due to inactivity.
3548989Selecting Donor Information Same as Billing Information during checkout does not pre-populate fields as expected.Selecting Donor Information Same as Billing Information during checkout pre-populates fields as expected.
3567572Discount codes are not applied when administrators enter TeamRaiser registrations for participants using credit cards.Discount codes are applied as expected.
3568760Co-captains are not able to edit team captain messages.Co-captains are able to edit team captain messages.
3575419Custom UI Java Script code in new Participant Center 2 instances is not displayed as expected to the end user.

Custom UI Java Script code in new Participant Center 2 instances is displayed as expected.

3578297When a participant registered for an event with delayed self pledge at one amount, and the registration fee was later adjusted to a second amount, the participant's pledge amount is showing that second amount.The original, confirmed amount of a delayed self pledge registration is maintained even if the registration fee is later changed.
3584236

An obsolete Convio contact page surfaced for some rare errors.

Obsolete Convio contact links have been replaced by current Blackbaud contact information.

3589345When adding new groups to a query, it is possible to sever the connection between the query and groups previously connected to it without warning.Aborting the process to add new groups to a query does not sever the connection between the query and groups previously connected to it.
3591373Only the first 25 contacts are visible in a Participant Center 2 contact list.Navigable pagination has been added to Participant Center 2 contact lists.
3592490When using the S-48 delayed self pledge tag and Yes, count registration fees towards fundraising goal is not selected, the transaction amount calculations are wrong.

When using the S-48 delayed self pledge tag and Yes, count registration fees towards fundraising goal is not selected, the transaction amount calculations are correct.

3598137The Position field on the constituent profile record is recording special characters as extended ascii characters, causing csv exports to download as ANSI.Special characters are not recorded as extended ascii characters.
3601043Calendar events automatically use a default merchant account.Administrators select an available merchant account for calendar event payment processing.
3612227The Donation Form Timeline Report sometimes results in error messages and empty graphics.

The Donation Form Timeline Report runs as expected.

3623019Switching between the Plain Text and WYSIWYG content editor modes deletes code.

Switching between the Plain Text and WYSIWYG content editor modes does not delete code.

3625075

3626261

3691640

When multi-locale is enabled, timeout messages are not displayed in the assigned locale language.

When multi-locale is enabled, timeout messages are displayed in the assigned locale language.

3626685

S-1tag personalization components do not render correctly with the content editor WYSIWYG update.

S-1tag personalization components render correctly with the content editor WYSIWYG update.

3641380Errors occur when email campaigns are deleted while messages in that campaign are still scheduled to send.Links from orphaned email messages to the events calendar are removed, preventing the error state.