Blackbaud NetCommunity 6.64 New Features – Blackbaud Secure Payment Page Enhancements

Options
We are excited to inform customers about a change that we made to NetCommunity version 6.64.


Changes have been made to the Blackbaud Secure Payment page in NetCommunity. The Event Registration form parts and Payment 2.0 web pages use the secure payment page (PDF) to process transactions. Interruptions can occur when passing information from the NetCommunity page to the secure payment page, either when your website server refreshes while a user attempts to submit a transaction, or when a user leaves the secure payment page up for a time that exceeds the session login. When the user returns to the page and submits the transaction, the session has timed out.


Previously when an interruption occurred the payment processor received the payment and the card was charged, but the information from the web page was not able to be sent to the NetCommunity plugin in The Raiser's Edge. If the user resubmitted their transaction, their card was charged a second time.


Changes were made in 6.64 to have new database processes check the secure payment page for unprocessed data every 24 hours for the period between 12/01/2014 and the current date. If there were any transactions that were not submitted to the NetCommunity plugin in The Raiser's Edge, then these transactions will be pushed into the plugin. It is possible that you may see transactions appear that have already been manually entered, or that were previously thought to be missing.


Still have questions? Take a look at some of the FAQs below:

What if transactions have already been entered into The Raiser's Edge manually, or the transaction data that is showing in the NetCommunity plugin is not needed?


If the transaction was already entered in to The Raiser’s Edge, the transactions can be deleted from the NetCommunity plugin. If not, feel free to process the transaction as normal.

How many times will transactions be pushed to the plugin?


Once the transaction has been pushed to the plugin once, the data will not be pushed again. This includes any transactions that are pushed, and then deleted from the NetCommunity plugin.

Why did Blackbaud make this change?


We made this change to help alleviate any missing transaction from occurring. We noticed that possible timeouts were causing transactions to not show in the NetCommunity plugin.

For more information on this change and other changes in 6.64 of NetCommunity, please refer to our 6.64 new features guide (PDF).

Categories