Donation Pages

Some of the things you can change are the heading or description of these pages, add or remove cards, and adjust the information shown on some cards. Learn more about how you can customize these pages to provide an engaging giving experience.

Configure the Donation Entity

The Donate page in Community Hub displays donation products for all entities set up in your org. When constituents click on a donation, they are taken to the Donate Now page.

For the Donate Now page, you can configure whether submitted orders are created based on the donation product's entity or based on a primary entity.

Use the Donation Product's Entity

We recommend this approach if you are not using stored payment methods or Entity Crossovers. This allows constituent to make donation orders which are processed and paid for using the payment gateway for the entity on the donation product.

That you can customize the DataSource for the pages so that you can exclude Donation Products from specific entities from the main Donate page. As a best practice, that this should be done for PAC entities so that the rules and regulations of PAC Donations are respected.

For example, you can create a query similar to this, which will need to be set to System (rather than User):

By default, the order is created with the entity set on the donation product and payment is made using the payment gateway for that entity. Also, the Donate Now page displays constituents stored payment methods for the entity set on the donation product.

As an example: April Black creates a stored payment for the ISEN entity. When April browses to the Donate Now page to make a donation to ISEN Research, her stored payment method displays and when she submits the donation, the order is marked with ISEN and the payment processes using the ISEN payment gateway.

When April browses to the Donate Now page to make a donation for the Education Foundation—which is through the Nimble Foundation entity—her stored payment method does not display because she has no stored payments for the Nimble Foundation and the order is marked with Nimble Foundation and the payment processes using the Nimble Foundation payment gateway, which is the entity set on the donation product.

Use a Primary Entity

We recommend this approach if your association has donation products for two or more entities and uses Entity Crossovers to ensure payments are accounted for properly. This allows constituents to view and use their stored payments created for the primary entity to make donations, regardless of entity on the donation product.

Alternatively, administrators can set the primary entity the Donate Now page uses when creating an order, submitting payment, and displaying stored payment methods.

As an example: An administrator sets ISEN as the primary entity for a Community Hub and April Black creates a stored payment for the ISEN entity. When April browses to the Donate Now page to make a donation to ISEN Research, her stored payment method displays and when she submits the donation, the order is marked with ISEN and the payment processes using the ISEN payment gateway.

When April browses to the Donate Now page to make a donation for the Education Foundation—which is through the Nimble Foundation entity—her stored payment method for ISEN displays and the order is marked with ISEN and the payment processes using the ISEN payment gateway.

In Donation Primary Entity Id, enter the Salesforce ID for the entity the Donate Now page uses when creating an order and submitting payment. Additionally, only stored payment methods for the given entity are displayed on the Donate Now page.