authorize.net C# 包装器/库
Authorize.net 有没有好的库或包装器?他们网站上提供的代码示例似乎有点……原始。我正在寻找一个易于使用、面向对象的 API,我可以简单地设置一些属性,并且它负责处理底层的所有管道代码。
我发现了一些随机的博客文章,人们提供了他们编写的代码,但是博客文章中提供的代码通常并不能让人高度确信它已经过良好的测试。我的意思是,如果有必要,我们会考虑这些,但我们更喜欢看起来已经经历过某种发布/测试周期的东西......即使它只是发布在 codeplex 或其他东西上。
谢谢! :-)
Are there any good libraries or wrappers for Authorize.net? The code samples available from their site seem a little ... raw. I'm looking for an easy to use, object oriented API that I can simply set some properties, and it takes care of all the plumbing code under the hood.
I've found a few random blog posts of people offering their code that they've written, but code offered in a blog post doesn't give a high degree of confidence generally that it's been well tested. I mean, we'll consider these if we have to, but we'd prefer something that looks like it's gone through some sort of release/testing cycle ... even if it's just that it has been posted on codeplex or something.
Thanks! :-)
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
回答有点晚了,但也许是这个?
http://code.google.com/p/ payment-processor/
A little late answering, but perhaps this?
http://code.google.com/p/payment-processor/
我在一些电子商务网站上使用 SharpAuthorize.com。其中一个每月大约赚 1 万美元……
网站上有说明,但您应该在实际代码中使用交易 ID,而不是用户名和密码。
I use SharpAuthorize.com on a few eCommerce sites. One of which makes around $10K / month...
It is noted on the site, but you should use a transaction id instead of the username and password in real code.
查看我的答案这里,它应该可以帮助你。在我的回答中,我指出博客文章作为参考。不过,您可能需要查看修订版才能看到我的完整答案。由于某种原因,它对我来说被切断了。查看博客文章的网关提供商实现部分。它应该可以帮助您并让您继续实现自己的代码来与 Authorize.Net API 进行通信。我使用过类似的实现,它对我来说效果很好。
See my answer here, it should help you out. In my answer, I point to a blog post as a reference. You may need to view the revisions to see my whole answer, though. For some reason it is getting cut off for me. Check out the Gateway Provider Implementations section of the blog post. It should help you out and get you going on implementing your own code for talking to the Authorize.Net API. I've used a similar implementation and it has worked well for me.