Suppose I have a website that receives money through a payment gateway when people register to the site.
How do you test it? Can it be done without real money?
Most payment gateways, e.g. Paypal, provide sandbox instances and fake credit card numbers that you can use for testing.
Related
Payment gateway isn't setup to test orders. This store can't accept real orders or real payments.
I add a custom payment to Shopify and when I place order using method the error appears
enter image description here
You can't test real payment methods on development stores.
This is because development stores have limitations on them to make sure that they are used only for development.
You'll have to transfer the ownership to your client. You can find more information here.
I am currently working on integrating Sagepay with a financial payment system. We have a Sagepay test account and have been creating transactions within the Sagepay test environment fine.
However, we have a number of test plan scenarios that don't appear to be supported with the Sagepay test environment, e.g.
Create a card payment successfully then do a Repeat against the payment and simulate a failure at Repeat stage (insufficient funds, card expired, etc).
Sagepay support have said this is NOT testable so how is anyone testing their Sagepay integrations? Are there third party test environments available or what is anyone doing to test their Sagepay integrated systems?
Just a suggestion.
Create a PAYMENT transaction.
Block the IP address that the transactions are initiated from (in My Sage Pay)
Try a REPEAT transaction call to the API.
It won't simulate the card expiry / failure to auth scenario, but might help. If you do try, be aware that the setting might not take immediate effect (should be around 15 minutes or so).
I'm considering setting up a eCommerce website and was wondering about the payment side of things.
After some searching I came across Stripe, which seems very similar to PayPal and Google Checkout.
I have a few questions about Stripe and eCommerce in general.
What do I need to take payments on my website? Presume that I have the shop set up, and the buy button in place. Do I need an SSL certificate, I've read something about being PCI complaint? What is and why would I need a merchant account.
Stripe appears to handle a number of things for me, and it stores the users card details. How would this work with things such as logging in to a website. Would I store the users email and password and then when they wanted to buy something Stripe would just handle the credit card side of things or would the entire user details be stored on Stripe.
Can you build and style your own payment form that then connects to Stripe or do you have to use their form on your page?
Do you have to upload all of your products to Stripe or can you store these in your own database and just pass the value of goods purchased to Stripe for payment?
What are the advantages/disadvantages of Stripe and is there any competitors that I should know about?
Thanks
Stripe requests that you should serve up payments pages over SSL. Anyone involved in payment processing must comply with PCI, if you use something like Stripe you will need to serve the payments page on SSL, but Strip will handle the payment info. Check out https://support.stripe.com/questions/do-i-need-to-be-pci-compliant-what-do-i-have-to-do for more details on what you'd need to do.
Not entirely sure on this front, perhaps someone else can comment?
You'll be able to style your page and use Stripe for the payment piece.
You can use Stripe's checkout or build your own (sounds like this is what you want to do) via Stripe.js.
Stripe is generally recognized as one of the most developer-friendly ways to accept payments online. They've worked hard to build a simple service that a developer can get up and running a matter of hours. Braintree is a competitor that may offer some valued added services and you might want to take a look at Balanced as well. I work at LevelUp, which has been used in conjunction with Stripe (as another payment method, similar to PayPal) and as a stand alone solution for apps processing online or mobile payments.
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:
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).
Now I have two questions:
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- 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?
I put an error code in the amount variable that is passed on to IPN via via an NVP api call, like this (lots of value pairs in the middle excluded as irrelevant):
$nvpReq = "BUTTONCODE=HOSTED&..............&L_BUTTONVAR1=amount=".$err_code
EDIT
So it appears I have PayPal Website Payments Standard, which means I cannot incorporate cannot have credit card payment forms directly on my website, but customers have to be directed to PayPal. I'm fine with that, as long as customers have the option to pay with credit cards.
The screenshot looks like PayPal Standard, which is an HTML-only (non-API) integration.
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.
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.
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)
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.
Here are some EC links for programmers:
https://tryit.paypal.com/guide/ec
https://paypal-labs.com/integrationwizard/ecpaypal/main.php
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.
I'm building an e-commerce website from scratch in Ruby on Rails. I currently have PayPal integrated into the site, but the client wants to go with a cheaper solution (that takes less cut than PayPal.) I don't have a website for them, they don't have integration docs. All I got was a Merchant Identification Number (MID). The guy from the payment company said that my client would be able to use this Merchant Identification Number when the shopping cart site asks for it.
The payment guy thinks that my client is using a pre-packaged solution like Volusion or Magneto.
Can I use the Authorize.net payment gateway with just a merchant identification number? It looks like from this page, http://activemerchant.rubyforge.org/classes/ActiveMerchant/Billing/AuthorizeNetGateway.html#method-M000393, that I need an Authorize.Net API Login ID and an Authorize.Net Transaction Key.
What information am I missing from the payment guy?
He said that we could use VeriSign or Authorize.net... but VeriSign was acquired by PayPal, wasn't it?
The merchant ID is required, along with other details, to register for an Authorize.Net account. Once you have that account they will provide you with the API loginand transaction key. Then you. Can integrate it into active merchant and accept payments.