Use this link to share with your colleagues:
Payment Exception Resolution: https://help.pm.leapevent.tech/a/31530
This article is old! Wouldn't you rather read something... fresher?
There may be outdated information or suggestions in this article that made sense at the time of the release, but no longer. For the most up-to-date information about this topic, use a keyword in the search bar above. If you're looking for more current release notes, you can find those here.
Partly because we're no longer storing credit card information, and partly just to make the system easier to use, we've implemented a new process for handling payment exceptions.
Payment exceptions generally happen at the box office for one of two reasons:
- The patron's credit card information was entered incorrectly, or the card was simply declined.
- The patron's credit card is valid, but something went wrong while PatronManager was communicating with the credit card processor.
1. Invalid or Declined Credit Card
There are no existing payment transactions for this Ticket Order. If you see this message, the patron's card has not been charged -- you should re-enter the information and try again.
2. Processor Error, version one:
This payment has been authorized, but not captured. If you see this message, the patron's card is valid and it's been authorized, but they haven't actually been charged yet. In almost every case, you should click the "Capture Funds and Complete" button.
3. Processor Error, version two:
The payment has been captured successfully. The patron was charged but the order hasn't quite been completed yet -- click "Complete" to finish the transaction.