Should adding payment tags be allowed?

[PavLL]

It's been deprecated to add contact info such as websites to items for the reason that this info should rather be added to the brand's Wikidata page.

But what about payment:* tags? There exists the "payment types accepted" attribute on Wikidata and that should be enough instead of spamming 20 payment tags on every single object with that brand. It's even worse than contact tags.

[bhousel]

Yes, we mostly don't add payment:* tags to items, for the reasons that you said. If you found some tags like this in NSI that you think don't belong, please let us know. Or if you got here because it's being discussed somewhere else, please link to the discussion so we can follow along.

We discussed here a bit
#6701

Here's an example of the sort of thing we are hoping to avoid
#10196

In summary

• If the tag is true everywhere then it doesn't really add any value and just bothers users with "upgrade" warnings.
  (e.g. adding payment:credit_cards=yes to restaurant brands might be technically correct, but not helpful)
• If the tag isn't true everywhere and needs to be surveyed by users, then it doesn't belong in NSI anyway.

I think we might allow few exceptions for some kinds of features where the payment types are interesting , for example I seem to remember that we might set payment tags on some toll collection devices or ticket vending machines.