What's Recent

To process transactions when a credit or debit card is not physically present (such as back office mail-in or phone donations), you can now enter offline credit and debit card gifts without requiring the card’s security code (CVV). While the CVV field still appears, it is now optional.

Previously, CVV was mandatory for offline gift entry unless using the S1300 Tag process. With this update, you can process individual or batch offline entries with or without the CVV code directly through checkout modal.

Requirements

• The donation form must use checkout modal.

• Not compatible with checkout embedded.

• Works within Luminate Online only.

• Not compatible with external websites or applications.

• Requires a checkout-enabled merchant account.

• No separate merchant account or payment gateway is required.

Note: Direct debit support is coming soon.

For detailed steps on using this feature, see Offline donations. Follow the steps to set up an offline donation form and enter your offline card transactions.

So that you can add gifts through checkout for companies that span multiple TeamRaiser events, the checkout solution now supports gift entry for National Cross-Event Companies in TeamRaiser.

See Add a Gift for a National (Cross-Event) Company.

Previously, the getParticipants API could return newly registered participants with "null null" for names until participant processing completed. This could sometimes lead to temporary inconsistencies in participant data for API consumers.

With this release, participants whose names have not yet been populated are now excluded from getParticipants API responses. until their names are fully populated. This change eliminates the brief window where incomplete participant records were returned, ensuring more accurate and reliable data for consumers.

To ensure PCI compliance, we now automatically add the Checkout modal data element to donation forms that are moved out of archive status into active status.

We've also updated the user interface to help you recognize this change.

See Restore an archived form.

We’ve enhanced Good Move App Setup to support multi-lingual public event names, ensuring consistency with the language-specific values entered in the Identify TeamRaiser step.

Public Name values for English (US), French (Canada), and Spanish (US) now sync to their corresponding language tabs in the Good Move app.

See Configure Good Move App Event Details.

The deprecation of Yahoo’s legacy Social Directory APIs disabled the existing Yahoo contact import functionality in the Participant Center, so we've removed the option. We're currently exploring a new Yahoo protocol that would allow you to use your own Yahoo-subscribed APIs.

Participants can always manually import Yahoo contacts by:

1. Exporting contacts from Yahoo.

2. Importing them into Participant Center via CSV.

For help, see Import contacts from Yahoo into the Participant Center.

We've enhanced internal logging to verify the correct application name of either Luminate or TeamRaiser

We've added additional messages and data to aid in analysis of custom form issues

Internal testing and improvements implemented for the May 1st Auto-Migration Compliance Script.

The checkout payment experience was enhanced to reduce processing time.

When processing a donation, the spinner now briefly displays a "Processed" message to confirm that the donation is actively working. This provides feedback to reassure donors that their transaction is progressing. The "Processed" message is available in English, French, and Spanish and requires no action to implement.

When unarchiving forms, a message now clarifies that archived forms were not auto-migrated with checkout and should be updated with checkout prior to use.

TeamRaiser registration forms now offer a choice to use either a modal or embedded checkout, allowing you to customize the payment experience for participants.

With the embedded checkout option, payment methods appear directly on the registration form page, instead of in a pop-up modal.

To offer embedded checkout on your TeamRaiser registration form, choose the Checkout embedded option during configuration of the TeamRaiser's Payment Page.

Note: To offer embedded checkout, configure your TeamRaiser to support checkout if it isn't already. See Checkout in TeamRaiser.

How do I update my TeamRaiser registration form to use embedded checkout?

1. Go to Fundraising, TeamRaiser.

2. In the Action column of the TeamRaiser, select Edit.

   Tip: For live, published forms, you may consider making a copy of the form to update and review changes before publishing instead of working with the live form. However, remember that this will create a new URL with a different donation form ID.

3. Go to Customize Pages, and in the list of TeamRaiser Pages, locate the Payment Page and select Configure.

4. In the Payment Options section, select Checkout embedded.

   Select Finish.

5. Verify your form renders as expected prior to publishing.

Note: Preview does not display checkout.

