Cedarville’s now annual tradition of a one-day, twenty-four hour giving day blitz fell on April 20 in 2016. While we were able to re-use a number of website front-end design patterns from the 2015 site, several back-end modifications were needed due to system changes and new requirements from the advancement staff.
The first major change was in our credit card handling. Due to PCI compliance requirements, the university is on a completely different system for handling credit cards from a year ago. We no longer host credit card form fields and therefore no longer funnel the credit card processing on our site through back-end systems for processing. The fields are all hosted off-campus through a series of iframes. Until this point, we had directed users to a standard payment screen for all website transactions that required credit card input. For this one-day giving site, one of the requirements was to streamline the user flow and maintain the giving day user interface as much as possible. After overcoming several challenges, we were able to have the iframe fields hosted in the giving day UI to create the desired seamless experience.
The second major change was the integration of Google Sheets into the back-end process. For a giving blitz like this, it’s helpful to have a subset of the data go into a spreadsheet that can be concurrently edited and collaborated on by several offices. The helps keep everyone in multiple offices spread across campus on the same page regarding where the university is in the giving matches and challenges presented throughout the day. It also helps expedite receipting and thank you notes written by volunteers throughout the day. Once the gift was processed and added to our standard donation database, a row was added using Google’s C# APIs to a particular Google Sheet shared by the giving day team. The Google Sheet document had two additional worksheets–one for manual entry of gifts not processed by the online form and one for summarizing the data from the first two worksheets. The summary data worksheet also was used to determine what total dollar amount was shown on the website–the website would periodically fetch the data from the sheet for display.
Because of time constraints, we were unable to fully test the entire system for edge case scenarios, causing a few hiccups when the giving site went live on the giving day (sound familiar Martian movie?). First, Internet Explorer (all versions, of course) had issues with the iframe-within-an-iframe that caused the credit card fields to either not show or not be clickable/navigable. Some rearrangement of our jQuery reference fixed that issue (moved from pointing to our on-campus .js file to the CDN version). Second, for about 45 minutes that morning, Google had some crazy thing going on with their API calls, causing them to intermittently fail to add rows to our Google Sheet with the following error – Google.Apis.Auth.OAuth2.Responses.TokenResponseException: Error:”internal_failure”. At first we thought the errors were caused by our site hitting some API rate limits or something like that, but after 45 minutes, the issue just disappeared. Thanks Google. Thankfully our error handling captured enough data to recreate the rows by hand. Disaster averted.
This was a challenging project, especially given a short time constraint and the rush to fix the two issues during the giving rush in the morning. But it was rewarding as well to see it all come together and work well (besides the few hiccups I mentioned). The integration of Google Sheets as a secondary target of information from the giving form provided a streamlined workflow for processing the steady stream of incoming donations and thereby proved extremely helpful to the team of users running the giving day.