懒惰的在线商家：信用卡授权
1 分•作者: FesterCluck•10 个月前
这个问题从互联网诞生之初就存在，但线上公司不理解或干脆拒绝理解信用卡授权/交易的工作原理，真是太糟糕了。
商家们：当你们“收取”我的卡时，你们是在进行授权。你们会收到一个与此对应的代码，它确保你们在批量结算交易时，可以收取“最多”这个金额。这种冻结的时长各不相同，但肯定会超过你们下次结算的时间。你们标准的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?