Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Search Support

denyshon is currently working on this problem. Post a reply | View other questions that need attention.

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

two failures (in 6 weeks) of Firefox during online Credit Card payment process

  • 2 replies
  • 0 have this problem
  • 7 views
  • Last reply by rda2

more options

Over the past six weeks I have had two failures of Firefox [running current version 146.0 (aarch64)] in completing CC payment processes -- at least one involved updating an expired car, I can't recall if the other involved such a change or just entering a card.

I am using Firefox on a mac mini M4 Pro running macOS Sequoia 15.7.2 (up to date, fully supported, but not Tahoe the recently released new version of macOS). I am running Firefox with 4 extensions -- 1 Password, Print Friendly, Raindrop.io, and Authenticator. None were being actively used during these incidents.

In both cases when I switched to Safari and opened the sites, I was able to successfully complete the CC changes and payments. So it does not appear to be related to a problem in my internet connection.

My questions are: a) has anyone had a similar experience with Firefox

     -- particularly incidents related to online financial transactions

b) if so, have you found a solution c) regardless, do you have any suggestions about the cause of the problem or changes to try

Otherwise, my experience with Firefox has been excellent and I am very happy with it, but this is obviously a frustrating and time-consuming problem.

I have reported it to Firefox -- the response was that they will look into it but that my next step should to ask "the community" here.

My thanks in advance for any help or suggestions.

Bob

Over the past six weeks I have had two failures of Firefox [running current version 146.0 (aarch64)] in completing CC payment processes -- at least one involved updating an expired car, I can't recall if the other involved such a change or just entering a card. I am using Firefox on a mac mini M4 Pro running macOS Sequoia 15.7.2 (up to date, fully supported, but not Tahoe the recently released new version of macOS). I am running Firefox with 4 extensions -- 1 Password, Print Friendly, Raindrop.io, and Authenticator. None were being actively used during these incidents. In both cases when I switched to Safari and opened the sites, I was able to successfully complete the CC changes and payments. So it does not appear to be related to a problem in my internet connection. My questions are: a) has anyone had a similar experience with Firefox -- particularly incidents related to online financial transactions b) if so, have you found a solution c) regardless, do you have any suggestions about the cause of the problem or changes to try Otherwise, my experience with Firefox has been excellent and I am very happy with it, but this is obviously a frustrating and time-consuming problem. I have reported it to Firefox -- the response was that they will look into it but that my next step should to ask "the community" here. My thanks in advance for any help or suggestions. Bob

All Replies (2)

more options

Hi Bob,

Here are some standard troubleshooting steps that may resolve the issue.

  1. Please check if you have Enhanced Tracking Protection (ETP) enabled. You can do that by clicking the shield Fx89ShieldIcon icon at the left of the address bar.
    • If ETP is enabled, try disabling it.
  2. If the problem is not fixed, try clearing Firefox cache.
  3. If it does not help, also try clearing cookies and data for the website you experience troubles with (warning: you will be logged out on this website).
  4. If it also does not help, try running Firefox in Troubleshoot Mode. If the problem doesn't persist, please follow the steps from this article to troubleshoot further.

Does any of that help?

Also, what do you mean by reporting the issue to Firefox? What exactly did you do? (I'm afraid that can't be done from this website.)

more options

Denys,

Thank you!!! Each of those makes a lot of sense. But given I encountered the problem twice in 6 weeks. That interval would seem to make it more challenging.

Assessing the impact of anything I do *now* is difficult. The cache will refill, so will the cookies and data for many sites, and I assume that stopping ETP for months is probably not recommended. Though I readily acknowledge it is a candidate since it is ON (I didn't know that and had never heard of it ;-)) and brags about blocking "over 1000 trackers since July 2025."

So my question now is do you think if I encountered the problem again

  • would it be worthwhile to implement changes one by one in sequence and see if that had impact.

(I appreciate this is a holiday season and most folks have plans

  • feel free to give me a one line response saying
    • you can't answer the questions
    • you can't answer these questions until after [date]

My would proceed in the sequence you propose

  1. Clearing cache
    • is straightforward and global
  2. Clearing cookies and data for "the website" is trickier
    • the wrinkle in financial actions is that they always
      • start on one site asking for payment
      • and then move to the financial that handles the transaction
    • but since the problem is only apparent at the financial site, and could well represent an interaction involving data passed between the two sites. I would assume it makes sense to clear cookies and data for both concurrently
  3. Troubleshooting mode and (4) beyond
    • I don't know much about those but figure they are progressively more complex

In trying to implement this, I would assume that as I go from 1 to 2 to 3 to 4

  • it would make sense to
    • (a) close all browser windows
    • (b) implement all proceeding actions as well as the next "new"action
      • that is if I do (1) and it doesn't solve the problem
      • then going to (2), means I do both (1) and then (2) and then ...
    • (c) quit Firefox and restart it

Please note that you did not suggest that one of my four extensions would be expected to be involved. If they were I assume it would impact almost any financial site and would be a more widely know problem.

Your suggestions do indeed help. I'm just trying to understand the likely best way to implement investigation of a problem that could involve complex interactions.

Thank you again -- very much.

Bob

Moderator note: This post has been edited to correct the formatting.

Modified by Denys

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.