There were changes made to the Blackbaud Secure Payment page in NetCommunity in version 6.64. 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. An interruption can occur 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 and the user then returns to the page and submits the transaction; basically causing the secure payment page to time 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 sent to the NetCommunity plugin in The Raiser's Edge. Also,when users were filling out the event registration form, users were taken back to the first step of the form. 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. The process checks for any unprocessed data 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.

If transactions have already been entered into The Raiser's Edge manually, or the transaction data is not needed, then the transactions can be deleted from the NetCommunity plugin. Once the transaction has been pushed to the plugin once, the data will not be pushed again.

We made this change to help alleviate any missing transaction issues. If you see that you are missing transactions, please allow up to 24 hours for this process to run to see if the transactions get pushed to the 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).