To support a multilingual Good Move app experience that aligns with your fundraisers’ preferred languages, you can customize some TeamRaiser content in English, Spanish, French, and French (Canada). You can also set the default language to a language other than English.

From Good Move App Setup in TeamRaiser, now you can enable multilingual functionality for your App Event Details and Message Templates.

Once you’ve enabled multilingual functionality, you can manage notifications in those languages from the Good Move Notification Manager.

Canadian direct debit, also called Automated Clearing Settlement System (ACSS), is now available for payment processing through checkout for one-time and recurring gifts, in both the modal and embedded checkout options.

To comply with Canadian payment mandates, donors see a pre-authorization agreement (PAD). The PAD agreement occurs between an account holder and a merchant, and it authorizes the merchant to withdraw funds from the holder’s account on a recurring basis.

When you enable direct debit on a form, checkout processes a PAD from a Canadian bank account, collects the mandate acceptance, and sends the agreement to the donor in English and French.

PAD mandates (ACSS agreements) are available for your review at any time. Access the Mandate URL, Mandate ID, and Mandate Sent Date in the Transaction Details, and TeamRaiser Gift Details reports.

A new mandate is generated whenever there is a change to the recurring gift.

Tip: ACSS is the acronym used for Canadian direct debit, while Automated Clearing House (ACH) is for US direct debit.

How do I offer Canadian direct debit as a payment option in checkout?

Although there is no specific action needed to configure support for Canadian direct debit, you do need to make sure you are set up to process CAD payments and that you have direct debit options enabled on your forms.

To ensure your donation forms provide direct debit as a payment option, review your donation form's checkout element to make sure the Direct debit option is enabled. See Checkout embedded or Checkout modal.

For a TeamRaiser registration, include the Direct debit option on the event's payment page. See Configure the Payment Page of a TeamRaiser Event.

REMINDER: To meet PCI v4 compliance, update your active API-based forms to use the new checkout APIs. Although the previous transaction-handling Luminate Online APIs remain valid until May 1, 2025 to ensure no impact to your existing donation forms during giving season, the new or updated PCI v4-compliant APIs are available in this release so you can begin testing.

Important API order of operations clarification for "applicationName"

When making a checkout payment call through a TeamRaiser API (such as addGiftCheckout or processRegistration), first call getTeamRaiserConfig to retrieve the applicationName of TeamRaiser, which should be passed in the checkout call.

Similarly, when making a checkout payment call through a Donation API (such as donateAch or donateCheckout), first call getDonationFormInfo to retrieve the applicationName of Luminate, which should be passed in the checkout call.

Forms that use the previous APIs will continue to work until May 1, 2025; however, make plans to identify your active (or soon-to-be-active) forms, then understand the methods you must change.

Warning: The previous methods listed below were deprecated starting May 1, 2025.

Note: If you use addGift for offline payments, update the method to addGiftCheckout.

Donations by Transaction report update

In Donations Management, Donation Reports, the Donations by Transaction report now shows the Tender Type Name and Tender Instance Name so you can identify the payment type used for the donation and have consistency with the Transactions Details report in Report Writer.

For more information, see Donations by Transaction report.

As part of ongoing security efforts, jQuery libraries in Luminate Online will update to version 3.7.1 on April 23, 2025. jQuery is a JavaScript library that simplifies HTML document traversal, event handling, and animation. If your site uses a jQuery version in a form or PageWrapper for a customization, review the information below and take action to avoid unexpected behavior.

Note: Multiple jQuery versions in your UI code can cause conflicts and problems. Review your code to ensure your pages work with Luminate Online's jQuery version 3.7.1.

What issues occur when there's a jQuery version conflict?

Multiple versions of jQuery on the same page can cause conflicts and issues. In Luminate Online, issues can vary, but we're aware that on an embedded checkout form, a spinning wheel can occur when custom jQuery code in the Page Wrapper or the donation form's HTML Caption data element conflicts with jQuery code used by Luminate Online. The spinning wheel prevents the form from functioning correctly.

