Quote from: nons on June 29, 2025, 07:51:08 AM

Quote from: Mahdirakib on June 29, 2025, 06:59:48 AM

[...]

Quote from: bitbollo on June 29, 2025, 06:36:40 AM

mmm I would say OP that sounds like a silly excuse... because these funds have been sent to a key that is in THEIR ownership not in the ownership of another entity! Yes this jey "belong to another account" but the coins area still on a wallet/key that they own the key.

No, you are missing the key point here. It was a deposit address of another user. Therefore, the funds have been credited to the account of that user. Most probably, the user has already played with the funds and made a withdrawal or lost it. Stake isn't liable in that case. The situation is like sending funds to a wrong address.

The irony is them telling me to be more careful with my transactions 😡
I sent their answer to Bitpanda support, let’s see if they fix their big mistake…

Hmm... I finally gave this thread a read today as I need to jot it to my to-do list what to write on my next list update, and I am at the same agreement with at least four other overseers here. It's on Bitpanda's responsibility.

But... if I may get a broader context, do bitpanda at least explain why the transaction bounced? I am aware that you've answered to Shasan and Mahdirakib that they said it's related to MiCAR, but did they explain exactly why it bounced? Because:

And given this is [I think we are all come into same agreement here] bitpanda's mistake, I can't and won't add this to Stake's entry on my list.