Payment & Transaction System Settings
Payment & Transaction Settings
To configure Payment & Transaction Settings, navigate here: System Settings > Home/Dashboard > Payments & Transactions.
In order to process credit cards or eChecks, your organization will need to connect NeonCRM to a gateway that connects to a merchant account.
The Tender Type lists all the payment methods your organization accepts. It will appear as a drop down field when entering a payment. To configure tender types, navigate to: System Settings > Home/Dashboard > Payments & Transactions >Tender Types.
The list of standard tender types come pre-loaded with every NeonCRM. Credit Card (Online) is used to process a credit card transaction through your Credit Card Gateway integration (i.e., BluePay, Authorize.net, PayPal Pro, IATS, or Forte). Credit Card (Offline - No Charge) will NOT process the card, It simply records that the card has already been processed.
There may be standard tender types that you do not accept. Change the status to Inactive for any tender types that you do not use.
The Status controls what standard tender types are available to select when system users enter a transaction from the back end of Neon, as shown in the example below.
For certain standard tender types, the Status also determines what payment options are available to constituents on your Neon forms.
- Activating the E-Check/ACH tender type will add the E-Check Billing Information fields to your Credit Card payment page. Set the E-Check/ACH tender type to Inactive if you do not have an E-Check/ACH Gateway configuration set up to accept this type of online payment.
- If your NeonCRM has been linked to a PayPal Standard account, then activating the PayPal tender type add the PayPal button to the bottom of your credit card payment page.
When you create a custom tender type, it will be available for system users to select when entering a transaction into NeonCRM from the back end.
All custom tender types support the following fields: Amount, Payment Received Date, Payment Note and Status. Below is an example of the payment method page when a system user selects a custom tender type.
Edit Credit Card Type to select from the four major credit cards accepted by your organization. You cannot add new types of credit cards. To activate or deactivate a credit card type, change its status to either Active or Inactive. Click Submit to save your changes.
Navigate to: System Settings > Home/Dashboard > Credit Card Types
*If you activate American Express, make sure your gateway/merchant account is able to accept this credit card type.
Credit Card Swiper
To use a credit card swiper with NeonCRM, you must obtain the following supported devices: MSR90 Card Reader
To enable the swiper, navigate to System Settings > Home/Dashboard > Credit Card Swiper
Check the boxes to enable the card swiper functionality on your front-end or back-end pages.
Enable card swiping on back-end payment forms
Enabling this setting has no impact on NeonCRM except allowing the use of the swiper hardware.
Enable card swiping on front-end payment forms
Enabling this setting allows the use of swiper hardware on your front-end payment forms. This could be useful for setting up payment "kiosks" where constituents can complete transactions on their own.
(Enabling this setting does alter NeonCRM's default behavior. When front-end swiping is enabled, all temporary data is cleared at the conclusion of a transaction. This means multiple people can safely complete transactions from the same computer.)
Manage your list of Solicitors. The detailed guide is found here.
To configure this list, navigate to: System Settings > Home/Dashboard > Solicitors
Solicitation Methods are the broadest way that you solicited a gift, such as a mailing, phone call, or email. To configure this list, navigate to: System Settings > Home/Dashboard > Solicitation Methods.
To add a method, simply click Add and then Submit. Delete will delete a source, and the Status dropdown indicates if this method is active or not.
Campaigns are the most common way of categorizing donations. Typically, a Campaign is used to track how donations came to your organization, such as a special fundraising event, annual appeal, or year-end fundraising drive. Campaigns can also have their own specialized online donation form.
Campaigns can be organized with a tiered structure, which means you can designate a parent campaign and then assign various child campaigns to that parent group.
A list of all your campaigns can be found under Fundraising tab > Campaigns, or it can also be accessed in System Settings > Home/Dashboard > Campaigns.
Funds are larger efforts than Campaigns or Purposes. You could have three or four campaigns that all contribute to your general operations fund.
To set up Funds, navigate to: System Settings > Home/Dashboard > Funds.
You will need to specify the name, code, start date, and status in order to set up a Fund.
When you mark a Fund as the default, you are given an additional option to Apply to front end (online) donations.
Purposes are a way to flag donations to be used for specific purposes. For example, people who donate to the Red Cross can say they want their donation used specifically for disaster relief. Similar to the Campaign field, Purpose can be a multi-leveled hierarchy as well and you would set up this in the same manner as the campaigns.
To configure Purposes, navigate to: System Settings > Home/Dashboard > Purposes
Name is the a required field. Defining a Super Purpose makes this particular purpose a Sub-Purpose of whichever one you choose. This means transactions that are attributed to this purpose will also be attributed to the Super Purpose.
When you mark a Purpose as the default, you are given an additional option to Apply to front end (online) donations.
You may add a processing fee that is added to Donations, Store Purchases, Membership fees, and Event Registration Fees. If you enable this fee, your constituents will pay this fee in addition to their regular amount. You would enable this fee when you want to add a fee to your transactions so that constituents bear the cost of your transaction fees. You must specify the processing fee for each type of transaction.
This does not give the constituents the choice of covering the processing fee. If enabled, they will be required to pay this fee.
To configure this fee, navigate to:
System Settings > Home/Dashboard > Credit Card Transaction Fees
Click Edit next to the transaction type for which you want to configure transaction fees. Your fees can be a flat-rate amount, or they can be a percentage of the purchase price. Select the type and the fee, and add a label. This label will display on front-end web forms. The label informs constituents of what the fee is. Click Save when finished.