Skip to main content

Deactivate a Transaction Processor

Bloomerang CRM

Updated this week

You can deactivate a transaction processor that you no longer use.

After you deactivate a transaction processor, you can't use that processor to process transactions. You also can't add that processor to forms.

Before You Begin

  • Verify that you have another transaction processor set up in Bloomerang CRM.
    If you have only one transaction processor, you must first add an additional transaction processor before you can deactivate the other processor.

  • If you have online forms, note which transaction processor you use for each form. If your forms use the transaction processor that you plan to delete, you must update each form to use a different processor.

Step 1 — Deactivate a Processor

You can deactivate:

  • Third-party processors

  • Bloomerang Payments

Warning: After you deactivate a transaction processor, forms and autoprocessing payments do not automatically update. You must manually update existing forms and autoprocessing payments currently assigned to that processor.

Deactivate Third-Party Processors

To deactivate a third-party processor:

  1. Click Payments.

  2. Click Payments Home.

  3. On the Payments Settings tab, in the Other Processors section, click the drop down arrow beside the processor.

  4. Select Edit.

    List of third-party processors
  5. Clear the Active checkbox.

    Active checkbox that is cleared
  6. Click Save.

  7. If asked to confirm, click Deactivate.

Deactivate Bloomerang Payments

Important: If you’re a new Bloomerang customer located in the United States, and your Bloomerang CRM database was created on or after February 10, 2026, or if the Disconnect Bloomerang Payments option doesn't appear, you can’t disable Bloomerang Payments.

If you use the Kindful Fundraising add-on, you must first deactivate it before you can deactivate Bloomerang Payments. Please email [email protected] to deactivate your Kindful Fundraising add-on.

To deactivate Bloomerang Payments:

  1. Click Payments.

  2. Click Payments Home.

  3. In the Bloomerang Payments section, click Settings.

  4. Click Disconnect Bloomerang Payments.

    Disconnect Bloomerang Payments link

Step 2 — Update the Processor for Forms

After you deactivate a processor, you must edit your forms to use the new processor.

Step 3 — Update the Processor for Autoprocessing Payments

After you deactivate a processor, you must run a report to find pledges, recurring donations, and memberships that use the inactive processor to autoprocess payments.

To run this report:

  1. In the Include section, click Add Filter.

  2. Search for and select Type, then select Pledge and Recurring Donation Schedule, then click OK.

    Transaction type filters

  3. Click And, then search for and select Processor. Select the inactive processor, then click OK.

    Processor Is filter
  4. Click And, then search for and select Matches Multiple Filters.

    1. In the Include section, click Add Filter. Search for and select Pledges and Pledge Payments.

    2. In the Include section, click Add Filter, then search for and select Pledge Status. Select In Good Standing, and In Arrears, then click OK.

      Pledge status filters
    3. Click OK again.

    4. Click Or, then search for and select Recurring Donation Schedules and Payments.

    5. In the Include section, click Add Filter, then search for and select Schedule Status. Select Active, and Overdue, then click OK.

      Schedule status filters
    6. In the Include section, click Add Filter, then search for and select Membership Schedules and Payments. Select Active, and Overdue, then click OK.

      Report filters for memberships
    7. Click OK until you are back to the main set of filters. The report results appear.

Next, update the processor for each transaction listed in the report:

  1. From the report results, click a transaction to go to and edit the pledge, recurring donation schedule, or membership schedule.

  2. Change the processor to your current processor.

Related

Did this answer your question?