简体   繁体   English

PHP信用卡支付网关集成

[英]PHP Credit Card payment gateway Integration

I need to develop an application which requires integration with credit card payment gateway and hence for testing i need a free developer account or any other possible account so that i can check whether the payment processing is correct or not. 我需要开发一个需要与信用卡支付网关集成的应用程序,因此为了进行测试,我需要一个免费的开发人员帐户或任何其他可能的帐户,以便我可以检查付款处理是否正确。

So please specify me, if there exist some payment gateway that allows the creation of a free account for testing. 因此,请指定我,如果存在一些允许创建免费帐户进行测试的支付网关。

If not is there any other solution,the application doesn't support paypal 如果没有其他解决方案,则该应用程序不支持贝宝

Authorize.Net具有可以集成的开发环境。

You can apply for a free test account with Authorize.Net . 您可以通过Authorize.Net申请免费的测试帐户 You can test all of their APIs as you would for a live integration with no cost to you. 您可以像免费进行实时集成一样测试它们的所有API。

No two credit card APIs are the same, don't integrate an API you don't intend to use. 没有两个信用卡API是相同的, 不要集成您不打算使用的API。

Also, every card processor will have his own quirks, just because you found one card processor that likes your API calls doesn't mean that the one you will intend to use will like your API calls. 同样,每个卡处理器都会有自己的怪癖,只是因为您发现一个喜欢API调用的卡处理器并不意味着您打算使用的那个卡处理器就喜欢您的API调用。

Note that even the nomenclature in the specifications differs widely, authorizations are sometimes called reservations, preauthorizations, captures are sometime completions or charges, and purchases are sometimes sales, authorizations..... Oo 请注意,即使规范中的术语也相差很大,授权有时也称为保留,预授权,捕获有时是完成或收费,而购买有时是销售,授权.....哦

In short: 简而言之:

If you implement one API, it has no merit on judging if another API will work 如果您实现一个API,则无法判断另一个API是否有效


Generally, credit card APIs fall into 2 basic categories: 通常,信用卡API分为2种基本类别:

  1. form APIs - 3d secure is always implemented on the payment processor side and you don't need to do anything to ensure PCI compliance as credit card data is entered on the processor's site - in 90% of cases all you need to do is remote submit a form to the payment processor and catch a callback when transaction is processed 表单API -3d安全始终在支付处理器端实现,并且无需做任何事情来确保PCI合规性,因为在处理站点上输入了信用卡数据-在90%的情况下,您需要做的只是远程提交支付处理者的表单,并在处理交易时捕获回调
  2. direct APIs - 3d secure must be implemented on your side in 90% of cases and you need to ensure a minimum of PCI DSS compliancy as credit card data is entered on your site (no storing of full PAN and CVV, SSL certificate, ...) - this one usually included 2 apis for processing authorizations (authorize/purchase and pares submit) and APIs for refund, capture of authorizations and void of authorizations 直接API-在90%的情况下,都必须在您身边实施3d安全,并且由于在您的站点上输入了信用卡数据,因此您需要确保符合PCI DSS的最低要求(不存储完整的PAN和CVV,SSL证书,.. 。)-这通常包括2个用于处理授权的API(授权/购买和对等提交)以及用于退款,获取授权和取消授权的API

Note, you can usually use a form API to do authorizations and direct API for capture, refund and void. 请注意,您通常可以使用表单API进行授权,并直接使用API​​进行捕获,退款和作废。

See PCI DSS Self Assessment Questionnaires for Merchants 请参阅针对商家的PCI DSS自我评估问卷

Other than that, going deeper would be going too broad, you will need to specify what kind of integration you are going for before I could elaborate. 除此之外,更深入的介绍可能会太广泛,您需要在进行详细说明之前指定要进行的集成类型。

To see examples of CC apis just google for "credit card processing api", I suggest you take a look at several of them to get a general feeling for things that are similar in many APIs and things that are different. 要查看仅用于Google的“信用卡处理api”的CC api的示例,建议您看一下其中的几种,以大致了解许多API中相似的事物和不同事物。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM