I would like to find the Paypal BillMeLater documentation. I've looked over the developer site many times and searched all over Google; where might it be?
Also - where can I create a sandbox account for testing payments processed via BillMeLater?
To be clear, I would like to integrate BillMeLater so that a user is not redirected away from the site, but can still use this method to pay.
This is not currently possible; BillMeLater can only be used via the paypal site (eg: through express checkout)
Related
My goal is to create a business PayPal sandbox account which has the account type Business Pro and which allows me to grant access to third party APIs.
Currently there are two ways of creating sandbox accounts in PayPal. The first method involves creating an account from the developer dashboard and linking that account to the PayPal dev account via the link provided on the Sandbox Accounts page. However, creating an account this way does not allow me to link third party APIs. When I log into the sandbox account and click the link to update Api Access it gives a browser error of "Too many redirects".
The second way of creating a sandbox account involves going to sandbox.paypal.com and signing up a Business account on there. I am then able to link this sandbox account to the PayPal dev account from, again the link provided in the dev dashboard. Creating a sandbox account this way also allows me bypass the browser error and link third party APIs. However, it doesn't allow me to upgrade that sandbox account to Business Pro, and gives me the following error: Something went wrong. PayPal Payments Pro could not be enabled. Try again.
Is there any way I can create a sandbox account which is able to link to third party APIs and be a Business Pro type?
To anyone else that might have this problem, I had to create a ticket here: https://www.paypal-techsupport.com/app/ask and ask them the question of why it wasn't linking. They had to change my account type to a new one that they were/are developing.
I have spent the last couple of nights bashing my head against the wall amongst a see of conflicting out of date documentation and semi-helpful blog posts that were/are appropriate to what I am trying to do.
Essentially I want to write a wee personal app do download my images from PicasaWeb/Google+ and store them on my local hard disk.
I have managed to do the following:
Figured out the GData API for the appropriate request to get private album data (works fine in my 'google-logged-in' chrome browser)
Got the correct private data back from my GData URL with the token generated by the OAuth playground.
Managed to get an OAuth2 token back from https://www.googleapis.com/oauth2/v3/token using JWT.
However - when I try my access token I generate myself I get back a forbidden response with the message 'Not authorized to view access private'.
I am pretty stumped - my only guess is that my service account configured in google developers console doesn't actually have access to my personal google stuff like google+ photos. When I look in there I can see the OAuth playground has access. How do I give my app access - and do I need to in this scenario?
Thanks in advance,
Robert
"my only guess is that my service account configured in google developers console doesn't actually have access to my personal google stuff".
Totally correct.
I guess I see 2-3 questions per month on SO where people have made the false assumption that a Service Account is some kind of proxy to their Google Account. It isn't. It's a completely new and independent account.
The two approaches you can take are:-
Share the items to the Service Account so it has permission to access them.
Give your app direct access to your Picassa account. See How do I authorise an app (web or installed) without user intervention? (canonical ?) for the steps involved.
Our site is ready, but PayPal is still running in Test mode / Sandbox.
How do we make it live and take actually payments? Is this a setting PayPal-side?
CMS is Drupal 7.x
Currently you are having PayPalMode,PayPalApiUsername,PayPalApiPassword,and PayPalApiSignature for test or sandbox mode. But to run on LIVE mode you need to again grab all the above mentioned details from the Real LIVE PayPal account.
Do let us know the Payment method you are using ! I am assuming for DoDirect Payment Method.
Just set PayPalMode = 'live';
On your site, at admin/commerce/config/payment-methods, edit your PayPal WPS settings.
Enter the email address of your real PayPal seller account.
Switch over from "sandbox" to "live", and I would also recommend switching off the debugging mode at this stage.
It is always best to test the live account is working properly by sending through a low-value order using your own credit card. You can then refund the order later if it works.
Hope this will works for you !
You can also follow the following 2 help links:
Drupal Paypal Payment Standard
And
Commerce PayPal Payments Advanced / Payflow Link
(I am reposting this question here because I tried on the google news group and got no responses.)
I need to build a shop for my client, and the client already has a domain and a web site. I need to integrate e-commerce functionality in to the site. This is going to be done by sending AJAX requests to the API.
my question is whether I need to get a partner account for this? I am not yet going to write an app that people would install, I am just building a store for my client. how is it done?
You do not need a Shopify Partner account for this. You can instead create a "Private application" within the normal shopify admin, which will give you the api credentials you need to make stuff happen.
This article on the shopify wiki gives a good overview of the process for getting started (the first sections are most relevant in your case):
http://wiki.shopify.com/Using_the_shopify_api_gem_with_the_credentials_of_a_private_app
I'm getting some rather conflicting information from PayPal. I've spent 2 hours on the phone with them today, and posted my questions on their forums, and I have not received one single solution. So I am turning to SO since people here actually know what they're doing.
I am trying to add the AddressVerify and MassPay APIs to our website. We are currently using the Payflow Pro (DirectPayment, etc) calls with no problems. This uses our PayPal Manager login, password and vendor credentials for authentication via the HTTPS interface. This is all written in PHP using NVP.
However, when I try to add the AddressVerify and/or the MassPay APIs using the HTTPS interface, all I get back is a PNREF and an error saying, "Invalid Tender."
On the forums, I see everyone using email addresses as logins, and a certificate key of some sort. I called PayPal today to figure out how the heck to get that information, and the developer there said I don't use the login with the key and that I'm using the wrong SDK. He told me where to get the Dev Guide and that I should use that instead.
However, the dev guide only outlines what we're already using, and I wasn't about to sit on the phone for another hour and 40 minutes.
So my question is this:
Am I just missing something, or did I just get some bad information? I'm guessing it's the latter, because nobody there seemed to know squat about jack diddly.
Am I correct in assuming that the code ( as outlined here ) is what I should be using? If so, how do I obtain a signature key and presumably a new login & password?
If the dev guy from PayPal is correct and I should be using the HTTPS Interface, then how do I get that to work? Because like I said above, all I'm getting from that is a PNREF and an error message saying, "Invalid Tender."
If anyone has any experience with this and/or some suggestions on how to get this stupid thing to work, I'd be forever greatful!
Thanks in advance!
Brian
In case anybody is interested in knowing, I received a response from the devs at PayPal:
If you are using Payflow then you should be using the Payflow Pro SDK, it would require a User, Vendor, Partner, and Password in the credentials that get passed over. It would also return a PNREF number. If you are wanting to use Website Payments Pro, then your SDK would have either a API Username, API Password, API Signature, or an API Username, API Password,and API Certificate. The AddressVerfiy API is an API that is available for Website Payments Pro/PayPal accounts not Payflow. You can find all of the SDK's for both services here. The Payflow SDK's are the ones at the bottom of the page.
So apparently MassPay and AddressVerify is part of the Web Payments Pro, which uses a different SDK than the Payflow Pro stuff. And for this, you need to obtain a separate username, password, and certificate or key. The Payflow Pro credentials will not work with this.
Hope someone else can benefit from my hours of wasted time!