I am designing a dialog which would allow user to transfer credits from his account to "an object's account". Transfer is only in one direction -- after you confirm transfering credits to an object's account, you can't retrieve them.
Dialog has two buttons showing numbers of credits on both accounts -- user's and object's. When dialog opens, it has focus on middle textfield, where you can enter number of credits to transfer.
While you are changing the number, number of credits on "Your account" changes accordingly to show how much credits you would have after the transfer. You can increase number in the textfield by clicking either the arrow or button below "Object's account". But despite the fact of clicking the button, number on it doesn't change -- only textfield value changes. I didn't want to repeat the information about number of credits being transfered, according to DRY principle.
To be clear, I was inspired in part by Minecraft trading interface (screenshot below) as I wanted the dialog to be similar in look and behaviour (in sensible way) to it.
My question is: Would presented design of dialog be clear and comprehensible for average user? I'm looking forward to comments and suggestions / improvements.