I've built an extension to Chrome and have loaded it into the developer dashboard, but I get a message that:

A one-time developer registration fee of US$5.00 is required to verify your account and publish items.

When I click Learn More, it takes me to this page. But when I click on PayNow, nothing happens. It just redirects back to the dashboard with the following status:

This publisher is not linked to a Google Wallet account.

This article talks more about how to pay the developer registration fee, but doesn't offer much by way of advice.

I have a Google Wallet account, but can't figure out how to link it with my new developer account.

The same issue was posted recently on Google Chrome Forum and I've added it to the Chromium-Extensions Group, but neither have generated answers yet

  • 1
    Oh hi there, I'm the person who posted that, it's a small world! From what I can tell, there's a small error in Google's JavaScript that prevents the payment form from popping up correctly (there's an undefined variable). Of course all the JavaScript has been minimized, so there's no realistic way to go in and fix it yourself. If anyone has a solution, I'd really appreciated it! Jul 17, 2013 at 16:44
  • 1
    Hey there! I imagine some change to Google Wallet has broken the way their developer dashboard works and they just haven't noticed yet. I hope it's fixed soon. I'll post it here if I find anything helpful.
    – KyleMit
    Jul 17, 2013 at 17:43
  • 1
    @JeffreyYasskin, chrome.google.com/webstore/developer/dashboard
    – omab
    Jul 17, 2013 at 21:42
  • 1
    @KyleMit: You should post an answer rather than putting that information in your question.
    – ale
    Jul 18, 2013 at 18:23
  • 1
    @AlEverett, I guess I view the updated I posted as more of an ongoing process. I'll conclude with an answer when the issue is resolved. If I saw this question was answered, I'd expect a resolution, but as of now, there isn't one.
    – KyleMit
    Jul 18, 2013 at 18:30

1 Answer 1


Update: 7/18/13

Div from Google has posted an update on the Google Products Forum:

Hi folks:

Thanks so much for your reports -- we definitely want you to get to publishing! We've been working with the team here and it looks like a fix is on its way (hurray). No exact timeline, but it should be here soon.

More from me if I receive any updates. Thanks again for letting us know!

Cheers, Div

Update: 7/18/13

Joe Marini from Google has posted the following update on the Chrome Extensions Group

If you are having issues paying the fee, please send me a message.

Update: 7/19/13

Div from Google has posted the following update

Hi all! Update from me as promised! The fix has been identified -- woohoo! It should roll out fairly soon. I'll be sure to update one more time (and will stop filling your inboxes :) once it's fully live. Thanks for your patience on this.

Update: 7/19/13

Joe Marini from Google has posted the following update on the Chrome Extensions Group

The fix has been checked in and will go live with the next CWS release on Monday or Tuesday.

Update: 7/23/13 - RESOLVED

Users have posted on the forum that the update is working correctly

  • It is happening right now. Anyone same as me?
    – Dummy
    Aug 16, 2016 at 17:56

Not the answer you're looking for? Browse other questions tagged or ask your own question.