I have been using the Express Checkout methods of the PayPal Classic API to allow my site's clients to set up both recurring and one-off payments. Everything works smoothly in my test environment with it pointing to the PayPal sandbox environment.
Now I have been trying to go live. I am following the instructions from https://developer.paypal.com/webapps/developer/docs/classic/lifecycle/goingLive/ which tells me to register my app. I go to https://apps.paypal.com/user/my-account/applications/new and fill in my details, but in the section 'Services used by App' there is nowhere to tick Merchant Services. I'm not using the Adaptive API or Invoicing, but the page won't allow me to submit without filling in something on the Adaptive Payments section. There is no help or guidance on the page.
How do I proceed?
If you're just using Express Checkout and Recurring Payments you won't need to submit an app. The app submission is for people using Adaptive Payment or Adaptive Account API calls.
You should be able to use Express Checkout as long as you have a confirmed and Verified Business PayPal account.
Related
Using ASP Classic
Paypal LIVE Express checkout
It shows the Payment Amount at the checkout, but the payment doesn't go through. The payment doesn't even leave customer's account. I have tried using my wife's paypal account to complete the checkout.
I am only using paypal checkout system and have added all the API information in expresscheckout.asp and paypalfunctions.asp
I have also tried adding these API options too, but still wouldnt work
L_PAYMENTREQUEST_n_NAMEm
L_PAYMENTREQUEST_n_NUMBERm
L_PAYMENTREQUEST_n_AMTm
L_PAYMENTREQUEST_n_QTYm
Any help would be great.... tks
Recently I had implemented Recurring Payments API using the following payment methods:
Direct Payment
Express Checkout
All was working fine on Sandbox account. But on Live account when i enable one payment solution like Express Checkout then service for Direct Payment is disabled and vice-versa. How can i enable both above mentioned payment methods/solutions for Recurring Payments?
You are requested to go to the link below to upgrade your US PayPal account to the Pro account.
https://www.paypal-business.com/paypal-pro
After that you are able to integrate Direct Payment for Recurring Payments.
You can also refer to the link below.
https://www.paypal.com/cgi-bin/webscr?cmd=xpt/cps/general/DPRPLaunch-outside
I am building website which requires customer to update paypal account.
Is there anyway to check the reality of customer's account?
When my customer fill out their paypal account in my site, I want them to be directed to paypal login page to login and paypal will return the result.
Does paypal api support this situation?
Pretty much any implementation of PayPal you choose would follow the flow you mentioned.
Payments Standard would allow you to create basic buttons or create an HTML form and POST directly to PayPal to process. It would send the user to PayPal for login and approval to complete the payment. The transaction details would include the payer status (verified or unverified) as well as the address status (confirmed or unconfirmed) and lots of other details about the order.
Express Checkout is basically the API version of Standard, but it's much more advanced and open to integrate in the way that works best for your site or application. In this case, some of buyer/transaction data is available during the process within your app through API requests and responses, and then you can also get to it via transaction details after the fact just like payments standard provides.
Another option would be to use Adaptive Payments, but if you're doing a general payment of any kind you probably don't need that. That's what you would use if/when you start wanting to split payments among multiple receivers within the same transaction, setup preapproval profiles, etc.
If you happen to be working with PHP my class library for PayPal will make the API calls very simple for you.
You could do what PayPal itself does when you register. Send them a few cents and have them tell you how many when they get it. The payment itself will fail if the account doesn't exist, and telling you how many cents proves that they own the account.
I am currently using payments standard and moving to payments pro. Both are on paypal hosted pages.
Whenever I am testing however, I seem to be directed to the payments standard page rather than the payments pro page. Is there a particular change in the URL i am meant to use? I cant see anything in the documentation that say this is the case.
Cheers
It depends on how you're trying to process payments.
Payments Standard and the Hosted Checkout are two different payment methods but can look kind of similar. With Payments Pro you can use Direct Payment API calls to process credit cards directly from your website or redirect your buyers to a secure PayPal site to complete payments.
The URL you use for the secure checkout page through Payments Pro is different. You should be redirecting buyers to https://payflowlink.paypal.com for the live site and https://pilot-payflowlink.paypal.com for test transactions.
I hope that someone can shed some light on this.
We have developed with PayPal using Website Payments Standard, Website Payments Pro (DoDirectpayment).
There are several other methods like Advanced Checkout, Express Checkout, Payflow Pro, etc. What does each one do? Is there some place where one can see all of these and the differences between them?
To give you a quick and brief overview of some of the main differences.
Website Payments Standard - Uses HTML buttons buttons that you generate from your PayPal account, or you can use a 3rd party cart, or build your own. The buyer is basically redirected to the PayPal payment pages, to enter in their information. You have some control over the checkout flow but are limited in what you can control. There is no monthly fee for this services. The buyer is on the PayPal site when they complete the payment.
Website Payments Pro - There is a monthly fee for this service. With this service, you have full control over the checkout flow. The buyer stays on your site when they enter in their billing information. Instead of using HTML and redirecting the buyer over to PayPal, you will be using API calls to send the data over to PayPal and get a response back.
Express Checkout - This is usually used in conjunction with Pro or by itself. This allows the buyer to checkout with PayPal instead of using their credit card directly on your site. The buyer is redirected over to the PayPal site to sign in or to pay with a credit card. No billing information is entered in on your site. This method uses API call similar to Pro, and allows for some control over the checkout flow. You will have more control with this than you would with Website Payments Standard. The buyer will be back on your site when they actually complete the payment. There is no monthly charge for this service.
Payflow Pro - This is similar to Website Payments Pro. There is a monthly service charge for this service. You can either use the API's and keep the buyer on your site where they enter in all of the information and complete the payment. Otherwise you could also use the hosted checkout pages and have the buyer enter in their billing information on PayPal's pages allowing you to be PCI compliant. Also with Payflow, you can use your own processor as long as it is one that is compatible with Payflow. So don't have to use PayPal as your processor if you choose not to.
Hope this helps.