难道这个简单的贝宝的解决方案允许信用卡交易和负面测试？ [英] Does this simple paypal solution allow credit card transactions and Negative Testing?
问题描述
我很困惑的服务，并在这里PayPal网站似乎也服务了400的和404。
I am so confused about the services and over here the paypal website also seems to be serving up 400's and 404s.
这是网页如何寻找我的网站上的客户，当他们准备支付：
This is how the webpage looks for customers on my site when they are ready to pay:
据我所知，我没有防爆preSS结帐，但我不知道我是否有网站付款专业版（我公司创建了此帐户）。
As far as I know, I don't have Express Checkout, but I'm not sure if I have Website Payments Pro (my company created this account).
现在我有两个问题：
1 - 这只是沙箱。但在的真正的网站，这是否解决方案，使用户有机会通过信用卡付款？其实我已经成功地在沙盘做了信用卡交易，我只是担心，因为我听说，客户只能做在贝宝网站付款专业直接刷卡交易。贝宝网站信息过载，我无法找到我的路周围回答简单的问题是这样的。
1- This is just the sandbox. But on the real site, does this solution that give users the opportunity to pay by credit card? I've actually successfully done a credit card transaction in the sandbox, I'm just worried because I've heard that customers can only do direct credit card transactions in PayPal Website Payments Pro. The PayPal website is overloaded with information and I can't find my way around it to answer simple questions like this.
2 - 是否有可能做交易的负面测试这个网页上？如模拟活动用户的信用卡或PayPal账户没有足够的平衡？如果有可能，我现在用的是ButtonManagerAPI，然后才是正确的方式下面的方法去做？
2- Is it possible to do negative testing for transactions on this page? Such as simulating the events that the user's credit card or Paypal account doesn't have enough balance? If it is possible, and I am using the ButtonManagerAPI, then is the technique below the correct way to go about it?
的我把一个错误code。在经由通过NVP API调用传递给IPN，这样的金额变量（大量的中间值对排除，因为无关）：的
$nvpReq = "BUTTONCODE=HOSTED&..............&L_BUTTONVAR1=amount=".$err_code
修改
所以看起来我有贝宝网站付款标准，这意味着我不能合并不能直接在我的网站的信用卡支付形式，但客户必须到PayPal。我很好与，的只要客户可以选择用信用卡支付的。
推荐答案
的截图看起来像贝宝标准，这是一种HTML只（非API）的集成。
The screenshot looks like PayPal Standard, which is an HTML-only (non-API) integration.
这可以收到钱可以使用防爆preSS结帐API的..一般通过与API USER / PWD /签名验证的任何常规业务帐户。对于编程/开发资源的企业，EC是目前推荐的方式来接受PayPal付款。
Any regular business account that can receive money can make use of the Express Checkout API.. typically by authenticating with an API USER/PWD/SIGNATURE. For businesses with programming/development resources, EC is by far the recommended way to accept PayPal payments.
如果您通过SOLUTIONTYPE =鞋底在最初SETEX pressCheckout调用，它将接受来自没有一个PayPal帐户，类似于你在上面显示标准的截图谁客户的客户的信用卡。
If you pass SOLUTIONTYPE=Sole in the initial SetExpressCheckout call, it will accept credit cards from "guest" customers who don't have a PayPal account, similar to the Standard screenshot you're displaying above.
选择EC超标的主要原因是，它是你的结帐软件和PayPal的服务器之间的更紧密的握手。使用标准的HTML只，顾客被重定向远离您的网站和一个成功的事务被提交后，（他们可能留在paypal.com，而不是点击返回或他们的浏览器可能会崩溃返回之前可能不会返回到您的网站---而与EC返回到您的网站是内置任何接触金融体系）之前
The main reason to choose EC over Standard is that it's a much tighter handshake between your checkout software and PayPal's servers. With Standard's HTML-only, the customer is redirected away from your site and might not return to your site after a successful transaction is committed (they may stay on paypal.com and not click to return or their browser might crash before return --- whereas with EC the return to your site is built-in before anything touches the financial system)
随着最近developer.paypal.com的测试，所有新的沙盒商家帐户满临帐户默认情况下。如果，除了接受PayPal付款，您希望直接在自己的网站建立一个信用卡报名表报名参加现场Pro帐户将是有益的。
With the recent beta of developer.paypal.com, all new sandbox Business accounts are full Pro accounts by default. Signing up for a live Pro account would be useful if, in addition to accepting PayPal payments, you wished to create a credit card entry form directly on your own site.
下面是一些程序员EC链接：
Here are some EC links for programmers:
- https://tryit.paypal.com/guide/ec
- https://paypal-labs.com/integrationwizard/ecpaypal/main.php
Button Manager的API是不太可能对你有用。而且有办法做的沙盒负面测试，但它真的不是一个重要的问题，当你还没有决定对产品/ API。
The button manager API is unlikely to be useful to you. And there are ways to do negative testing with the sandbox, but it's really not an important concern when you're still deciding on a product/API.
这篇关于难道这个简单的贝宝的解决方案允许信用卡交易和负面测试？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
