Can you see if the same address appears multiple times as well in Google Payments: https://payments.google.com/manage/w/0/#addressBook:

It appears a single time in Google Payments. Please see attached screenshot.

Deleted: Screen Shot 2016-09-21 at 09.11.47.png 58.4 KB

	Screen Shot 2016-09-21 at 09.11.47.png 58.4 KB View Download

re: #4, shrike, I believe the Payments component is the correct one. This is related to our integration with Google Payments. 

keviniu: this seems like a sync issue (the same credit card entry appearing multiple times). Is there some way we can diagnose what's happening to chaorenl here? Would a screenshot of chrome://sync-internals/ help?

To see the addresses synced down, you can navigate to chrome://sync-internals/, click on the tab "Sync Node Browser", and then open the folder "Autofill Wallet".  An address item should have a name starting with "Address:".

+jstuppy & jsaul.  This is possibly a known issue.  In addition to shipping addresses at the user level, each credit card is associated with a billing address, and thus there could be multiple addresses synced down for a user with multiple credit cards. While I'm not sure about client side deduping, on the server side, jsaul@ added some deduping logic recently (cl/133222081, which is live in dev channel and will be live in stable late this week).  John/Jared, could you add comment or clarification?

This is fundamentally a problem with addresses from Payments. They are not de-duped. So  unless the address is an *exact* match, a duplicate is created. I agree that we need to solve this problem. I'm working on a proposal for how to address this. The short version of the story is: we should stop consistently syncing down addresses from Payments. It should be a one-time sync, where the addresses become local, and can then be put through de-dupe and merge routines.

> So  unless the address is an *exact* match, a duplicate is created.

But these are indeed exact matches.

I think duplicates with minor variations are kind of okay. It's great if you can get rid of them, but not that bad if you can't. I sometimes get those on the Google Payments UI itself, but I could just de-dupe them manually by editing.

jsaul: Is this obsolete?

jdonnelly: For the purposes of this bug, I believe so.  sebsg@ landed a change in M58 that should convert server addresses to local addresses, allowing for better client-side de-duping and editing.

I'll close this as Obsolete, but feel free to reopen if you encounter it again.