This has been a problem since the dawn of the internet, but online companies not understanding or straight up refusing to understand how cc authorizations/transactions work is just awful.
Merchants: When you "charge" my card, you're pulling an authorization. You receive a code that corresponds with that, and it ensures you can collect UP TO that amount when you close the transaction in a batch. The length of that hold varies, but can definitely extend beyond the moment of your next closed batch. Your standard 10,14, or 30-day response is actually a default you or your provider setup. It's the authorization expiration period, and it's sent during the initial transaction. The purchaser's bank honors it.
With that auth code, you may update the authorization for less without pulling a new auth code. You may also include the transaction in a batch for the given amount OR LESS. Closing a batch collects.
Leaving dangling authorizations out there when your applications have bugs should not be the onus of your users. Implement proper authorization updates in your error handling. No accidental payments or refunds to worry about, just update the authorization to $0.
Community, what are your thoughts?
