On March 7 (?) PayPal appears to have blocked access to existing Sandbox accounts (accessible through developer.PayPal.com). They require a login using my own paypal live account, then to "import" the existing Sandbox accounts.
But now, instead of having testers log into the Sandbox account, I have to give the credentials to my own live account. Obviously, that won't work.
The suggestion is apparently to create a "throw-away" PayPal account to "host" the existing sandbox accounts. This does not work (error: "Something has gone wrong. Please try again."). This might be because the Sandbox accounts have "already" been imported into the original account (my own live paypal account).
So I either need to "un-import" the accounts, then import them into a throw-away account, or to copy them from the live account to the throwaway account.
Has anyone managed to get through this? Or am I barking up the wrong tree?
(Note: PayPal apparently no longer provides technical support during business hours.)
I have feeling that you are near about, what you want. Actually previously there are separate section of sandbox environment. But now sandbox environment exists into actual account .
Firstly you need to login into your actual account of paypal then you required to import (means setup a new sandbox account in actual account) sandbox account.
Now you can login with your credentials. In my case its just simple but after reading your question its look you do some wrong things somewhere. please ask anything you want in comments or let we chat in chat-rooms.
Related
I'm trying to create a user authentication screen, so I decided to use Firebase.
However, I am facing a problem. Nowadays I have enabled 2 providers, which are:
1- E-mail/Password
2- Google
Enabled providers
I can create users perfectly.
When I create a user with E-mail/password option and use the Gmail address guilherme.nunes#fover.com.br, Firebase creates the user normally.
After using email, I am trying to use the second option of Google provider, using the same email. Now the old user is replaced with the new provider in Firebase.
account created
After this, if I try to login with the first option (E-mail/Password) again, it says that the user does not exist.
I tried disabling the option to have 1 user per account, but then, Firebase creates 2 distinct users.
What I would like, is to link 1 account, with several providers.
Can someone help me, please?
When you enable the option to allow only a single account per email address, Firebase has certain providers that are preferred for certain email domains. Most notably: the Google provider is the preferred provider for #gmail.com addresses.
So in your initial process, you:
Register a user something#gmail.com with a email+password account.
Register a user something#gmail.com with a google account.
In this case, the second registration replaces/overrides the initial account.
What you want to do is link the two accounts/providers as described in the documentation on account linking. With this approach you don't fully register an account in step 2, but instead link the credentials for that second account to the email+password account that was already created for the user.
The documentation has a step-by-step explanation on how to do this. If you're having trouble making this work, post a new question with the minimal, complete/standalone code that reproduces where you got stuck.
I am using Firebase test lab to automate ui test.
Is there any possible way to login my own test account instead of test account ?
It seems that Firebase support custom login but not work for me.
Custom sign-in: If you provide test account credentials, you need to
tell Robo test where to enter them, and also provide those
credentials.
Thanks
If you require a Google account to log in, your only option is to allow Robo to use its own account.
If your app allows some sort of custom username/password login using form fields that you created yourself, then you can arrange for those values to be entered by configuration, as the documentation is saying. This is not going to be a Google account.
I am using PayPal Express Checkout in my project and I am using my Sandbox testing account to test the PayPal in the development environment.
I am using my Business account I get from PayPal website. Now I want to go live,
what should I do before I go live?
Some said that I should ONLY remove sandbox from my PayPal links, it didn't seem to work with me.
Others said that I have to create an app, but then they will give me client-ID and Secret.
Where should I place them?
because sandbox testing accounts gives me three API credentials USER, PWD, & SIGNATURE
from where I can get my live credentials for USER, PWD, & SIGNATURE
Login to this URL with your live PayPal account: https://www.paypal.com/us/cgi-bin/webscr?cmd=_login-api-run
It will drop you directly into the page that displays your username, password, and signature (with little "show" links for each one).
The long way to get there is to login to www.paypal.com, click into your profile, and look for "API Access".
I have created a sandbox account in developer.sandbox.com and in have a buyer account and seller account associated with it.
I am logged in with my sandbox account and when my app(donation form) is redirected to paypal sandbox url, it asks me to signin with a sandbox account.
The same worked a week before but after paypal developer site had an upgrade to BETA version it is causing this problem. Please help.
This has already been answered here (Paypal Sandbox Testing - Change of URL Endpoint?)
Basically you need to clear your cache and cookies and ensure the test merchant account you are using has been imported to the new BETA version. Then generate a fresh token and it should work (just worked for me)
I am using first time Aweber.I am stuck at some point when I used Aweber API.Below are steps to explain my issue:
I created an account on Aweber labs and created application there. I also retrieved
Consumer Key , Application Id and Consumer Secret from there and put in my demo.php .
When I run this file I had a form with login/password:
Please see this below url :
https://auth.aweber.com/1.0/oauth/authorize?oauth_token=Aq2I3AD7yh7wKBGMGs2pALaP
Now my question is which account's user/pass need to write here. I tried with Aweber lab account details which showing "Notice: Invalid credentials - please retry".
Should I go there "https://www.aweber.com/order.htm" and create paid account to fill there.
Please give your suggestions asap.
With Regards
The AWeber docs are mindbogglingly poor. I don't even understand why they have an API: your app and your keys have nothing to do with accessing any user's data. They just prove to AWeber that yes, you are a developer.... but so what? You want to access USER data (e.g. their lists and subscribers), and that requires a paid account that you can access. From everything I can tell, the AWeber API merely lets you recreate the standard login form from https://www.aweber.com/login.htm on your site.
If you can add the oAuth tokens to your code, that would allow you to retrieve data for a given user, but I don't see any examples in the docs of how to do that, or any explanations that "oh yeah, by the way, AWeber handles this completely differently than any other email company out there." So good luck.
You need to log in with your Aweber credentials, not your lab credentials. Also, when you receive your tokens, add them to your code or everyone visiting your form/app will be redirected to that screen because it will be checking for the cookies that Oauth sets and they won't exist.
EDIT: So to be clear,
You need to set the Oauth cookie yourself first via code in your script
You need to execute the code so the cookies get set in your browser
Then you need to look at the values of the cookies to get your accessKey and accessSecret
Then you need to hard code those values into your script:
$account = $aweber->getAccount($accessKey, $accessSecret);
Lastly, do not forget to remove the Ouath cookie setting in your script
In the demo code provided by aweber just after this line:
$account = $aweber->getAccount($_COOKIE['accessToken'],
$_COOKIE['accessTokenSecret']);
you will be able to get account id
$account_id = $account->id;
This will give you the account id of the logged-in user.
This PHP tutorial should make the integration pretty painless:
http://engineering.aweber.com/quick-start-api-script-in-php/