I have a website that has two versions: live(mywebsite.com) and dev (dev.mywebsite.com). "Live" for real users and "dev" for development process.
So, I want to use PayPal Live mode on the live website and PayPal sendbox for testing on the "dev" subdomain. How can I organize this process?
I am not sure which PayPal product you are using.
Ideally if you just make sure that if you are calling a paypal api in sandbox it will have "sandbox" in the url..Also you can create sandbox account with a different email address that also will help in distinction.
Related
What is the difference between https://sandbox.paypal.com and https://developer.paypal.com ?
I mean: I need to generate API credentials to make some tests on SOAP API for Express Checkout and I can't understand if I need to use my developer account or I need to create a new Sandbox account...
Which one I need to use to test my application?
The Sandbox is the correct place to test your application. Basically you can say: "sandbox.paypal.com" is the test network of PayPal and "developer.paypal.com" is the control center for the live version and the sandbox version.
Read the official documentation >here< if you want to know how to get started with the PayPal Sandbox.
You need to use your REAL PayPal Account for the Dev Portal. In the Dev Portal you create TEST Accounts that you can use for your Sandbox. In the Dev Portal you can also create the API Keys. How you do this is explained in the Link that I mentioned.
I am working with WordPress and will be setting up online shops using PayPal for multiple clients.
Can I create a single PayPal Sandbox Developer Account through my personal PayPal merchant account and then use that to test my integrations for different clients? In other words, I want all the transaction emails to come to me while testing and not to my clients.
Thanks in advance!
If sites are all going to create the same call then yes, that what I normally do, Il include my PayPal login and once I'm done testing I simply include the client PayPal login instead.
If written a simple paypal standard checkout which sends a form to
https://www.sandbox.paypal.com/cgi-bin/webscr?
together with get variables like items, tax, adress, business, redirect URL, etc.
Under developer.paypal.com I have one paypal-facilitator#... & paypal-buyer#... account. (The facilitator is used as business variable in my URL).
After a lot of testing everything runs smooth and ready for production. My Question is how do I bring this live? Does it suffice to use
https://www.paypal.com/cgi-bin/webscr?
as Checkout URL? Or do I have to recreate the facilitator account in some paypal production environment?
If you simply replace the url "https://www.sandbox.paypal.com/cgi-bin/webscr?" with "https://www.paypal.com/cgi-bin/webscr?" it will switch to live mode, please also make sure that you use Live PayPal account credentials as the sandbox/facilitator accounts will not work in live mode.
I have an asp.net website that is supposed to allow users to make payments with Paypal. I want to test it with the Paypal sandbox.
So I created a developer/business account at "developer.paypal.com'.
Using this account I created a lot of fake email accounts, some personal, some business, for testing. But now, I want to tell the website to enable IPN, and also, to send IPN notifications to a particular URL. I don't see a place on the site to do that. (I assume this would be in the sandbox site, not in the real site).
Any help is appreciated.
Try enabling it on the account level (log into the sandbox account and set it there). There is an IPN simulator as well.
I recently set up Paypal payments standard on my web app and things are working fine. I am able to use Paypal sandbox to test and things work the way I expect.
However, I would like to send out the app to my beta testers and allow them to test making payments without actually using their Paypal accounts or credit cards. I can create sandbox merchants and sandbox payees, but that doesn't quite do it. My button send them to sandbox.paypal.com... but when they get there they are asked to log in with a developer/sandbox password. It doesn't just let them login with the test payee account.
I can work around this, but I wanted to see if I was missing something.
Ya this type of situation was not what we intended the sandbox to be used for. Every sandbox account is tied to a developer account so there is no way around this.
You can do your unit testing or test your application in sandbox, and go live to actually have your clients start using it. There was no plan to have your clients test making payments in sandbox.