Brickwork Setup and Support

A Customer Code/token’s payment information (ex. field values: Credit Card Number, Credit Card Expiry Date, etc.) can now be copied to a new Customer Code/token.  Therefore, allowing you to create a new recurring payment schedule for the same saved payment information.  

For example, if an existing donor wants to set up a new recurring donation with your organization (with a new recurring schedule) but wants to use their existing payment information, you can easily create the recurring payments in Brickwork WITHOUT requiring the payment details again.  

Use case example: A donor requests a monthly recurring donation of $10. Therefore, you create a Recurring Donation record and then set up recurring payments via the iATS Virtual Terminal which creates a Customer Code/token to store the data. At a later point the donor requests an additional annual recurring donation of $20. Previously you needed to re-obtain the payment information in this case from the donor but you can now simply clone the payment information from the previous Recurring Payment’s Customer Code/token.  

What’s New? 

The Recurring Donation object virtual terminal has been updated with a new dropdown field labeled ‘Use Saved Payment information’ which allows you to select previous Customer Code payment information to clone. The field only appears if there is an existing Customer Code for the donor. If a previous payment information option is selected (Ex: Credit Card ending in 4232), then a new Customer Code is created with that payment information.  

Please note: This feature is only available for North American clients now and is NOT available in the UK and Euro. 

 
FAQS

Will this change effect any of my existing Brickwork or Salesforce setup? 

No 

Are the parent customer code and child customer code connected after the cloning has been completed? 

No. After the parent customer code is successfully cloned and a new child customer code is created, both are no longer connected. Which means any changes made to the parent customer code will not affect the child customer code and vice versa. 

How can we find out if a specific customer code is parent or child? 

This can be checked via the iATS legacy portal report only.