Why can't I enter the expiration date when manually entering a card?

[Spider]

[The title of this thread has been edited from the original: I am trying manually enter a credit card but it won’t allow me to enter the experation year]

Trying to enter a payment manually but when I get to the month and year it won’t allow me to the use in

[#2]

I've moved your post to this thread as it sounds like what you're experiencing is related to the expiration date issue we had our engineers look into, @mdr_moore. Please take a moment to update the Square app on your device(s), and things should starting working as expected for you!

[SWBVA]

Yes, reload Square from the App Store.

[jaunefleur]

I am trying to manually enter visa/debit credit cards and it won't let me. Is there something I need to do to have them accepted?

[Joe]

Hi there, @jaunefleur 👋 Thanks for reaching out to us here on the Seller Community! Happy to have you join us here! So sorry to hear about the trouble taking manually entered transactions. We are here to help!

What specifically us happening when you try and enter a manual transaction? Are you receiving any red colored fields when attempting? Also, what device are you using? In the meantime, take a look at this helpful resource. 

I've gone ahead and merged your post into an existing thread of Sellers who were also looking for information regarding manual card entry trouble. This will make it easier on our side for record keeping.

I will keep an eye out for your reply! 

[jaunefleur]

I am using a square terminal. I am having an issue only with some debit/visa cards that I have to enter manually. I do not get any red colored fields. It just declines it. It does not do it with every debit/visa card I enter manually. It is happening with one persons card regularly though. I call him and he comes in and it reads it just fine on the terminal. It just won't do it manually. It was issued from RDC and I have never had any other problems with that bank.

[JustinC]

Hmm, sounds like an issue with the card since you're able to manually enter other cards. Curious to know if there's some restriction on the card that disallows manually entering the numbers for a purchase. Or the info you're entering could be mismatched. 

Nonetheless, your customer will need to contact their bank to learn more or come in person to purchase since card present transactions work for him using that card. 

@jaunefleur

[jaunefleur]

OK. Thanks for responding. I will call my customer and request he talk to his bank.

[JustinC]

Sounds good! @jaunefleur

[killey78]

Hello, for the last week i have been trying to process some manual credit cards with expiration dates however, the square system is not allowing us to use particular years.  Is there a problem that we are not noticing?

[ashc]

Hey @killey78,

I moved your post to the relevant thread about this issue that we were experiencing last week that now has a fix!

Check out the best answer for more details and please update your app to the latest version to fix this.

[notnow]

We have been using Square for several years. We do swiping and manual entry - yesterday while entering (visa) cc info the info would not proceed to enter the year - called the client to check on the info which i had correct- rebooted the phone- no go-- tried again to day -no go. Have run another manual card today(amex)- did fine, then  tried a different client visa and it would not enter the number 2 in the year 1/24-- it was also the 2 that would not enter in the 1st client (01/21).  there were  2(s) in the  cc numbers preceeding the problems in entering the year.---- Any help would be appreciated.

[AnchorSPFla]

I've had an issue that I cannot seem to find anyone else having, and I don't have access to call the 800 number after I attempt to reach out to the Support Chat Room.

I can currently replicate this issue.

If I try to manually enter a card (I've tried a Visa and a Mastercard)...when it comes to just the expiration MM/YY portion, if I attempt to type in 01 (January), then follow it with a 2 (I was going to type in 24 for 2024), the square won't input the number 2.  It's not similar as if the information is wrong (normally it would turn red or make a 'thump' noise).  I can't find any exact wording that fits this issue description in any other forum threads.  I've already restarted the IPad I'm using and logged out/logged in to the Square app and the same issue still exists.

[ashc]

Hi @AnchorSPFla and welcome to the Community.

I moved your post to the existing thread that was made for this issue.

This fix was implemented in a recent app update so please update your app to the newest version to fix this. 

[JHorn]

Has the expiration date issue been resolved. We are still having the same problem

[FreemanT1]

I didn't get a reply from SQUARE, but it is working for me now.  I deleted the app, shut down my device for 5 minutes, then re-installed it.  I also got a noticeba few weeks ago that square had an update, so I did that update as well.  Good luck!  

[Joe]

Hi there, @FreemanT1! Thanks for reaching back out. Sorry that we missed you in our rounds of replies!

So glad that you got this problem solved. We appreciate you leaving your troubleshooting steps here for others to follow. Let us know if you run into any other issues. We are here to help!

[laurelgravelyn]

My phone will not allow me to enter the expiration date on a transaction.

[isabelle]

Hey @laurelgravelyn-

Have you deleted and reinstalled the Square app? If not, please try doing this, as long as you have no payments pending in offline mode. 

[karlhartman]

I am trying manually enter a credit card but it won’t allow me to enter the expiration year

[nika]

Hi @karlhartman- Have you tried the troubleshooting steps mentioned on this thread?

[girl]

This reply was created from merging an existing thread: how do I add in a card with 2024 expiry

I am adding a new card to the customer profile but can't get it to accept 2024. how do I key it in, tried 04 and 24

[Valentina]

Sorry to hear about the difficulties, @girl. Our engineers have been made aware of this issue, and are currently working on a fix. In the meantime, I've moved your post to this thread where @ashc provided a workaround.