支付网关理论
我是社区和 PHP 的新手，所以我的问题对某些人来说可能听起来很愚蠢，但让我们进入正题。
我目前正在学习使用 PHP，其中一部分包括实现对工作站点的电子支付。我在网上读了很多资料，但我无法弄清楚一些事情：
支付网关 <-> 之间有区别吗？支付处理器，或者它们用于描述同一事物？
- Authorize、Paypal、Google Checkout 等第三方时，我们真的需要一些硬编码吗？还是您可以只遵循他们网站上提供的信息？
我浏览了一些（我认为）主要的支付网关，但没有看到任何提及 SOAP 和 WSDL 的内容。它们是否真的以我无法找到的方式需要，或者它们只是很少使用，这就是为什么我没有找到任何提及它们的原因？
提前致谢，如果我听起来像个菜鸟，我很抱歉。希望在你们的帮助下学得更快，伙计们。
I'm new to the community and PHP, so my question may sound stupid to some, but let's get to the point.
I'm learning to use PHP at the moment, and part of it includes implementing an e-payment to an working site. I've read a lot on the net, but I can't figure out some things:
Is there a difference between Payment Gateway <-> Payment Processor, or they are used to describe a same thing?
When using a third party like Authorize, Paypal, Google Checkout, or something like this, do we really need some hard coding, or can you just stick to the information provided on their sites?
I looked through some of the (I think) major payment gateways and I haven't seen any mention of SOAP and WSDL. Are they really needed in a way that I can't find out, or are they are just used rarely and that's why I haven't found any mention of them?
Thanks in advance, and sorry if I sound like a noob. Hope to learn faster with your help, guys.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
一般来说，支付处理器是实际处理支付的供应商。大多数支付处理商都提供网关，这是您用来提交付款进行处理的接口。
使用支付处理器时，您必须编写的代码量将根据处理器提供的网关的实现以及您选择的实现之一而变化。通常至少有两种——某种最灵活的原始 API，以及某种与处理器的超级简单链接。 PayPal Standard 和 Google Wallet 是后者的好例子，而 Authorize.net 的典型用法是前者的好例子。如果您通常使用 API，您需要实现自己的订单创建流程/购物车，然后您只需在最后提交付款和其他详细信息。这使您可以保留网站上的所有内容（不一定是数据，而是体验）。简单的途径通常涉及在购物过程中将用户一次或多次发送到处理商站点，通常会导致定制有限并明显破坏用户体验。
有些网关将使用 SOAP/WSDL，有些将使用简单的 REST 接口，有些将使用其他实现。然而，他们通常选择在内部实现，但大多数都会提供一个库来将其用于主要脚本语言（PHP、Ruby、Python、C#.Net、VB.net），因此您很可能不需要手动制作您只需使用提供的库并处理返回的结果即可进行调用。
Generally speaking a Payment processor is a vendero that actually processes payments. Most Payment Processors offer gateways which is the interface you use to submit a payment for processing.
When using a payment processor how much code you have to write is goign to vary with the implementations of the gateway the processor offers and which one of those implementations you choose. Normally there are at least two - some kind of raw API which is the most flexible, and some kind of super simple link to the processor. PayPal Standard and Google Wallet are good examples of the latter, while typical usage of Authorize.net is a good example of the former. IF you use the API generally you need to implement your own order creation process/shopping cart and then you would jsut submit the payment and other details at the end. This allows you to keep everything on you site (not necessarily the data but the experience). The simple route usually involves sending user to the processors site one or more times during the shopping process usually resulting in limited customization and a clear break in user experience.
Some Gateways will use SOAP/WSDL some will use simple REST interfaces, and some will use other implementations. Its generally however they chose to implement in house, but most are going to offer a library to use it for the major scripting languges (PHP,Ruby, Python, C#.Net, VB.net) so odds are you wont have to manually make the calls you'll just utilize the library the provide and deal with the results returned.
嗯，这是一个棘手的商业支付网关，不同的第三方实施方式在不同的站点之间有所不同。您可以找到最容易实现的一个，但执行此操作时要小心。是的，支付网关和处理器之间是有区别的，处理器是使付款转到银行并转账的地方，网关确保您输入的凭据是正确的
快乐编程
well this a tricky business payment gateway differ from one site to another from different 3rd party implementation. u can find the easiest one for you to implement but be careful when u do this. and yes there is a difference between payment gateway and processor which is the processor is what make the payment go to the bank and transfer the money, the gateway make sure the credential that u have enter is correct
happy programing