Authorize.net 测试在测试模式下下降
在测试模式下使用 Authorize.net，如何测试“下降”？ 如果测试模式只是批准我的所有交易，而不管假帐单地址如何......
Using Authorize.net in test mode, how I can test "declines"?
If the test mode just approves all my transactions regardless of fake billing addresses ...
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
测试以生成特定交易结果
在开发者测试环境以及生产环境中测试交易结果时，您可以通过使用旨在生成特定交易结果的测试信用卡号提交测试交易来生成特定的响应原因代码：Visa 测试信用卡号“ 4222222222222”。该卡号用于测试，并且只能用于该目的。通过将帐户置于测试模式或提交 x_test_request=TRUE 来提交测试交易，其中美元金额值等于您想要生成的响应原因代码。
例如，要测试 AVS 响应原因代码编号 27，请提交信用卡号“4222222222222”和金额“27.00”的测试交易。
要在实时环境中测试 AVS 或 CCV 响应，您需要提交具有正确街道地址、邮政编码和卡代码信息的实时交易以生成成功的响应，以及提交不正确的街道地址、邮政编码和卡代码信息以生成其他响应。您可以立即作废成功的交易，以防止处理实时测试交易。这可以在商户界面的未结算交易页面上快速完成。无法在开发人员测试环境中测试 AVS 或 CCV 响应。有关 AVS 的更多信息，请参阅商家集成指南，网址为 http://www.authorize.net/support/商人/。
Testing to Generate Specific Transaction Results
When testing transaction results in the developer test environment as well as the production environment, you can produce a specific response reason code by submitting a test transaction using a test credit card number designed to generate specific transaction results: Visa test credit card number “4222222222222.” This card number is intended for testing and should only be used for that purpose. Submit the test transaction by either placing the account in Test Mode, or submitting x_test_request=TRUE, with a dollar amount value equal to the response reason code you would like to produce.
For example, to test the AVS response reason code number 27, submit the test transaction with the credit card number “4222222222222” and the amount “27.00.”
To test the AVS or CCV responses in the live environment, you will need to submit live transactions with correct street address, ZIP Code and Card Code information to generate successful responses, and incorrect street address, ZIP Code and Card Code information to generate other responses. You can void successful transactions immediately to prevent live test transactions from being processed. This can be done quickly on the Unsettled Transactions page of the Merchant Interface. It is not possible to test the AVS or CCV responses in the developer test environment. For more information about AVS, see the Merchant Integration Guide at http://www.authorize.net/support/merchant/.
如果您使用 AIM API，安东尼在其回复中提供的信息是准确的。如果您使用的是 CIM API（该 API 允许您在 Authorize.net 的服务器上存储客户信息并使用令牌对其进行收费），则过程会略有不同。
另外，请注意，这些交易的
4222222222222测试卡号只有 13 位数字，而不是 16 位。我没有立即注意到这一点，但它会产生影响。The information anthony provided in his response is accurate if you are using the AIM API. If you are using the CIM API (the API that allows you to store customer information on Authorize.net's servers and charge them using a token), the process is slightly different.
Also, take note that the
4222222222222testing card number for these transactions is only 13 digits long, not 16. I didn't notice that immediately and it makes a difference.