We’ve addressed an issue where updated payment amounts were correctly charged and reflected in MerchantTrack but not saved properly in PEAK 15. This led to discrepancies between what customers were charged and what was recorded in the system.


What Was Happening

In some cases, users updated the payment amount on a submitted payment but processed it before saving the change. As a result, the correct amount was charged, but the original amount remained in PEAK 15. This created confusion and potential reporting errors.


What’s Changed

To prevent this from happening:

  • If the payment amount is changed, the Process Payment button is now disabled until the record is saved.
  • A clear warning message appears, reminding users to save the payment before processing.
  • Once saved, the button is re-enabled, and the updated amount is correctly recorded.

This update applies to all payment methods and merchant accounts for consistency.