Checkout FAQ

Tip: Register for a Checkout for Luminate Online workshop for a live walk through of these changes.

The new checkout experience is a combination of new merchant account settings and new form data elements that together provide a dynamic, secure, and PCI v4-compliant payment transaction for your donation forms. These updates require a Blackbaud Payment Services account to process and disburse credit and debit card payments.

In addition to credit and debit card, direct debit, and offline payments, the new experience also includes Apple Pay, Google Pay, PayPal, and Venmo digital wallets. We continue to support sustaining (recurring) payments, designated giving, giving levels, tributes, and premium fraud management.

You can use your current Blackbaud Payment Services and Blackbaud Merchant Services accounts. If you need to create accounts, see Getting Started with Blackbaud Merchant Services. Whether you are using new or existing accounts, you need to configure Payment Capabilities in Luminate Online.

Checkout is offered in two versions, modal and embedded. Checkout modal is an iFrame window that surfaces when the supporter is ready to make a payment. Checkout embedded is integrated into your form design.

Warning: Luminate Online will no longer support direct credit and debit card payment processing through Payflow Pro, iATS, and CyberSource payment gateways after January 31, 2025. See End of Support date for directly-connected payment gateways through Luminate Online.

The Checkout modal element is available now. The Checkout embedded element is available late November 2024.

Designing and implementing new options and improvements will continue even after March 2025.

Note: All active forms must use the new checkout experience for transactions when the new PCI v4 standards take effect in March 2025.

• Centrally Managed Payment Methods: Every payment type you accept is available under one merchant account. A single account for direct debit, credit and debit cards, and digital wallets makes management easy and efficient.

• Centrally Managed Payment Processing: End-to-end donation flow from checkout to disbursement is available when using Blackbaud Merchant Services merchant accounts with the new checkout experience.

• More Payment Options: Checkout supports a wide range of payment methods, including Apple Pay, Google Pay, PayPal, Venmo, direct debit, and credit and debit cards.

  Note: Initially, checkout will support single transactions with PayPal, with support for recurring PayPal transactions coming soon. Currently, Venmo only supports USD and single transaction processing.

  Note: The Checkout modal in the 24.4 release does not include options for donors to select check or cash payments, but this is coming in the 24.5 release.

• Improved Form Design: Forms are responsive and mobile-first. Get a modern and intuitive interface with either the embedded or modal checkout data element.

• No Downtime: Collect more with zero downtime.

• Optimized Payment Capture: More payment methods equal more choice, which translates to higher conversion rates raising your revenue. Blackbaud continually runs A/B tests to improve these conversion rates and optimize the donor experience.

• Reduced Processing Fees: Donor Cover and Complete Cover are coming soon to the new checkout experience!

• Secure By Design: Checkout adheres to the highest standards of payment security, being fully PCI-compliant. This ensures that all payment transactions processed meet rigorous security protocols, including encryption, tokenization, and secure data handling practices, and premium fraud management.

Yes! Checkout supports Apple Pay and Google Pay for single and recurring transactions. Initially, checkout will support single transactions with PayPal, with support for recurring PayPal transactions coming soon. Currently, Venmo only supports USD and single transaction processing.

Tip: To accept PayPal and Venmo transactions, link your PayPal business account to your Blackbaud Merchant Services account. See How to set up PayPal (and Venmo) with Blackbaud Merchant Services.

Note: The new requirements only apply to forms that are published and actively accepting transactions. Start with forms that will be active from March to June 2025. This may decrease the forms you need to address.

Reviewing and updating your forms is a big job, but it doesn't have to be overwhelming. Use the project guide below start making a plan that works for you. We recommend the following approach.

1. Identify your needs. Make a list or calendar of campaigns, events, and communications you know you are expecting from March through June 2025. What donation forms do you need for those? These are the priority.

2. Identify forms to prioritize those that require action. Use the Donations by Form report to identify forms that apply to the March through June 2025 priorities. Unpublish or archive unneeded forms.

   Tip: New eLearning, Auditing Active Donation Forms, is now available.

3. If you do not have Blackbaud Merchant Services and Blackbaud Payment Services accounts, create them. See Get Started with Blackbaud Merchant Services.

   Tip: New eLearning, Understanding Secure Payment Processing / Blackbaud Luminate Online, is now available.

