Transactions represent constituents’ contributions to an organization. These transactions can be either monetary or in kind. All transactions have an amount that is always positive. Some types of transactions can have $0 amounts to represent a fully discounted item, such as a free admission event ticket, or a gift that is in kind. All transactions are linked to constituent accounts, and finally, transactions are the only source of financial data in Neon CRM.

Neon CRM is a revenue focused system and cannot be used for many general accounting purposes, such as tracking expenses or outgoing funds. As a CRM, the focus of transaction data in Neon CRM is the constituent accounts to which transactions are attached. The creation of generic account records to act as a catch-all for general funds is therefore not recommended for any integrated app.

There are four transaction types in Neon CRM:

  1. Donations
  2. Event Registrations
  3. Memberships
  4. Store Purchases

Transaction types are generally separated by their purpose, as outlined below. Each transaction type has its own unique properties and associated data types, although transaction types also share common functionality and data patterns, such as for payments.


Donations represent general purpose contributions and are the most common transaction type in Neon CRM. Donations are not associated with the exchange of goods and services and do not have fields for tracking the tax deductibility, and so, they are generally considered 100% tax deductible.

All donations must include the following data:

  • Linked account
  • Donation date
  • Donation amount

Campaigns, Funds, and Purposes

There are 3 primary allocations for categorizing donations in Neon CRM:

  • Campaigns
  • Funds
  • Purposes

Campaigns are generally the most important allocation for donations in Neon CRM and are the basis for most donation segmentation and reporting. Campaigns are typically donor-facing and have public campaign pages and donation forms associated with them. Finally, campaigns can have a multi-leveled hierarchy, allowing several campaigns to be nested under a common parent campaign.

Funds are larger efforts than campaigns or purposes. They are often used as an accounting allocation. The most common examples of funds are Restricted, Unrestricted, and Endowment (if applicable). You can have three or four campaigns that all contribute to an unrestricted fund.

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 campaigns, purposes can have a multi-leveled hierarchy as well.


Pledges represent a commitment to a gift that is typically fulfilled over multiple payments. In fundraising, pledges often have strict implications for revenue recognition and tax purposes. However, not all organizations will use pledges in Neon CRM in this way.

In Neon CRM, pledges and pledge payments are a special type of donation that share many of the same properties and relationships. In fact, pledges, pledge payments, and donations all share a common table in Neon CRM's database structure, which means your app can assume all three types share the same data models except where specified.


Event registrations allow constituents to register for events that are configured in Neon CRM. There are three primary objects that are exposed in the Neon CRM API:

  1. Events
  2. Event Registrations
  3. Event Attendees

The event represents the event itself, including the event date/time, location, ticket pricing and restrictions, and statistics about the event.

The event registration is the purchase of an event ticket or admission to an event. A registration is linked to a single account—the registrant—and has a payment object representing how the registrant paid for the registration.

Event attendees represent the individuals who will be attending the event. While only one registrant can be linked to a registration, a registration can have many linked attendees. Attendees can be accounts or just names listed as part of the registration.


Memberships track the collection of dues from members of an organization and contain start and end dates for determining a member's status with the organization.

Memberships may have $0 dues, allowing memberships to be used more generally for tracking an account's status with an organization over a defined period of time.

Levels & Terms

Memberships are sorted into different levels, representing the different types of memberships at an organization.

Each level can have one or many terms, representing the different costs and periods of time for which a membership level can be purchased. Membership terms are always paired with one membership term designated for first-time joining members and the other designated for renewing members.

A membership transaction must be linked to a membership level and term and will inherit the membership name, cost, term dates, and other fields, although some of these values can be overwritten on a transaction-by-transaction basis.

Store Purchases & Shopping Carts

The store is Neon CRM's ecommerce module and allows organizations to sell physical and virtual products that include shipping and tax.

The store API is also capable of purchasing store products, donations, and memberships together in a shopping cart. Please note though that it is not necessary to use the store to purchase donations and memberships, as there are dedicated API methods for purchasing those individually. You may wish to use the store for these if you want to allow constituents to purchase multiple items at the same time.

API Reference

API methods related to transactions.

API v2


Pledges & Pledge Payments

Recurring Donations

Fundraising Campaigns

Event Registrations



Store Orders