I've seen other postings where people can't load "My Selling Tools" and I happen to be in the same boat.
Support hasn't responded yet and I'm hoping to do a demo Monday of the Windows 8/Paypal API integration from http://paypal.github.io/Windows8SDK/ into WinRT apps - hence turning to may favorite net community, stack overflow :)
The link above gives a sandbox account to allow for third party access, so trying to add that account to allow the third party access but can't even bring up the selling tools to do so. I was able to bring up the selling tools from my main login, but not from within the sandbox login.
Once I login to the sandbox environment and try to access "My Selling Tools" it just hangs. The browser doesn't matter, same result across browsers. I get nothing returned but the wait image. Actually anything on the left hand side hangs not just the selling tools. I've tried more than ten times all throughout the day.
Of course, the hope here is that someone from the PayPal Technical team replies.
I can't wait another hour on hold, I just can't.
I was having the same issues getting into any option on the left in Paypals seller tools, but I stumbled onto the solution.
The links on the left are incorrect. They all begin with "www.beta-sandbox.paypal.com/cgi-bin/..."
The issue is that "beta-" in the URL is invalid.
Using Chrome:
1) Right-click on the option on the left you want to get into
2) Click "Copy Link Address" in the pop-up menu
3) Paste it into the address bar
4) Remove "beta-" from the URL (see the "Profile / My Selling Tools" URL example below)
That's it.
INVALID:
https://www.beta-sandbox.paypal.com/cgi-bin/webscr?cmd=_profile-display-handler&tab_id=SELLER_PREFERENCES
CORRECT:
https://www.sandbox.paypal.com/cgi-bin/webscr?cmd=_profile-display-handler&tab_id=SELLER_PREFERENCES
Hope this helps.
Dave
I'll make sure this gets escalated. As a workaround, you can log in to your sandbox account and then paste this URL in your browser: https://www.sandbox.paypal.com/cgi-bin/customerprofileweb?cmd=_profile-api-access. Could you also reference this post in your ticket if you have not done so yet?
Related
someone knows how to add testers to an action on google package?
So other users can test the implementation on their Google Home devices?
Thanks!
Today you must use the developer's account to test except for the case of account linking where testers can put their own credentials in for that specific step, and test any functionality that relies on that. I am told by the Actions on Google support team that providing a mechanism for testers (with different accounts than the developer) to access Actions/agents prior to deployment is the number 1 requested feature "by far" so hopefully we will see it down the road.
Yes. Make sure everything under "Directory information" is filled out. Then go to the "Release" tab under "Deploy", and click on Alpha (which allows a quicker deploy for up to 20 users without review). Click "Submit for Alpha", and ensure you meet the requirements to check the checkboxes there. After that, you can press "Manage alpha testers" under the Alpha pane, where you can generate a link or add email addresses.
(screenshots anyone?)
I tried to build the Paypal Express Checkout. Last week all runs smoothly, I can create REST API app and the sandbox account as well.
But today, All the details is removed.
And there is this warning
We’re sorry, but something went wrong while getting your credentials.
Please try again.
When I tried to create a new app/new sandbox account it says
We're sorry, something went wrong during account creation. Please try
again.
After some googling and trying some of the solutions like "password is too weak", I realise that all the solutions are from years ago and all the screenshot is the old PayPal interface.
I would assume that this is related to the new PayPal.
PS: I am from Australia and have read the "Non-US developers should read our FAQ"
Anyone know how should I create REST API App?
This is not the correct way to create the API, but this resolves my problem instantly.
I had the same problem. The "Sandbox developer account" dropdown box had no entries although I had set up accounts before - so I couldn't create an app. After some trial and error hacking I finally found a way to inject a valid option in the html select and successfully created the app in the end.
Here's how:
Log in to your developer.paypal.com profile and go to Sandbox - Accounts.
Just use Firebug in Firefox or Developer Tools in Chrome to examine the source: Check the source of your BUSINESS account and you will find a code line like this:
<a class="profile" target="/developer/accounts/detail/22971020450123198612">Profile</a>
Note the id (e.g. 22971020450123198612), the country code (e.g. GB) and the email address.
Now go to Dashboard - My Apps & Credentials and press "Create app"
Open Firebug/Dev. Tools and examine the "Sandbox developer account" dropdown box. Right-Click the empty select in the dom and choose "Edit as HTML". Enter an option tag with your formerly noted values, just like this:
<option value="2297102045097598612,email#domain.com">email#domain.com (US)</option>
Check that the option now appears in the dropdown box.
Enter a name in the "App name" field and press "Create app".
That's it. Hope I could help.
I've signed in to the developer website but when I go to the apps page to create my app I see the following error message:
Problem creating sandbox facilitator account [Error code: 2001]
When I look on the sandbox accounts page I see there is a facilitator account there (xxx-facilitator#xxxx.xxx)
When I click the "create app" button the "sandbox developer account" dropdown is empty and when I try to create an app I get the following error message:
We’re sorry, but something went wrong while creating the application. Please try again.
So far I've:
created new sandbox users
submitted a query to paypal's tech support (no response)
left it a day and tried again
logged in, logged out...
I had the same problem. The "Sandbox developer account" dropdown box had no entries although I had set up accounts before - so I couldn't create an app.
After some trial and error hacking I finally found a way to inject a valid option in the html select and successfully created the app in the end.
Here's how:
Log in to your developer.paypal.com profile and go to Sandbox - Accounts.
Just use Firebug in Firefox or Developer Tools in Chrome to examine the source: Check the source of your BUSINESS account and you will find a code line like this:
<a class="profile" target="/developer/accounts/detail/2297102045097598612">Profile</a>
Note the id (e.g. 2297102045097598612), the country code (e.g. US) and the email address.
Now go to Dashboard - My Apps & Credentials and press "Create app"
Open Firebug/Dev. Tools and examine the "Sandbox developer account" dropdown box. Right-Click the empty select in the dom and choose "Edit as HTML". Enter an option tag with your formerly noted values, just like this:
<option value="2297102045097598612,email#domain.com">email#domain.com (US)</option>
Check that the option now appears in the dropdown box.
Enter a name in the "App name" field and press "Create app".
That's it. Hope I could help.
I got the 'Problem creating sandbox facilitator account' error as well but it was with a different error code of 'TAGETLIST404-20141017053750'. Obviously the suffix is just a timestamp.
The problem seemed to have been caused by the Oauth login popup that initially returned a timeouted session error but appeared to have still logged in anyway as it showed my name in the topright corner. But trying to create new apps returned the sandbox facilitator error.
Clearing cookies and logging in again, not getting the timeout error seemed to fix it and I could create accounts. I know this isn't a great answer but it's something to try.
I waited two days, and the error messages regarding the facilitator account went away. I was then able to make a new business account. This then allowed me to create a REST app without error.
I had the same problem and fixed it by just editing the source a bit.
Right click on the dropdown for your account if it's empty and click on Inspect element in your browser.
Inside the tags for the dropdown, add your email in tags. The email should be of a valid sandbox account that you had created.
For example, if you'd like to add a sandbox account with the email business#example.com,
add business#example.com within the select tags.
Seems like it's something easily fixable from Paypal's side but they haven't bothered fixing it yet.
for PayFlow API - allow up to 3 hours for the change to go into effect.after 3 hours it saved data while clicking.
In my case my primary email account was not confirm. after confirm it allow me
Today, I've just encoutered the same error with you. The problem is how Paypal raise the error, which made us very confuse. The error they should raise is: " You have not created any developer account yet, create an account and try again".
And here is how I fix it:
Go to: https://developer.paypal.com/developer/accounts
Create a BUSINESS sandbox account.
Go back and try create app again to see if it work.
This question already has answers here:
Please login to use the PayPal sandbox feature
(5 answers)
Closed 9 years ago.
DISCLAIMER: This question is specifically for the Paypal forum.
I have two Sandbox test accounts. parijat_kalia#hotmail.com (PERSONAL) and parijat_kalia-facilitator#hotmail.com (BUSINESS). The second one has the API credentials and I am using the NVP API to test our e-commerce subscription plan
. The response I get is :
10501: Invalid Configuration This transaction cannot be processed due to an invalid merchant configuration. Occurs when the billing agreement is disabled or inactive.
Hence, to activate it, I presume I need to log in with this sandbox account into the sandbox website so as to activate the billing agreement. The steps I follow are pretty basic.
Login to developers.paypal.com
Click on Applications tab in the horizontal menu
Click on Sandbox accounts in the vertical menu
Click on the specific accounts 'parijat_kalia-facilitator#hotmail.com' dropdown arrow button.
Click on Sandbox site
When i click on sandbox site, it loads in the PERSONAL account in the email i.e 'parijat_kalia#hotmail.com'. I obviously change this and try to login with the business account credentials. However it does not log me in whatsoever. I have changed the password, literally copy pasted it, but it does not work. Nor does deleting the cookies/clearing the cache and terminating the history help. Also, I am using Chrome, not IE.
Also, I presume this error is with Paypal's sandbox website, since the API call is technically logging me in with the credentials (I infer this since I am getting error 10501).
Can you please tell me what is going wrong?
I had an issue similar to that the other day. I was trying to switch from one developer account to another, but it kept logging me in as the first one. So, I couldn't use any of the sandbox accounts for the 2nd account.
I circumvented this issue by switching to private browsing mode in chrome (ctrl+shift+N) and logging in that way.
I can't guarantee this will fix your issue because it's not the same as mine, but it might help.
Misplacedme's answer worked for me, but I don't have enough rep yet, so I'll reply and add some info.
Chrome: Use an Incognito Window (ctrl+shift+N)
Opera: Use a New Private Window (ctrl+shift+N)
IE: No need for special window. It works as it used to.
Firefox: No need for special window. It works as it used to.
Safari: No need for special window. It works as it used to.
Note: These are all on a Windows 8 PC (sorry, I know most people in their right mind aren't using win8 much less developers)
I'm working on a custom e-commerce system for a client and ran into a fork in the road. The checkout system I'm using is very flexible and is meant to be integrated into an existing Web site. So essentially, I have all my products on a page. Each product has a "Buy Now" button associated with it. When clicking on that button, a modal window opens, showing a cart-like screen with the item they chose being added. From here, they can either close the modal window and "buy" another product or checkout. Here is where the fork comes in:
Option A: They are now redirected to the merchants site for the actual checkout. I can make that page look anyway I want, but it's independent from the client's real site. So if something on the real site changes, I have to update my files on the merchants site manually so there won't be any confusions e.a. a new menu item is added in the header.
Pro: They checkout on a page that's branded as the client and it takes up the full page. It might provide a better sense of security as apposed to option B.
Con: May involve some manual maintenance to keep the appearance of the site consistent.
Option B: When the modal window displays and they click on checkout, a new window/pop-up opens up. It shows them everything they need to checkout... name, address, billing info, etc. It would still be branded as the client's checkout system, but you wouldn't see the entire site (header/footer) in that pop-up window.
Pro: No maintenance involved and they'll always see the site in the background and know where they are at. On completion of checkout, they can close the window and are right back where they left of.
Con: It might defer some people from checking out, because you can't really tell where you're entering your credit card info... although it would be branded accordingly. They may also have a pop-up blocker that could prevent the window from opening in the first place.
Does anyone have any experience with this? Are people less likely to checkout from a pop-up window vs. a full page checkout system?
Any feedback much appreciated.
-Ryan
The answer is to brand the Web site and not use a pop-up, even if it requires some manual updating of the headers and footers. The reason being, that from the user's perspective, it can be hard to tell whether this is a pop-up from that site you just clicked "Buy" on or whether this is an ad from that site or another open tab. Furthermore, if you look at what everyone else is doing, you don't ever check out in a pop-up window. Lastly, the moment something pop-up asking for my credit card, I tend to close it, so knowing how I react to those, I answered my own question.
Case closed.
-Ryan