• Ideas

  • IDEA: Preventing “Shared request expired” confusion

Add this simple selection menu when requesting through a Shared link 🔗

Much more user friendly than manually canceling every Shared request after the first (and only) payment, while still cater to those who want to share a request to a group of people 🙌

    @Meester-Kevin#49427 Hi 👋

    Thanks for your suggestion! I know it can confuse a lot of people when they receive a expired notification after a month, it even gets me confused sometimes when I forget to close the request.

    So I think this could be a great little improvement, you’ve got my vote! Nice mock-up btw! 🌈👍

      @WJanson#49442 Thanks! 👍

      Such a QoL improvement deserves a little effort put into the mock-up ✌️😄

        @Meester-Kevin#49427 Really like this idea💡
        It’s simple but at the same time super useful.

        I would like to add a suggestion to include a third option: valid for x payments (so when you expect 3 people paying the request auto expires directly when 3 payments are done. Possibly it could even trigger a short message in the event stream that “everyone payed, request is done”)

          Currently those notifications are really useless indeed, no idea what it was I did one month ago... So this can definitely be made better.

            @Roel-Turquoise-Panda#50401 Thanks! ✌️

            I’ve also thought about those additional options, just like adding the option to set the expiration date.

            Unfortunately it can get messy very fast. As simple as those options in the mock up are, if you add an option with a variable input (like setting the number of requests), you need extra fields and won’t be a simple selection menu anymore.

              2 months later

              Ik zou deze feature uitbreiden met een optie zoals het nu bij bijvoorbeeld Tikkie werkt:
              Je vraagt geeft een totaalbedrag in en geeft aan met hoeveel mensen je dit bedrag wil delen. Is het teruggevraagde bedrag bereikt dan sluit automatisch dit verzoek.

                @pvdvossen#68640 Zowel dit als het originele verzoek zouden mooi zijn. Ik word knettergek van die "Request gesloten" onzin. Je bent verplicht om voor elke request terug de app in te gaan, de request te openen en deze handmatig te sluiten als je die vervelende meldingen niet wilt. Het zou zeker fijn zijn als dit voorkomen kan worden. :)

                  I totally agree with this feature request. Its indeed very confusing and you have to check if the request was payed. At least you can see this very quickly but still this can definitly be improved.

                    4 years later

                    Imo the most confusing part is that the original payment that happened a month ago, is no longer listed there. It has now moved up with the expire notification to the moment of the expiration. Bunq is actually rewriting the transaction history by moving payments up in your transaction overview.

                      @Arjen-Indigo-Bear#278934 The transaction overview inside the apps might sometimes enhance the ordering in these special cases to make certain things clearer, like which transactions belong together. But the PDF and CSV exports of your account should list everything strictly chronologically in case you ever need to dig deeper. The apps are for everyday use, and exports for archival / research purposes.

                        9 months later

                        I'm just here to keep this thread alive. It astonishes me that this was suggested 5,5 years (!?) ago and nothing has changed.

                        I like other before me have, would like to suggest a tab or widget where these request are gathered so you have them in one overvieuw. Then the manual part that need to be done is bearable. Requesting layments is just confusing and tedious. Shared payments aren't connected properly, and when payed you get a 'request expired' notification.

                        Dear Bunq, it is time this problem is being adressed :)

                          Write a Reply...