Icon request: Swish (payment)

[oscar-b]

What can it be used for?

It's the most popular payment system in Sweden used by ~6 million users (out of ~10 million population).

Example image (optional)

SVG versions can be downloaded here: https://www.getswish.se/sv-press/press-kit/

Icon request checklist

• This is a single icon or matched pair (Ex: lock / unlock)
• The title starts with "Icon request: " and is followed by the requested icon name (Ex: Icon request: magical-unicorn)
• I have searched for existing issues and to the best of my knowledge this is not a duplicate
• I have included at least one example image if it could be helpful (optional)
• The request is for a concrete object (it's harder to make an icon to represent happiness, it's easier to make a smiley face. ☺)

[addemod]

I second this. 👍

[danadalis]

Its 18 months since this was posted and the issue is still open. Hasn’t this been added yet?

[tarreislam]

B U M P

[akScript]

+1

[fostira]

+1

[tarreislam]

I don't get why this should be so hard to implement. What is the requirement to get an icon implemented?!?!

The equivalent of 3.6 billion dollars has been transferred via swish in August 2022.

Sweden have 11 million citizens and 7 million active Swish users. Roughly 63% of our population uses swish as their daily payment method. 90% of swedish business uses swish as an payment option.

[tagliala]

I don't get why this should be so hard to implement. What is the requirement to get an icon implemented?!?!

Hi!

You may be interested in taking a look at our Requesting Icons FAQs, they contain a lot of information about how requests work

Another useful resource is our Icon Leaderboard FAQs

[tarreislam]

Another useful resource is our Icon Leaderboard FAQs

Thanks

[sensibleworld]

So... our backlog of brand requests has reached a point where even we can't pretend we're keeping up. Some of these issues were opened before I had gray hair. And I've had gray hair for a LONG time. On top of that, treating requests as issues has always made it way too hard to see the forest for the trees.

To fix this, we are now managing all brand requests in GitHub Discussions. No more +1s or thumbs-ups needed. There's an upvote system built-in.

We are closing existing brand requests as part of this transition, but we are not saying no to your request.

If this brand request is still relevant for you, please re-open it in Discussions (and feel free to include a link back to this issue):
-> https://github.com/FortAwesome/Font-Awesome/discussions/new?category=brand-requests

And listen. We know this is annoying. If you need to vent, here are some pre-written responses you can use when opening the new discussion:

• Cool cool cool. No worry at all. I love re-requesting a brand that's redesigned three times while this issue was open.
• If an issue closes after seven years and nobody responds, did it ever really exist?
• I see you have chosen violence today. Re-opening per instructions.
• What's next? I have to file a TPS report, too?
• I am filled with the fury of a thousand suns. Why do I have to re-open the discussion? Couldn't you have just bulk converted all of the issues to discussions? What? You couldn't? What do you mean Github removed that feature earlier this year? You'd have to manually click the "convert to discussion" button on thousands of issues, while also ensuring it gets added to the correct category? That's a bunch of bull-phooey.
• No biggie.

[emanuel-lundman]

Discussion opened:
#20999