• Ask the Community

  • 🇬🇧/🇩🇪 Instant Payment to DKB (and others) not working

@Christoph-Green-Frog#59740 As I said before, it must be a pure Sparkassen issue. I tested it with many German and European banks. Everything worked like a charm from and to Bunq. I wonder what has been already done from Sparkassen and Bunq in order to track it back and have a root cause analysis for this problem. Like for example when did the last SCT Inst. from a Bunq account arrive at Sparkasse etc. when and what did Sparkassen change in their IT system and so many more things. But it probably depends way more on Sparkassen, because they have to be supportive and interested into finding the issue for this failure in their system. I personally hope that the investigations are on a really advanced level, but only Bunq knows all the details of what is really happening or has happened exactly behind the doors during the past days. Hopefully this issue will be fixed shortly...it’s really annoying that something that was so useful stopped working and I started to think that it might be not fixed that soon for this or some other reason. We shall see then what will be the next development like.

    @Roeshimi#59616
    Aquiring (phishing) login credentials to online banking should be comparatively easy - as opposed to aquiring transaction authorization through code or other means (de: „TAN-Methode“), as these are usually only valid once/for a limited time, rely on a second factor device etc... And crossborder transfers to foreign accounts will usually be regarded a higher risk factor.

    I can well imagine that
    1. logging in to online banking
    2. entering a (higher-risk) instant transfer
    3. to a foreign account
    3. and then not going through with it but rather canceling, supposedly due to being unable to overcome „TAN“ transaction authorization
    looks much more „suspicious“ of a compromised login than a login followed by a straightforward successful payment.

      @NiB#59875 Sounds reasonable

        Now the Sparkasse (SOLADES1VSS) is also no longer available via SCT Inst (which worked last Monday 21.1. in the evening). DKB (BYLADEM1001) is still not available for SCT Inst from bunq, but is in the meantime available for SCT Inst from Norisbank (NORSDE51XXX).
        Any good news on this bunq? From my point of view it is getting even worse than better.

          @SimonM#60069 Or any news from bunq at all. I like bunq a lot but they are really really lacking in communication when stuff like this happens. Another reason why they should introduce something like a status board where people can see what's going on

            @Roeshimi#60073 I just spoke with someone from my sparkasse (OASP) and she says it's bunqs fault. So I contacted bunq support just a few minutes ago and they say it's the sparkasse's fault.

              @Robert-Silver-Turtle-4265395482#60077 This reminds of the Asterix comics and the search for "Passierschein A38"
              It's strange that bunq support says that it was Sparkasse's fault, when they said a few days earlier that they were still investigating.

                @Elise could you provide an official statement? the users are confused about the situation with instant transfers.

                  @SimonM#60069 Norisbank is associated with Deutsche so could you test if they also have an instant transfer limit between 300 und 500 Euros? Some tried sending > 500 with Deutsche and it rejected. Would be also interesting if the limit also exists for incoming instants at Deutsche and maybe even Norisbank.

                    @jho#60096 totally agree. demanded it already in private conversation with support. I hope if it take even longer bunq will do that.

                      Started an Instant Payment (IP) with 100 EUR yesterday from Berliner Sparkasse to bunq, but it was processed as standard payment. Unfortunately the 100 EUR have not been booked on my bunq account until now, 6:00 pm. This hasn't happened yet. Weird!

                      The other way round from bunq to the Berliner Sparkasse was booked in the early morning on my account Berliner Sparkasse. Weird too!

                      Another Problem:
                      I would like to transfer money from bunq to Hanseatic Bank and I am facing problems like this: As I think that all SEPA transfers are sent initially by bunq as IP? The transfer to Hanseatic Bank fails immediately as they are returned to bunq within a second with the error: "Payment was reverted for technical reasons". Why does this error occur and is it possible to transfer money as standard payment and to select IP just on demand as the Sparkassen for example do this?

                        Für Überweisungen von LBB / Berliner Sparkasse zu bunq kann ich im "Überweisungsformular" kein Kreuz mehr machen bei "Echtzeit Überweisung".

                        IPs von LBB zur DKB sind problemlos auswählbar bzw. möglich. Getestet.

                        Today I tried to make an IP from Berliner Sparkasse to bunq but was not able to select Instant Payment (IP). So I guess, this will no longer be possible for me.

                          @Christoph-Green-Frog#60099 Norisbank to bunq (1000EUR) was denied:

                          An Instant Payment to DKB (higher Amount) was successfull:

                          Which proofs two things: Norisbank (and probably DB also) could send more than 1000,-EUR via SCT Inst. DKB could receive incoming Instants from german bank Norisbank (and maybe DB). And it is not possible to send Instant Payment from Norisbank to bunq (reason could be amount or technical)

                          And at Sparkasse it is no longer possible to select "Echtzeit-Überweisung" if "BUNQ" was recognized in "bei (Kreditinstitut):"-field. Where it is possible if "DEUTSCHE KREDITBANK BERLIN" or "DB PFK (DEUTSCHE BANK PGK)" or "NORISBANK BERLIN"

                            Volksbank Odenwald GENODE51MIC

                            From bunq no problem.

                              @jho#60260 Geht es auch von der Volksbank Odenwald zu bunq? Danke.

                                @Andre-Magenta-Starfish#60266 Weiß ich nicht, war eine Bestellung ;) Sorry

                                  Hab grad bei der Sparkasse Karlsruhe im Support angerufen und gefragt, wo das Problem liegt. Die Dame am Telefon wollte dann die IBAN prüfen, aber die Eingabemaske hat die bunq-IBAN nicht zugelassen (IBAN nicht zugelassen wg. der Buchstaben).
                                  Sie wollte mir dann immer wieder sagen, dass es an der IBAN liegen müsse bzw. dass die Bank dann wohl nicht bei SEPA Instant mitmache. Daraufhin habe ich ihr gesagt, dass das in der Vergangenheit funktioniert hat und nach einem Blick auf mein Konto hat sie mir dann geglaubt.
                                  Aktuell liegt das Problem jetzt bei den Kollegen "vom Online-Banking" und ich solle zurückgerufen werden.
                                  Ich bin gespannt

                                    Leute,

                                    bunq hat hier ja bereits zwei Mal geschrieben, dass sie dran sind. Wenn das eine übergeordnete Sperre ist, dann wird der "einfache" Support bei den "Unterbanken" auch nichts wissen :/

                                    Einfach abwarten, etwas Geduld! :)