定期计费 /w cvv2
我正在实施一个支付系统，但我不知道如何处理 cvv2 代码。我们的服务提供两周免费试用。我们要求用户输入账单信息，然后我们以 1 美元对他们的卡进行身份验证。两周后，我们进行了单独的身份验证和验证。 capture（我们不能执行prior_auth_capture，因为用户可以在试用期间升级他们的计划）。从那时起我们每个月都会向他们收取费用。
在我们的情况下我应该如何使用 cvv2 代码？我们不应该存储 cvv2 代码，因此我只能将其与我们最初执行的身份验证一起使用。仅仅在身份验证上这样做还值得吗？我不希望第一次身份验证成功（因为它有 cvv2），然后之前的身份验证+捕获失败，因为我们不保留它。
长话短说，我是这家公司的新人，我正在努力解决他们的计费问题。特别是国际客户的付款被拒绝（部分而非全部）。当前的系统不会将卡上的姓名传递给 auth.net，也不会进行任何类型的地址验证，我怀疑这给国际客户带来了麻烦。
我认为使用 cvv2（如果它适用于我们的情况）并发送卡上的实际姓名应该可以解决国际客户的问题。如果不是，那么接下来要尝试的就是地址验证？这有道理吗？抱歉，如果我的想法有点分散。
谢谢！
I'm implementing a payment system and I'm not sure how to deal with cvv2 codes. Our service offers a two week free trial. We require the user to enter in billing information and we auth their card for $1. Two weeks later we do a separate auth & capture (we can't do a prior_auth_capture because the user can upgrade their plan during their trial). We bill them each month from then on.
How am I supposed to use the cvv2 code in our situation? We're not supposed to store the cvv2 code, so I can only use it with the auth that we initially do. Is it worthing doing this just on the auth still? I don't want the first auth to succeed (because it has the cvv2) and then prior auth + captures to fail because we don't keep it around.
Long story short I'm new at this company and I'm trying to fix their billing problems. International customers in particular are getting payments declined (some, not all). The current system doesn't pass along the name on the card to auth.net nor does it do any sort of address verification, which I suspect is what's giving international customers trouble.
I would think using cvv2 (if it'll work in our situation) and sending the actual name on the card should remedy the issue for international customers. If not then address verification would be the next thing to try? Does this make sense? Sorry if my thoughts are a bit scattered.
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
发送卡上的姓名是没有用的，因为卡处理公司不会收到或使用该姓名。此外，除了支付信用卡处理费用的公司之外，AVS 不会给任何人带来麻烦，因为如果不这样做，他们的费用会高得多。
对于 Authorize.Net，您应该使用他们的 ARB 系统进行定期付款。订阅建立后，您无需执行任何操作，直到订阅用完或取消为止。这包括处理 CVV 和 AVS 问题。如果您选择对每笔付款使用他们的 AIM API，那么您将会遇到问题，因为如果您希望对这些交易执行 CVV，则需要捕获每笔交易的 CVV 号码。当然，处理交易不需要 CVV，因此如果您不提交，交易仍然会进行。
如果国际持卡人遇到问题，则更有可能是因为该卡是国际卡且风险更高，然后是 AVS 或 CVV 问题。这两个工具用于您端的欺诈检测。未获得处理者的卡批准。
Sending the name on the card is useless as it not received nor used by the card processing companies. Also, AVS won't give anyone trouble except for the company who pays the credit card processing bills as their fees will be much higher for not doing it.
With Authorize.Net you should be using their ARB system for recurring payments. Once the subscription is established you don't have to do anything until the subscription runs out or is cancelled. This includes handling CVV and AVS issues. If you choose to use their AIM API for each and every payment then you'll have issues as you'll need to capture the CVV number for every transaction if you wish to perform CVV on those transactions. Of course, CVV is not required to process a transaction, so if you don't submit it the transaction will still go through anyway.
If international card holders are having issues it's more likely because the card is international and higher risk then then AVS or CVV issues. Those two tools are for fraud detection on your end. Not card approval by the processors.