4. Complete the steps in Update your Checkout Experience.

   Tip: Add a new checkout data element without removing the existing Payment Type data element. When both data elements are present and the selected merchant account supports the new checkout, only the Checkout element is used. Having the Payment Type data element present allows you to roll back changes more easily if you decide you are not ready for the switch.

5. If you have API forms, update your corresponding shadow form and adjust your code to call the new checkout API methods. See the Checkout overview in the API docs for more details.

1. Select Fundraising and Donation Management.

2. Select Donation Report and Create a new report.

3. Select Donations by Form and Go. By default, all forms are selected.

4. When you are returned to the Donation Reports list, the new report’s status is Queued.

5. Select Refresh Report List to update the status. When the status is Completed, select Download under Actions. This provides you with a csv file of the report to track your audit and action items.

Tip: You can also use the report to identify API forms. If you have API forms you must update your corresponding shadow form and adjust your code to call the new checkout API methods. More details are coming soon to the API documentation.

Each donation form belongs to a campaign, and each campaign is associated with a Luminate Onlinemerchant account. To change the merchant account on a donation form:

1. Select Fundraising and Donation Management.

2. Edit a campaign on the list.

3. Open Choose Financial Options and select a merchant account

4. Save your changes.

TeamRaisers are associated with a donation form, and the donation form is associated with a donation campaign. That donation campaign is assigned a merchant account. To change the merchant account on a TeamRaiser, change the merchant account on the associated donation campaign.

To change the donation form associated with a TeamRaiser:

1. Select Fundraising and TeamRaiser.

2. Edit a TeamRaiser on the list.

3. Open Select Fundraising Options and select a Donation Form.

4. Save your changes.

1. Select Fundraising, Donation Management, and All Donation Forms.

2. Edit a donation form on the list.

3. Select Design Donor Screens and Edit the Donation Form screen.

4. Select Checkout modal under Select data elements to include in this form and select Add. Do not remove the Payment Type element.

5. Position the data element where you want it in the form by selecting the element name and using the Order arrows.

6. Select Save Order and Edit Selected.

7. Select your checkout configurations and Preview or Save your changes.

   

If you have a non-custom secure domain, either secure2.convio.net, secure3.convio.net or secure8.convio.net, you do not need to take action. Once your forms are set up with checkout, Apple Pay automatically displays as an option on compatible Apple devices.

If you have a custom secure domain, complete the one-time verification process. You must complete this process even if you previously set up Apple Pay to work in legacy Blackbaud Checkout, as the verification file contents have changed.

1. Using FTP access, place the Apple Pay verification file (new checkout version) at the following path on your website: [DOMAIN]/.well-known/apple-developer-merchantid-domain-association.

   Note: If this is your first time setting up Apple Pay, create the .well-known folder at the root level of your site. Folders that begin with a period (.) are hidden by default — if you don't see yours, check your FTP application's instructions for steps to view hidden folders.

2. From the Blackbaud Merchant Services Web Portal, under Settings, Payment Domains, add and verify your domain.

3. Repeat for each domain and subdomain where Apple Pay should appear.

   Note: Apple Pay displays 24 to 48 hours after a form processes its first payment, so if this is a new form, complete a credit card payment through the form, then wait 24 to 48 hours to check your form from a compatible Apple device to confirm that Apple Pay appears during checkout.

For more information, see Payment Domains.

To accept PayPal and Venmo through your forms, connect your PayPal Business and Blackbaud Merchant Services accounts in the Blackbaud Merchant Services Portal. See Get Started with PayPal in the Blackbaud Merchant Services Help.

Note: PayPal is not yet available for recurring payments.

Yes, all live donation forms need to be updated by February 2025. First, prioritize your live donation forms, then update lower priority forms.

No. When a campaign is updated to use the new checkout, all forms associated with that campaign must also use the new checkout. Add either the Checkout modal or Checkout embedded element to the form.

Yes, you can use your existing Blackbaud Merchant Services Account. You will, however, need to create a new payment configuration in Luminate Online.

If you are new to Blackbaud Merchant Services, see our step-by-step guide for setting up Payment Capabilities.

No. Payment Card Industry requirements do not apply to ACH.

If you currently process ACH transactions with a direct payment gateway such as iATS or Payflow Pro, you can continue to do so. However, all credit and debit card transactions will require the new checkout via Blackbaud Merchant Services with native direct debit support.