As of April 23, 2025, Luminate Online will use jQuery version 3.7.1.

Why do jQuery version conflicts occur?

When more than one jQuery version attempts to load on the same page, the methods and variables can overwrite each other, causing unexpected behavior or errors.

For example, if one jQuery version uses the $ symbol as a shortcut for jQuery and another library or version also uses $, one or both libraries can malfunction.

What do I need to do?

To ensure customizations are not impacted, review your PageWrappers and forms for custom jQuery versions.

If you locate a version that is not 3.7.1, either remove the version or update your code to include jQuery.noConflict()before the jQuery version used in your custom code.

Tip: Placing jQuery.noConflict()before your custom jQuery code releases the hold on the $ shortcut identifier, allowing Luminate Online's jQuery version to function without interference.

In the Page Wrapper:

1. Review the configuration of your Page Wrapper to identify any custom jQuery code that might cause conflicts.

2. If you find a conflict, make a copy of the Page Wrapper.

3. In your Page Wrapper, you can either:

   • Remove the conflicting version of JQuery.

     --or--

   • Update your code to include jQuery.noConflict() before the custom JQuery code, so that it doesn't conflict with the existing jQuery version in Luminate Online.

   For editing guidance, see, Edit an existing version of a wrapper.

In the HTML Caption data element on your donation form:

1. Go to Fundraising, Donation Management.

2. Select Manage from the Actions column for the campaign.

3. Select Edit from the Actions column of the donation form.

4. On the left, select Design Donor Screens.

5. In the list of Donor Screens, select Edit from the Actions of the donation form.

6. In the Form Designer right pane, select the HTML Caption element and select Save Order and Edit Selected.

7. Select the Edit Data Element tab, if not already selected.

8. Review the contents for custom JQuery code added to your form. For example, the image below shows the addition of jQuery version 1.7.2.

9. In HTML Content, you can either:

   • Remove the conflicting version of jQuery.

     --or--

   • Update your code to place jQuery.noConflict()before the custom jQuery code, so that it doesn't conflict with the existing jQuery version in Luminate Online.

10. Click Finish.

11. Validate the jQuery version in the browser console with the command, $.fn.jquery. Until the March 18 25.2 release, the jQuery version should return as 3.6.0. Beginning on April 23, 2025, the jQuery version should return as 3.7.1.

The Luminate Online 25.2.0b release includes an enhanced processing improvement and improved internal logging for transactions flowing through checkout.

Sustaining donors updating their billing or gift information in the Gift Service Center for a gift associated with a checkout donation form will see classic Blackbaud Checkout to complete their update. This update ensures PCI v4 compliance and applies to the original and current versions of Gift Service Center and supports Canadian currency.

Note: Donors who update billing information or recurring gifts on non-checkout donation forms will not see a change until May 1 when credit card fields will no longer be available on non-checkout donation forms.

We've also introduced new API methods, updateRecurringCheckoutPaymentInfo and validateRecurringCheckoutPaymentInfo, to support updates made by a logged-in user.

In Luminate Online, administrators making updates on a sustaining donor’s behalf in Sustaining Gifts area of Donation Management now also see classic Blackbaud Checkout modal when completing updates on a form enabled with checkout. See Update Sustaining Gift Payment Details.

When a supporter chooses a digital wallet payment option on a form with embedded checkout, the button to process the payment now appears centered below the billing fields.

Offline gifts in Donation Classic now support the new checkout payment processing feature, expanding on the online support offered in the 25.1.1 release. This update includes support of Canadian currency.

To configure offline forms in Donations Classic for checkout, select a checkout-enabled merchant account in the donation form configuration. After the update, the checkout modal will appear for payment processing.

For more details, see Checkout in Donation Classic.

To help with reconciliation between PayPal and Blackbaud transactions, PayPal now displays the Blackbaud Transaction ID under the custom_ID category when viewing a Blackbaud transaction in your PayPal business account. Previously, the custom_ID value displayed "Blackbaud."

To enhance payment updates for the checkout process, we've introduced new APIs:

