Authorized transactions are removed from batch when the credit card process is run a second time

When a user processes a Batch of authorized Credit Card transactions a second time, the process will overwrite the existing Authorization Codes and Permanently Reject the transactions. These Permanent Rejections are then removed from the Batch as per the configured Credit Card Process options, and so the original Authorized transactions cannot be added as revenue.

The Permanent Rejection message is also misleading, and may prompt users to contact Donors asking for their Credit Card details. This step is not usually required, and Blackbaud Support can confirm for you if there is a valid Credit Card Token in the CRM database. 

The rejection message will currently be:
"The donor’s current credit card information cannot be used to successfully process this payment. Please contact the donor to get updated credit card information. You will need to update the credit card information in the batch row to process the current payment. You will need to update the credit card information on the original revenue commitment record in order to process future payments."
Download and install the latest patch which contains all fixes from previous patches. If you are running an older version, download and install the latest version and then the patch.

Environment

 Blackbaud CRM
 4.0
 4.0
 Service Pack 4
 3.0.516

Was this article helpful?