This section is for understanding how to use the Payment (be sure to use the Payment with the API name of npe01_OppPayment_c) and related objects. Payment is an NPSP package object and works with Opportunity, GAU Allocation and General Accounting Unit (Fund) to track giving from donors.

The Non-cash Payment record type will also help your organization track other types of gifts such as stock/securities or other traded items. If your organization has a Tiingo account, if the API is configured, then when specific fields are populated, the high/low prices are returned to the Payment record without further user intervention.

• Custom Fields
• Record Types
• Action
• Flow
• Apex
• Creating Payments

Fields included with the Payment object include picklist, lookup, formula, date and text fields. Work with your teams to determine how your org uses this object. Make sure the fields are included on the Payment Page Layout and Lightning Page.

• Average Share Price
• Call the Tiingo API for this Security
• Credit Card Fee
• Gift Value
• High Share Price
• Low Share Price
• Number of Shares
• Number of Shares Sold
• Security Description
• Ticker Symbol
• Total Amount Sold
• Total Broker Fees Amount
• Total Gain (Loss) Amount
• Total Proceeds Amount
• Unique Ext Sys Id

Two record types are included with the Donor 360 package. This allows for different pages and fields to be visible for different types of payments. Cash Payment is for cash, checks, and other forms of payment where the money is considered Cash. Non-cash Payment is for other types of gifts which could include In-Kind, Real Estate, Stocks/Securities, etc.

• Cash Payment
• Non-Cash Payment

One Action is included in the package and it's used to launch a flow to add Security Settlement information and create the record. See the Security Settlement page for more details.

• CreateSecuritySettlement

• fdnp Tiingo Stock Api

• fdnp_cf1_TiingoApiController

Payments is a child record of the opportunity and track Scheduled Date, Payment Date, Payment Amount, Credit Card Fees, Payment Method, Check/Reference Numbers, credit card processing information and security information. The Payment record tracks when and how much was received by the organization and based on field values will create a Cash Payment or Non-Cash Payment record.

The flow used to create Opportunities also creates these Payment records and walks the user through generating the appropriate records connected to the Opportunity. The example below is a Cash Payment record shown first in the flow and then in the saved Cash Payment record.

A Non-Cash Payment record will look something like the screen shot below. First in the flow, then in the Non-Cash Payment record. With a valid Tiingo account and API setup in Salesforce, check the Call the Tiingo API for this Security box when entering the gift, make sure the Ticker Symbol field is populated and the Payment Date is populated and the security high/low information will be pulled into Salesforce from Tiingo.

For more details on entering Security Settlement information, see the Security Settlement page.