General Questions about Checkout

Our 2024 and 25.1 releases provide new checkout support for donation forms, online and offline TeamRaiser registration and gifts using checkout modal, Participant Centers, eCommerce, Personal Fundraising, Ticketed Events, Event Management Center, Donations Classic, and Embed a Donate Button.
In our upcoming 2025 releases, we will provide checkout support for the Gift Service Center and embedded (inline) checkout for TeamRaiser registrations.

Existing forms will continue to work with existing configurations up to the compliance deadline date in March 2025.

No. Changing forms to inactive/archived does not impact your scheduled recurring transaction processing.
Once a form processes a payment, the donation data is changed to a token within Luminate Online and used in an automated workflow process for charging and processing recurring gifts. The gift data is not tied directly to the form it was collected from.

Archiving a page or a donation form means moving it to a separate section for storage or reference purposes, making it no longer active or visible on the main list. On the other hand, unpublished pages or donation forms are still in the system but are not currently viewable or accessible to the public.
When a page or donation form is archived, it is essentially being stored away, while unpublished items are simply not displayed but still exist within the system.

First, change the merchant account on your campaign to use your previous merchant account. Go to Fundraising, Online Giving, and select Edit for the campaign. Select Choose Financial Options, then choose your previous merchant account.
Next, take action on your form:
If this is a copy of a previous form, unpublish the copy and republish your original form. See Publish a Donation Form.
If this is the original form (not a copy), and the Payment Type data element is included (in addition to the Checkout modal element), your form will process payments as it did before, because the checkout element will be ignored now that the campaign merchant account is reset.
If this is the original form (not a copy), and the Payment Type data element is not included, add the Payment Type element back to your form. See Payment Type Data Element.

No. Currently, reCAPTCHA is required and provided by default for online forms that use the new checkout to collect payments.

No, the modal is a nested iFrame window that is not impacted by browser pop-up blockers.

Yes, you are now able to add all of the standard field selections in the same donation form that uses checkout.

This experience remains as it is today. The only thing that will change is the payment section.

The original (Legacy) Blackbaud Checkout using the S1300 Tag remains without change and will continue to process transactions. We've updated the original version of checkout to be fully compliant with PCI v4 requirements.
Transactions through Legacy Blackbaud Checkout continue as XCheckout and Secure Checkout payment types.

Yes, when your site is configured for MultiLocale and set to use French-Canadian language, supporters will see checkout screens using French-Canadian language.

If you have a development (test) site, you can become familiar with working on some of the setup, but the checkout feature will not load when previewing or testing the form.
You can, however, test your forms on your production site by making a copy of your campaign and forms, then set up checkout on those forms. Preview and publish the copied forms when you are ready, then unpublish the original forms.

Yes, this functionality will be available.

If you need to create a basic donation form so that you can continue taking payments following the compliance deadline and auto-migration script, see the Knowledgebase article, Donation form is not working after switching to checkout. How can I create a simple form and page wrapper to use?