PROBLEM WITH PAYMENT API FOR FILING A RETURN - NOT ACCEPTING EXP MONTHS 9-12 CREDIT CARD ENTRY

[Nestle7277]

The payment API has three tabs, first is "Billing Address" for basic stuff. The second tab is for "Payment info" and this one is not working properly. - Name on card* works fine - Card number* works fine - Expiration month* has problems Only months 01-08 can be selected. Months 09-12 CAN NOT BE SELECTED. Therefore people can NOT pay for the upload processing fees for Turbotax and returns will not be processed. THIS IS CRITICAL TO BUSINESS OPERATIONS. It may be someone has HACKED your PAYMENT API. Get back to me when you have updated your software.

[cascadia1]

This is happening again this year (2025 return). Exact same problem and nobody could help when I called. 

[CatinaT1 · Accepted solution]

Here are the three things that other users have used to bypass this specific error:

Strangely, this often affects the selection but not the scrolling.

1. Click into the Month dropdown box.
2. Do not try to click on 09–12 with your mouse cursor.
3. Instead, use the physical scroll wheel on your mouse (or swipe with two fingers on a laptop trackpad) to scroll down to the correct month.
4. Once the correct month is highlighted, press the Enter key on your keyboard rather than clicking it.

The mouse click is often what triggers the the error in the field.

1. Click into the Credit Card Number field.
2. Use the Tab key on your keyboard to jump to the Expiration Month field.
3. Immediately type the two digits (e.g., 11) without using your mouse at all.
4. Tab again to move to the Year field.

If you are using the online version, this is often caused by a "script error" in your browser's cached data.

1. Open a New Incognito Window.
2. Log back into TurboTax and go straight to the payment screen.
3. Often, the "fresh" session in Incognito will allow the dropdown to function properly.

[cascadia1]

Thank you so much!!  It worked!  I really appreciate you taking the time and for all your help.  Filing is done! 😃

[Rnp777tx]

I have tried all of these options here with no success as the program won't even let me scroll with my mousepad in the month box, nor let me quickly type "11" after tabbing from the card number. I am using the desktop version. I was also online with tech support yesterday, 01/30/26, for nearly 3 hours with no resolution and they made it even worse by deleting my download out of my advantage account. My tech support person even got on with her Lead.  Now, after seeing here that this is an ongoing problem, FOR YEARS, another question I have is why didn't my tech support and her Lead know that this was even a problem. Supposedly, they had never seen it before! I have updated my computer, cleared cashe, cookies, etc etc with no good results. 

Got any other ideas besides purchasing a completely different tax program?

[CatinaT1]

@Rnp777tx  Can you tell us what operating system you are using? Windows 10, 11, etc.

[Rnp777tx]

I am using windows 11. This, year after year, continuing problem is absolutely ridiculous. Luckily for me, I have other credit cards with exp dates within the first 9 months of the year so I got my taxes efiled but this problem that TurboTax continually ignores has made me lose faith in them. 

[cefoster]

I'm having the same issue - the fixes using tabbing, scrolling, and the enter button have not worked after multiple tries.  I am using windows 11. I have no other option for a credit card using an expiration date of August or earlier.  This issue has never occurred for me before and I've used Turbo Tax for many years.  Please provide an alternate solution to those you listed in your response or preferably fix the problem on your end.

[CatinaT1]

Other than what I have already suggested, I am not aware of any other work around. We are currently investigating the issue and will provide updates as soon as possible.

[Nestle7277]

Your group has had this problem reported in Community since October 12, 2025. 
This is a problem with CACHE or the implementation of the PAYMENT API based on what was previously reported by me and others over the life of this problem.  In general the windows version does not matter and your question becomes a fishing exercise in the delay of gettiing a resolution with working with the windows platform development group.  You really need to chase this.  How do you know this is not an open hack in the PAYMENT API?  You don't!  This really should get prioritized (October 12, 2025 right?)