懒惰的在线商家：信用卡授权
自互联网诞生以来，这一直是一个问题，但在线公司不理解或直接拒绝理解信用卡授权/交易的运作方式，实在令人失望。
商家：当你“收费”我的卡时，你实际上是在进行一项授权。你会收到一个与之对应的代码，这确保你在关闭交易时可以收取高达该金额的款项。这个授权的保持时间各不相同，但确实可能会超出你下一个关闭批次的时刻。你常见的10天、14天或30天的响应时间实际上是你或你的服务提供商设定的默认值。这是授权的有效期，并在初始交易时发送，购买者的银行会予以承认。
有了这个授权代码，你可以在不重新拉取新授权代码的情况下，更新授权金额为更少的数额。你也可以将该交易以给定金额或更少的金额包含在一个批次中。关闭批次后会进行结算。
当你的应用程序存在漏洞时，留下悬而未决的授权不应由用户承担责任。在错误处理时实施适当的授权更新。无需担心意外的付款或退款，只需将授权更新为$0。
大家对此有什么看法？
查看原文
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.<p>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.<p>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.<p>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.<p>Community, what are your thoughts?