Brickwork Setup and Support

Learn how to set up and customize Brickwork.

Install all Required Extensions

Part 1: Install all Required Extensions

First and foremost, we need to download all the required packs for connecting Brickwork with your Salesforce environment so that you can accept payments directly from your Salesforce Account.

1.1 Install Brickwork from Salesforce AppExchange

First and foremost, you will to need to install the Brickwork package. Additional packages may also need to be installed depending upon your Salesforce configuration.

 

 

1.2 Install Non-Profit Success Pack from Salesforce AppExchange (Optional)
 


These instructions are written with the assumption that you are a Salesforce Administrator with permission to install packages and knowledge pertaining to editing standard and custom object page layouts and adding Lightning specific elements including deploying My Domain.

Click here to find Brickwork on the Salesforce App Exchange.

Notes for installation process:

  • Be sure to click “Yes, Grant Access to these Third-Party web sites” when prompted. This will allow Brickwork to communicate with the iATS servers.
  • We recommend installing Brickwork for all users, not just Admin users when deploying to Production.

1.3 Install NPSP Recurring Donation or NPSP Payments extension packages from the iATS website.

Here is an overview of what each option is and how you can expect to see your transaction information:

  1. NPSP Recurring Donation Integration (Recommended):

    This option connects Brickwork to the NPSP Recurring Donation object, and its related Donation records. Using an iATS Customer Code, all schedule details are synced between Salesforce and iATS Payments allowing for transactions to be automatically processed on the defined date you or the donor has selected. Brickwork will auto-import all transactions that have been processed and relate them to the correct Donation record. In addition, when the transaction is processed successfully, Brickwork will change the Stage of the Donation from Pledged to Posted (or the closed/won option you define) so your reporting and roll-ups are accurate. If the transaction is declined, Brickwork will change the stage to the closed/lost option you define.


    To utilize the Recurring Donations object with Brickwork and Aura, you must have our NPSP Recurring Donation add-on extension installed. Please click here to download the “Nonprofit Success Pack 'Recurring Donation' extension package” from our website. We include a production and sandbox link.

  2. NPSP Payments Integration: This option connects Brickwork to the NPSP Payment object directly, which allows for multiple Payment records to be created on a single Opportunity record. This is a Brickwork custom option that was developed for those customers who historically didn’t want to use the Recurring Donation object. While it’s still possible to use this option today, we do recommend using Recurring Donations instead. If chosen, all schedule details are synced between Salesforce and iATS Payments allowing for transactions to be automatically processed on the defined date you or the donor has selected. Brickwork will auto-import all transactions that have been processed and relate them to the correct Payment record on the Opportunity. In addition, Brickwork will mark the payment record as “Paid” when the transaction is successful.

    To utilize the Payment object with Brickwork and Aura, you must have our NPSP Payments add-on extension installed. Please click here to download the “Nonprofit Success Pack 'Payments' extension package” from our website. We include a production and sandbox link.
Contact Us