not at all! bugs happen, we're human. that's what qa is for ... oh wait!
no, as i also explained it's the recurrence of these sort of bugs that hints at incompetence. this is very basic stuff, so i'm not implying devs are complete idiots, they are actually quite capable, it's just that they collectively (architects, implementors and qa experts) fail to ensure very basic universal software requirements and practices. that's ... incompetence.
i've not implied anything of the sort. also, building your own engine doesn't excuse broken transactions. how about your bank tells you that next time you have to move money around and it gets lost?
you seem to take this very emotionally. be my guest, but i'm being quite objective and neutral. i could comb the bug reports and patch notes and fish out all transaction related bugs for you, the ones i've been reading for years (with a mix of giggles and facepalms) so you get a picture but ... i'm not going to do that, i hope you understand. :x
i'll give you one thing: from the description it is not really clear if this particular bug is a mishandled transaction, probably not. it could be bad ui component design or just a refresh bug, or that the 'transfer' option was just mashed together by a junior ina hurry who didn't really understand the ui logic. could be anything. still, it's broadly in the same category.
so other games are similarly buggy? well, then from a software engineering viewpoint they're incompetent too! what do you want me to say?