通过语音以编程方式通过电话接受信用卡 +像 Twilio 这样的电话 API（文本到语音和语音到文本）？
是否有人使用 Twilio 或其他语音 + 电话 API 创建了一个系统，以通过电话以编程方式接受信用卡？该系统显然将依靠语音转文本和文本转语音来自动化接受信用卡的过程。
如果是，CC 费用是多少？您使用了哪种语音 + 电话 API？
谢谢！
Has anyone created a system with Twilio, or another voice + telephony API, to accept credit cards programmatically over the telephone? The system obviously would rely on speech-to-text and text-to-speech to automate the process of accepting credit cards.
If so, how much were the CC fees, and which voice + telephony API did you use?
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
抱歉，但这确实是一个糟糕的建议。
在处理卡后，PCI-DSS 不允许您存储 CV2，并且只有在有效需要时才能存储其他详细信息。
此外，Twilio 不符合 PCI-DSS 一级标准，因此呼叫首先通过其网络传递的事实存在缺陷。它们将由 Twilio 存储。
使用第三方 ASR 提供商，他们无疑也会在转换后存储他们从录音中给您的响应。
总而言之，不值得这么麻烦/冒险，请使用经过独立 QSA 一级认证的专用提供商。
Sorry but this is really bad advice.
PCI-DSS will not allow you to store the CV2 after the card has been processed and other details can only be stored with valid need for them.
Also, Twilio is not PCI-DSS Level One compliant so the fact that the calls pass over their network in the first place is flawed. They will be stored by Twilio.
Using a 3rd party ASR provider, they will no doubt store the response they give you from the recording too upon conversion.
All in all, it is not worth the hassle/risk, use a dedicated provider for this that is Level One certified by an independent QSA.
是的，我已经这样做了，但由于与信用卡支付处理相关的 PCI-DSS 要求，这在技术上并不简单。评估的交易费用很可能会高于实际水平，因为您根本无法存储信用卡 CV2 值。使用有效 CV2 值完成的交易通常由收单银行以较低的费率处理。
我会忘记为此转录用户语音，Twilio 尚不支持允许直接语音输入的语法，并且对于此用例来说使用转录服务会很麻烦。您想要捕获的唯一数据是信用卡号、到期日和可选的帐单邮政编码（对于 AVS）。所有这些数据都是数值数据，可以使用
Twilio 有一个名为 Tropo 的竞争服务，它支持捕获语音输入的简单语法。我认为这是 Twilio 上唯一薄的 Tropo。 Twilio 有更好的 API，更便宜，并且由非常友善、乐于助人的人员运行。
最后你不想存储 CC 号码！不值得这么麻烦！您必须存储过期时间和 zip，因为 Gather 动词一次捕获一件事，然后通过 POST 或 GET 提交到您的应用程序。最后捕获信用卡号本身，然后立即提交到您的网关以进行购买、授权或标记化。
希望这有帮助。
Yes I have done this, but it's technically non-trivial due to the PCI-DSS requirements associated with credit card payment processing. More than likely the transaction fee assessed will be higher than it could be because you simply cannot store the credit card CV2 value. Transactions completed with a valid CV2 value are often processed with a cheaper rate by the acquiring bank.
I would forget about transcribing user speech for this, Twilio doesn't yet support grammars that would allow straightforward voice input, and using the transcription service would be cumbersome for this use case. The only data you will want to capture are credit card number, expiry date, and optionally billing zip code (for AVS). All these data are numerical and can be captured using the
<Gather>TwiML verb.There is a competing service to Twilio called Tropo, and the support simple grammars for capturing voice input. I think that is the only thin Tropo has on Twilio though. Twilio has a nicer API, is cheaper, and is run by very nice, helpful people.
Finally you DO NOT want to store CC numbers! It's not worth the trouble! You will have to store the expiry and zip because the Gather verb captures one thing at a time and then submits to your app via POST or GET. Capture the credit card number itself last, and then submit to your gateway immediately for purchase, authorisation, or tokenisation.
Hope this helps.
我认为您不会发现这是一个非常受欢迎的选择。如果有人给你一个信用卡号码，你想让这件事尽可能简单——这意味着要与一个人交谈。
但如果您决定通过 Twilio 取卡，请使用键盘（就像 Steve 所说，使用 Gather 动词）（当我致电我的信用卡公司时，他们会要求您输入信息，而不是使用语音识别，这是一种很好的指标，哪个效果更好）
I don't think you'll find that's a very popular option. If someone's giving you a credit card number you want to make that as easy as possible -- and that means talking to a person.
But if you do decide to take cards through Twilio, use the key pad (like Steve said, use the Gather verb) (When I call my credit card company, they ask you to type it in rather than using voice recognition, which is a pretty good indicator which one works better)
像 Twilio 这样的托管解决方案肯定无法正常工作，但您始终可以考虑在内部构建一个系统。今天与 Freeswitch + CMUSphinx< /a> 您可以轻松构建 IVR 来以非常高的准确度识别信用卡号。
由于您将自己托管该系统，因此不存在隐私问题。
Hosted solution like Twilio woudln't work for sure, but you can always consider to build a system inhouse. Today with Freeswitch + CMUSphinx you can easily build an IVR to recognize credit card numbers with very high accuracy.
Since you will host this system yourself, there will be no issue with the privacy.
无论“如何”：
3：Twilio 未经认证
证明：
https://www.twilio.com/help/faq/twilio-basics/what-can-i-do-to-keep-my-twilio-application-workflows-pci-driven
Regardless of the "how":
3: Twilio is not certified
Proof:
https://www.twilio.com/help/faq/twilio-basics/what-can-i-do-to-keep-my-twilio-application-workflows-pci-compliant
因此，Twilio 最近宣布它的作用正是这个问题中提到的。
目前仅支持 Stripe，但也接受其他网关的请求： https://www.twilio.com/ pay/request-connector
详细信息：https://www.twilio.com /docs/voice/twiml/pay
So Twilio recently announced which does exactly what was spoken about in this question.
Currently only with Stripe but accepting requests for other gateways too: https://www.twilio.com/pay/request-connector
Details: https://www.twilio.com/docs/voice/twiml/pay