The official response to this seems to ignore that it doesn't actually solve the problem. Even if I had put the wrong number in the initial field, when I couldn't paste from my password manager into the confirmation field I just typed the numbers from the first field. I didn't go back to anywhere to validate the numbers, all this did was make me frustrated not

"some customers..." how many? 0.3%? This peaves me like password character requirements.

I understand that disabling paste in the confirmation field is meant to prevent users from pasting what might be wrong info from the initial field. However, this is an annoyance to those of us who are pasting from an accurate source, like a password manager, as others have pointed out.

I wonder if you can use some machine learning like CAPTCHA to detect when the user is pasting from the initial field, and show an alert to say, "Are you sure you want to do that?"

YES. Not having this feature is abslut stupid.

Yes quickbooks response is remarkably stupid. I store my information in a password manager and you are preventing me from using a known good source. Fun fact! I am reading the number I just pasted into the first field to "confirm" it. All this does is make the user experience worse and increases the probability for error.

Stop making it harder to give people money.

> "Thank you for the feedback! We’re restricting the copy-pasting due to numerous pasting errors. Some customers are entering the first field incorrectly and copy-pasting it."

This is, without a doubt, the stupidest line of reasoning I've ever had the misfortune of hearing.

Everybody else gets by letting people copy/paste things - you know, to prevent errors - so I'm sure QuickBooks can manage to do the same unless you are all really, truly incompetent.

This response from Quickbooks is really quite daft, and doesn't seem to have taken the reasoning provided by the original poster at all.

If you really want to try to protect users from themselves in this regard using methods that deliberately break useful native functions like copy-paste, then short-circuit the 'copy' action from both text fields rather than the 'paste' action. If the concern is that users are picking an incorrectly entered account number into the clipboard from these fields, then _prevent that action_.

The result of your solution as deployed presently is that people copying routing and account numbers straight from their bank's web portal or app - which is a great way to enter these numbers vs manual entry - now have to enter a large number manually anyway. Meanwhile, users who are prone to errors when entering their account number in the first field anyway will likely use this field to reference when entering it again into the confirmation field, simplying duplicating their error because it's on the same screen, rather than referring back to something that's correct.

You're not helping anybody with this solution!

Thank you for the feedback! We’re restricting the copy-pasting due to numerous pasting errors. Some customers are entering the first field incorrectly and copy-pasting it.