Neon Fundraise offers payment processing primarily with Neon Pay, a payments platform for mission-driven organizations. Please click here to learn more about Neon Pay. Regardless of which processor is configured, processors can be managed in various locations in the Admin, as outlined below. To configure a new processor, please contact us.
How to view all your payment processors
Administrators can view a list of all the processors configured throughout the organization by clicking "Organization" in the top navigation bar in the Admin, and then navigating to the "Processors" tab.
Any processor configured for any campaign in the organization will show in this list, along with an account identifier, the number of campaigns it is configured on, and the total amount raised through that processor.
To view this tab, administrators require Donation Processing Options permissions on the organization level.
How to add a payment processor to a campaign
Payment processors configuration is an inherited setting, meaning they can be applied to an individual campaign, all campaigns in a group, or the entire organization. Click here to learn more about the Admin inheritance system.
Once you have determined to which entity in the Admin to apply a processor configuration, please follow these steps to apply a processor:
1. Navigate to the System > Processors tab within the entity to which to apply the processor.
If the configuration is inherited from a parent entity, you will need to click the lock icon and select "Override parent" before making changes.
2. Click the plus button to bring up the processor library.
Note that processors must already have been configured for the organization. To configure Neon Pay, click here. To configure a different processor, please contact us.
3. Select the processor to apply to the entity and click "Add".
4. On the Processors page, identify what types of transactions you would like to be handled through the processor and toggle those on.
Some notes on processor settings:
- These settings only define what transaction types can be processed through a given processor. For many of these settings (for example, ACH, Apple Pay, Google Pay) there are additional toggles under Forms > Donation Settings that add the relevant buttons to the donation page. Please be sure toggles are enabled in both locations so that front end users can take advantage of these features.
- Once a recurring plan is created, it will continue to be charged through the same processor, even if the "Recurring" setting is disabled later.
- Currencies supported by the processor are displayed in a read-only field at the bottom of the settings list. To add or remove supported currencies, please contact us.
5. To remove a processor from an entity, click the three dots above the processor logo, select "Remove", and confirm.
6. Additional processors can be added to the entity following the above steps.
Multiple processors are listed in priority order, with top priority at the top. To change processor priority, click the three dots above the processor logo, and select "Move Up" or "Move Down" as applicable.
Transaction types will be processed through the highest-priority processor that has that particular type enabled.
For example:
- If Processor A is listed before Processor B, and both have "Recurring" enabled, recurring transactions will be processed through Processor A.
- If only Processor B has recurring transactions enabled, recurring transactions will be processed through Processor B.
- If Processor A has Donations and Recurring Donations enabled, Processor B has Apple Pay enabled, and Processor C has Recurring Donations and Bank Accounts enabled:
- Donations will be processed through Processor A
- Recurring Donations will be processed through Processor A
- Apple Pay transactions will be processed through Processor B
- ACH transactions will be processed through Processor C
Some ways to make use of the multiple processors feature include:
- Organizations can configure their instance to process some transaction types on one processor and others on another. For example, a configuration in which one-time donations are processed through one processor, while recurring donations are processed through another processor. This allows organizations to keep these funds separate as potentially required by applicable business rules.
- Organizations can set up backup processors in the event their primary processor is down. Note that backups are not enabled automatically — this still requires an administrator to manually change the priorities of the processors (or disable the relevant transaction types on the higher processor).