Payments

Payments represent how a constituent paid for a transaction.

Types of Payments

There are two types of payments in Neon CRM: online and offline.

Your app can process payments live through the Neon CRM API by sending card or ACH information to Neon CRM to be processed by the payment gateway linked to the organization’s system. These are known as "online" payments. Processing online payments through Neon CRM's API is legacy functionality restricted to API v1 using a supported third-party gateway. Alternatively, your app can manage payments outside of Neon CRM and pass a record of the payment to Neon CRM with the transaction. These are referred to as "offline" payments.

An online or offline payment must be passed with any transaction that has a non-zero amount.

Tender Types

The required fields for payments vary depending on the type of payment, known as the tender type. There are 9 standard tender types in Neon CRM:

  • Cash
  • Credit Card (Offline-No Charge)
  • Check
  • Credit Card (Online)
  • In-Kind
  • Wire Transfer
  • PayPal
  • E-Check/ACH
  • Other

Users can also create custom tender types.

Neon Pay

Neon Pay is Neon CRM's recommended payment processor. Learn more about Neon Pay in this support guide.

However, external applications cannot process payments through Neon Pay using Neon CRM's API. At this time, only Neon One's internal applications can integrate with Neon Pay.

However, before building custom apps, we recommend exploring Neon CRM's built-in solutions, like embedding Neon CRM forms in an external website, that would enable you to use Neon Pay.

Third-Party Gateways v1 only

Neon CRM supports a variety of third-party gateways, which can be used for online payment processing in API v1. However, third-party gateways are implemented without client-side tokenization, meaning you must handle credit card or ACH information in your app to pass to Neon CRM for processing. This solution is not recommended for integrations that will be used across multiple Neon CRM systems.

PCI Compliance

Processing payments through third-party gateways in the Neon CRM will require your app server to handle card information. Note that the handling of payment data has implications for how your app maintains compliance with PCI requirements for payment processing online. Make sure you review and understand these obligations before proceeding with this solution.

API Reference

API methods related to payments.

API v1

(See transaction methods for documentation on submitting payments with transactions.)

API v2

(See transaction methods for documentation on submitting payments with transactions.)