sign up google merchant account - android-pay

I need some advice on setting up merchant account in google.
When I try to set up merchant account, account signing up page shows me an error.
The error code is shown as "An error occurred {"type":"PLATFORM_ERROR", "payload":"0"}"
I've tried to resolve this issue with Google support team, but they keep sending me general information and manual..
Please give me suggestions on this issue. (I already finished developing my commercial application, but can't set the price because of this issue. )
Thanks in advance.

I had the same issue.
What I did to resolve it was to flush the browser cookies, history and cache. After that, I opened a new browser tab and logged in to my Google Wallet account (the one I set up previously to BUY apps on the play store). As I was logging in, I noticed there was some error but it quickly resolved itself - I successfully logged in and could see what I previously bought.
After that, I closed and re-opened my Google Dev Console, and tried to setup a Merchant Account again and it worked.

I experienced the same problem and I finish solved changing my address length, uou can't use more than 64 characters. see https://stackoverflow.com/a/21412790/2359141

clear cache and everything by using ctl+alt+delete
keep only one tab
Select proper product type , I selected Computer software its worked for me
Do sign out and login in wallet google

I found the solution.
You just have to let the VAT number empty during registration, fill it later.
It worked for me.

I got the payload error as well, what resolved my problem was changing my PO Box address to a physical address. Google chat support figured it out.

Related

Instagram: unable to create client in Manage Clients

The problem is that in Manage Clients at https://www.instagram.com/developer/clients/manage/ client was created,
but it became invalid, the id did not work, i.e. instagram disabled it, the inscription was disabled.
We decided to delete the old client and create a new One, but instagram does not register it. The line of consent and the captcha does not issue. Respectively writes 2 errors:
1.Incorrect Captcha. Try again.
2.Error sending: fill in all required fields.
How can this be corrected?
I've had this same issue, and haven't been able to get anywhere with it. The support page for Instagram says to report a bug using the "Report Bug" button on the Developer Dashboard (http://instagram.com/developer/clients/manage/). If you click that button it takes you to a form that asks if you want to report a bug for the old API or new API. If you select the old API it says "we're not taking bug reports for the old API", if you select new API it takes you to Facebook's developer support page. I created a ticket there, and they told me I had to report it through Instagram's support links. WTF?? That's what I did .....
Anyways, the problem is related to a bunch of javascript errors on that client registration page. I first encountered this problem about 3-4 weeks ago, and it's still around. Feels like IG really doesn't give a crap about their developer community ....

Error while retrieving data

I had an app that was working fine with inapp purchase - I still was in test mode but it was fine.
Then I decided to go to production but got issues - in the meantime nI had lost my certificate keys, so I had to use another package name, upload a new app on Google play and use new certificate credentials.
Anyway.
I did the exact same thing with this new app, and I also add the inapp purchase package, but when I launch the app I have this error :
Error while retrieving the informations from the server ([DF-AA-20])
Any idea of why I have this error message ?
I checked the inapp package name several times and it's ok...
What could be the issue ?
I've been trying to solve this for hours...
Thanks for your help.
I was able to solve the issue by doing these steps:
- I copied the public key found in "Services & API" google account and added it in my code
- I published the app in alpha mode and had to wait until it was really "published", and not "pending publishing"
Now it's working fine and I'm able to make test purchases.
But then I deleted the test account and tried to make a real purchase, and I'm having this error:
"Error: Impossible to buy this article"
Does anybody had this issue ?
Thanks

Instagram Api: Client is no longer active

Yesterday, I was doing some test with Instagram API. I want to design a web page where I show the lastest photos in our account (Some like social feed). Today, I'm recieving this error: "The client used for authentication is no longer active.".
Somebody knows if I did some wrong working with your API and How can I do to fix this problem.
Best regards.
Thanks.
I'm running into similar issues. Have not been able to successfully pull anything through the API for over 12 hours.
Check out this link for quick API testing:
http://instagram.com/developer/api-console/
Nothing seems to work.

Can't sign up for Azure - "We were unable to verify your account"

Anyone else have this problem?
I cannot sign up for an Azure account.
On the registration page, it asks for your phone number and wants to confirm it by sending a text or calling you. I only have a Google Voice number, and I always get
We were unable to verify your account
No matter if I choose text or call. There is no way around it. Any help?
EDIT: Other posts have indicated it's a problem when your country isn't listed, but that is not the case here (I'm in the U.S.). Those posts suggest calling "your local Microsoft branch" but how do I find that?
.
After reading the comments above, and calling Microsoft myself, I was told the verification process does not support Google Voice or Skype phone numbers.
The person I spoke with on the pre-sales department of Azure said he could not manually create an account for me or validate my Google Voice number, despite me sending him this question on StackOverflow showing that others had been successful in calling Microsoft as I had.
My solution was to use a friend's number and have him send me the verification code he received. However, it must be within the Azure signup's session timeout period or the code is no good.
I really hope someone at Microsoft sees this and corrects it for future customers.
I wanted to throw in a answer for Republic Wireless users who are having this problem.
I know this doesn't pertain specifically to Republic Wireless, but this is for those users, and should perhaps prove helpful, since this is the 1st result from Google on the error message.
Republic Wireless is a VoIP company, but they still use an underlying sprint phone number to handle calls/texts when you are not under WiFi, here is how to access your underlying phone number so you can get past the Windows Azure registration verification:
Open the Phone app (the standard dialer that comes with the phone).
Dial ##786#.
The number shown for Mobile Number is your Sprint number.
Hit the Back or Home button to dismiss the information screen.
https://community.republicwireless.com/people/carlh/blog/2013/11/20/moto-x-how-to-find-out-your-phones-sprint-number
I faced this exact same error. After trying different solutions, i decided to change my browser from Google Chrome to Microsoft Edge - and i was able to verify my account thereafter

Libspotify: There was an error generating your application key

I have a premium Spotify account and I am trying to generate an application key to use with libspotify. I am doing this using the form here: https://developer.spotify.com/technologies/libspotify/request-key/, but the generation of the key always fails with a message "There was an error generating your application key".
I tried formatting my application name differently (e.g., spaces, no spaces, no dashes, etc), but the outcome is still the same.
Not sure if it's of any relevance, but I am logged in through facebook and my user name on the application form is shown as a number.
Is it possible that there is something wrong with my account ?
Thanks in advance,
-Kal.
I suspect that something is up with the API key registration page. I've filed an internal bug report with the team that maintains that (I work at Spotify), and hopefully it'll be up and running soon! I'll update this answer if it turns out to be something other than that.
Edit: The error was on Spotify's website, everything seems to be working again.

Resources