• updateRecurringCheckoutPaymentInfo - This method, designed for the Gift Service Center, allows logged-in users to update their credit card information for recurring gifts using a secure token.

• validateRecurringCheckoutPaymentInfo - Also supporting the Gift Service Center, this method ensures all required values are provided when updating payment information for logged-in users.

• donateACH - This method processes direct bank debits through the United States Automated Clearing House (ACH) and Canadian Automated Clearing Settlement System (ACSS) with legacy merchant accounts.

To allow for the use of Legacy Blackbaud Checkout to continue so your customizations can persist in forms, we've updated our infrastructure to ensure that you can use the Legacy Blackbaud Checkout, launched with the S1300 tag, within a checkout-enabled campaign and form.

See Checkout using the S1300 Tag.

With Credit Card Updater, you can now see whether the last attempted card update was successful in the Blackbaud Merchant Services Web Portal. This information is helpful to know when to contact a donor for updated card information.

In the Blackbaud Merchant Services Web Portal, go to Reports, Credit card updater. Under Status, you'll see the whether a card was marked as Updated or Could not update.

For more information, see Credit Card Updater in the Blackbaud Merchant Services documentation and Credit Card Updater Service in the Luminate Online documentation.

• Child TeamRaiser Blueprints now display in the Good Move Notification Manager.

• Team page updates now automatically send to Good Move, including the team story and photo.

• Personal page updates now automatically send to Good Move, including a participant's page title, story, and photo.

The following areas of Luminate Online now support the new checkout payment process. Canadian currency is also supported.

Ticketed Events

Payments for ticketed events can now launch the new checkout feature. To configure your ticketed event for checkout, select a checkout-enabled merchant account on the Edit ticket information step of the event configuration.

After the update, the checkout modal will appear for payment processing.

See Checkout in Events.

eCommerce

Store purchases can now launch the new checkout feature. To configure your eCommerce store for checkout, select a checkout-enabled merchant account on the Change the Store Merchant Account configuration page.

After the update, the checkout modal will appear for payment processing.

See Checkout in eCommerce.

Personal Fundraising

Payments and donations for personal fundraising campaigns can now use the new checkout feature.

To configure personal fundraisers to use the new checkout in a new campaign, select a checkout-enabled merchant account in the personal fundraising campaign configuration.

To configure personal fundraisers to use the new checkout in an existing campaign, Edit the campaign, then select a checkout-enabled donation form and campaign in the edit campaign details section.

After the update, the checkout modal will appear for payment processing.

See Checkout in Personal Fundraising.

Donation Classic

The new checkout feature is now supported in Donation Classic for online gifts. Offline gifts will be available in a future release.

To configure Donation Classic forms to use the new checkout, select a checkout-enabled merchant account in the donation form configuration.

After the update, the checkout modal will appear for payment processing.

Embed a Donate Button

When using the Embed a Donate Button feature, the new checkout modal launches to guide donors through the payment process. The initial window now requires the following fields to comply with guidelines and requirements:

• Email

• First name

• Last name

• Zip code

• Country

To use the new checkout in the Donate button, use the code found in the Publish step from a donation form that is associated with a campaign configured for the new checkout.

S1300 Tag Version of Blackbaud Checkout

With this release, you can either continue offering your existing configuration for the S1300 Tag version of Blackbaud Checkout or set up a new S1300 Tag form using the new checkout.

To use the new checkout in the S1300 Tag version of Blackbaud Checkout, reference a donation form ID of a donation form and campaign configured for the new checkout.

See Checkout using the S1300 Tag.

New in this release, all donors must now provide the following additional information before continuing to payment to comply with guidelines and requirements:

• Email

• First name

• Last name

• Zip code

• Country

After entering this information, donors select "Give securely" to launch the new checkout modal.

Event Manager Center

The Event Manager Center now supports the new checkout feature wherever payments are taken by Event Managers and Company Coordinators.

Improved Checkout Support for California Assembly Bill (AB) 488

The checkout process was enhanced to fully support compliance with California AB 488.