Payment 2.0
Note: This change was released in Blackbaud Internet Solutions 3.0 patch 55.
This enhancement enables Blackbaud Internet Solutions to transmit data to Blackbaud CRM when users
navigate from your Blackbaud Internet Solutions Payment 2.0 web page to the secure payment page and an
interruption unexpectedly occurs before the transaction is submitted. Previously, when an interruption
occurred, the payment processor received the payment but the information from the Payment 2.0 web page was
not sent to Blackbaud CRM. Also, when the Confirmation page appeared, users were prompted to re-enter
biographical information. This occurred because the data from the Payment 2.0 web page was stored in a
browser session which could not process the transaction to Blackbaud CRM after the interruption.
Tip: An interruption can occur when your Blackbaud Internet Solutions website server refreshes while a user
attempts to submit a transaction. An interruption can also occur when a user leaves your secure payment page
for a time that exceeds the session login and then returns to the page and submits the transaction.
Now data from the transaction is temporarily stored in a new CMS_SessionVariableBackup database table so
Blackbaud Internet Solutions can send the information to Blackbaud CRM regardless of whether an
interruption occurs. Data that is temporarily stored in the table includes the following.
l
l
Biographical data on the Payment 2.0 web page
Merchant account information on the secure payment page. For PCI DSS compliance, this excludes credit
card information.
l
Shopping cart ID
l
Cart item IDs
l
Finder number when you integrate with Blackbaud Direct Marketing
To support this enhancement, a new database process checks the table for data every 24 hours. After Blackbaud
Internet Solutions submits the data to Blackbaud CRM, it no longer exists in the table. The remaining data stays
in the table for 30 days unless your system administrator changes the new
UnprocessedBBSPTransactionLifeSpanInDays web.config setting to increase or decrease the number of days. For
example, to increase the number of days to 60, enter <UnprocessedBBSPTransactionLifeSpanInDays = 60> in the
<appSettings> node of web.config.
Note: The remaining data in the table likely exists because users entered payment information on the secure
payment page, but did not submit the transactions. Your system administrator can access the table to provide
you with a list of these users so you can follow up with them.
Your system administrator can also use the new ArchiveUnprocessedBBSPTransactions web.config setting to
specify whether the process should move the remaining data from the table to a new CMS_
UnprocessedBBSPTransaction archive table in the database, or to delete it permanently. For example, to move
the data to the archive table, enter ArchiveUnprocessedBBSPTransactions=True in the <appSetting> node of
web.config. Otherwise enter False.