You cannot have the new checkout experience and your legacy checkout experience on the same form. Going forward any form that allows credit and debit card payments will not support third party gateways such as iATS or PayflowPro.

Tip: We recommend that you migrate your direct debit recurring gifts from your current direct payment gateway to Blackbaud Merchant Services to consolidate your payment processing vendors, reconciliation, reporting, and admin processes. Processing all your transactions through your Blackbaud Merchant Services account allows you to take advantage of all the new payment features and capabilities. This is a single, end-to-end solution for credit and debit card, direct debit, and digital wallet transactions.

Warning: If you do not migrate your existing direct debit recurring gifts to Blackbaud Merchant Services, you will have to maintain two workflows. The first for all existing direct debits to be run with your direct connect payment gateway, and the second for all new direct debit transactions that will be processed with your Blackbaud Merchant Services account.

No. Changing forms to inactive/archived does not impact your scheduled recurring transaction processing.

Once a form processes a payment, the donation data is tokenised 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.

Yes, they will continue to work if they were processed on Blackbaud Merchant Services.

Yes, you can choose payment methods to offer on your donation form, including digital wallets, credit card, and direct debit options.

PayPal requires specific action, so unless you complete the configuration, it will not display. To accept PayPal and Venmo through your forms, connect your PayPal Business and Blackbaud Merchant Services accounts in the Blackbaud Merchant Services Portal. See Get Started with PayPal in the Blackbaud Merchant Services Help.

Note: PayPal is not yet available for recurring payments.

• Credit cards support both single and recurring payments.

• Direct debit supports both single and recurring payments.

• Apple Pay and Google Pay support both single and recurring payments.

• PayPal currently supports single transactions. Support for recurring PayPal transactions is coming soon.

• Venmo currently supports only USD and single transaction processing.

Coming in 2025 to Luminate Online forms, Complete Cover/Blackbaud pays is when Blackbaud covers the fees for the form and donors have the option of giving an additional amount to Blackbaud to help support organization's that use Blackbaud Merchant Services for processing.

With this option, even if a donor decides not to contribute extra, processing is always free to your organization. See the Knowledgebase article, What is the difference between Complete Cover/Blackbaud pays, Donor Cover, and My organization pays?

Some payment methods, such as Apple Pay or Google Pay, require specific browsers. See the Supported browsers section in Digital Wallets.

Supporters can pay with Apple Pay for one-time and recurring gifts when using a compatible Apple device with the latest version of iOS or iPadOS support, watchOS, or macOS supported versions.

Currently, PayPal and Venmo are not available for recurring gifts. If you use a merchant account with a PayPal and Venmo configuration on a form that has recurring payments enabled, the PayPal and Venmo payment options are hidden.

Note: TeamRaiser Delayed Self Pledges process as recurring gifts. Therefore, PayPal and Venmo are hidden on TeamRaiser forms allowing Delayed Self Pledge.

Support for PayPal recurring gifts is coming soon.

Yes, your ApplePpay experience will be the same.

Apple Pay and Google Pay are only included when Digital Wallets are enabled. Apple Pay and Google Pay process at the same rate as credit cards in Blackbaud Merchant Services.

See Blackbaud Merchant Services Processing Fees.

Our first release of the new checkout includes donation forms and online TeamRaiser registration forms using the modal checkout feature.

In our upcoming releases, we will release an inline checkout feature, and all applications that process transactions will use the new checkout options, including:

• Offline Participant Center and TeamRaiser gifts

• eCommerce

• Personal Fundraising

• Ticketed Events

• Gift Service Center

• Event Management Center

• Donations Classic

• Embed a Donate Button

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

Yes, you need to update any donation forms that still processes recurring gifts, even if it is in an Unpublished status. Add either the Checkout modal or Checkout embedded data element to the form.

After the update, donation forms will continue to process recurring monthly gifts tied to those donation forms after March 2025.

Archived donation forms can continue to process recurring (sustaining) monthly gifts tied to those donation forms, but you must update any donation form that still processes recurring gifts, even if it is in an Archivedstatus. Add either the Checkout modal or Checkout embedded data element to the form.

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.

