We have recently discovered that it is possible for a BBIS donation (using Payment 2.0) to be charged one amount, with a different amount being downloaded into batch. While we cannot yet reproduce this issue, we have seen this happen with a recent donation.

In this particular instance it is causing us to make an embarrassing call to a major donor to ask how much they intended to donate to us.

While there is custom javascript on the donation page used in this transaction, I would argue that nothing on the client side should allow the user pay the incorrect amount for a transaction.

I would like to propose the idea that BBIS/CRM/BBPS ensures that a donor is charged the actual amount of the transaction (as it appears in the DonationTransactions table and ultimately in Batch).