thread Re: Phone number paste with CTRL+V not working, weird behavior on editing in Payments Troubleshooting

Phone number paste with CTRL+V not working, weird behavior on editing

Velo — Sun, 21 Sep 2025 17:04:57 GMT

When editing a customer, it is not possible to possible to paste a phone number using the keyboard. It only works using the context menu (right+click - Paste).

The behaviour has been confirmed on Windows, Linux, using Firefox or Chrome.

Also, when correcting the phone number (imagine the number is 123-456-7890), if you place the cursor before the 4, you cannot use the Delete key to delete it. If you use Backspace to erase the 3, the cursor is sent at the end. If you place the cursor somewhere before the end of the number, typing a number will also send the cursor at the end.

CTRL+Z also doesn't work. If you select the whole number, you can't use Delete. You can't use CTRL+A to select the text in the field

Overall, this field has some pretty weird behaviors and seems very intense with auto-formatting, to the point of generating bugs.

Re: Phone number paste with CTRL+V not working, weird behavior on editing

JustinC — Wed, 12 May 2021 18:15:58 GMT

Sounds like a change in your keyboard functionality or accessibility settings. Is this happening on any other site, like Facebook or Twitter when creating a post, for instance. Try opening a Microsoft word doc to test there?

@Velo

Re: Phone number paste with CTRL+V not working, weird behavior on editing

Velo — Wed, 12 May 2021 18:25:23 GMT

Hello!
It's not. None of the 4 computers/browsers I worked with ever had keyboard functionnality or accessiblity settings touched.

Copy pasting anything else from anywhere to anywhere works just fine.

Re: Phone number paste with CTRL+V not working, weird behavior on editing

JustinC — Wed, 12 May 2021 19:06:39 GMT

Hmm, strange. I just tested on my demo account and I'm running into the same issue. Reach out to our CS Team so they can create a ticket for your account. Our Engineers will need to dig deeper and deploy a fix for you.

@Velo