At this time, the original (Legacy) Blackbaud Checkout using the S1300 Tag remains without change and will continue to process transactions. We have 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 site on the Cluster 8 environment, you can become familiar with working on some of the setup steps, but the checkout feature will not load when previewing or testing the form. This is due to a security measure in the environment.

To test your forms on your production site, you can make a copy of your campaign and forms, then set up checkout on those forms. Publish the copied forms when you are ready, and unpublish the original forms.

Yes, this functionality will be available.

Yes, the Checkout modal allows you to select a primary color to match your branding.

The Checkout embedded data element allows you to select a primary color, font color, and font family.

Tip: Style customization is available in the data element configuration. You can also apply custom-built payment solutions such as DAF Pay or other customizations, such as recurring gift upsells, before or after the new payment section in your form.

The Style field in the Checkout data element allows you to enter a primary color in the checkout modal.

1. Select Fundraising, Donation Management, and All Donation Forms.

2. Edit a donation form on the list.

3. Select Design Donor Screens and Edit the Donation Form screen.

4. On the left, under Arrange the order of the selected data elements, select either Checkout modal or Checkout embedded.

5. Select Save Order and Edit Selected.

6. Enter the color in the Style field, and Preview or Save your changes.

   Checkout modal:

   

   Checkout embedded:

   

Due to the changes for PCI v4 requirements, we can no longer allow custom code in the payments section of a donation form. This means that you must place your custom DAF Pay button in a location outside of the payments section of your donation form.

For example, you can apply the DAF Pay button directly above the forms "Payment Information" section, or place it next to the gift amount button selection.

By March 2025, your TeamRaiser event must use a donation form that is associated with a campaign configured with the new checkout.

1. Go to Fundraising, TeamRaiser and Edit.

2. On the left, select Edit Fundraising Options.

3. Choose a donation form. The form must be associated with a campaign that is set up to use checkout.

4. Save the update.

Note: Support for inline checkout for TeamRaiser registrations is coming in a future release.

For more help, see Fundraising Options for TeamRaiser Events.

If you currently use APIs for your forms, then by March 2025, you must update certain methods to use new APIs that pass tokens to meet PCI v4 standards.

Replace donate, addGift, and offlineOrganizationGift, and add additional validation methods. See the Luminate Online API Changelog for full details of these changes.

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

NOTICE: Before March 2025, update the following API methods in your forms. Again, both APIs will run concurrently until March 2025 at which time the previous method will be deprecated.

The following new methods use transaction tokens to handle payment information. These methods are only compatible with transactions in the new checkout.

donateCheckout - Similar to donate , this method meets PCI v4 requirements for credit and debit card transactions. See donateCheckout.

offlineOrganizationGiftCheckout - Similar to offlineOrganizationGift, this method meets PCI v4 requirements for credit and debit card transactions. See offlineOrganizationGiftCheckout.

addGiftCheckout - Similar to the addGift API, this method meets PCI v4 requirements for credit card and debit card transactions. See addGiftCheckout.

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

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

The following new methods verify your form.

• validateDonateCheckout validates whether the payload passing in donateCheckout is valid or not.

• validateProcessRegistrationvalidates whether the payload passing in processRegistration is valid or not.

• validateAddGiftCheckout validates whether the payload passing in AddGiftCheckout is valid or not.

• validateOfflineOrganizationGiftCheckout validates whether the payload passing in OfflineOrganizationGiftCheckout is valid or not.

Updated API methods

• Both processRegistration and refundTransaction were not replaced so as to minimize impact. However, changes were made to their logic and behavior. The new behavior reviews whether a transaction token is passed in the payload instead of card credentials.

  Until March 2025, if the transaction token is not passed in the payload, then these APIs revert to reviewing the card credentials passed within the payload and behave as the APIs do today.

  After March 2025, the APIs will only operate using transaction token data.

  The APIs were also updated to handle any transaction type supported in Luminate Online, including checkout transactions.

• In a future release, ProcessRegistration will handle PayPal payment methods (and other payment methods), so processRegistrationPaypal will no longer be needed.

• getTeamRaiserConfig no longer returns a transaction token or payment information.

See our Overview of Checkout API for information on the Luminate API updates.

See our Integration Guide for steps to connect Luminate Online forms with Blackbaud Merchant Services.

Note: startDonationis unchanged.

Transactions in the new checkout show as Credit Card, Direct Debit, or as "XCheckout" if you are using an external payment processor such as PayPal.