Problems with payment through Google Chrome

[William Unruh]

I am having problem s with using Google Chrome on Mageia 8 ( and
earlier). I use Lycamobile in the US as my cell phone provider. HOwever
almost always, if I try to pay (ie fill out all the credit card info
etc) on Chrome and submit it, Lycamobile claims that the transaction
failed. If I then go through the same system using Konqueror or Firefox,
the transaction works fine. I have tried to call my credit card company
to ask why the payment was refused, and thay have no record of the
transaction having been submitteed at all, so it is clear that it is
Lycamobile that was unhappy and not the credit card company.
Has anyone else seen something like this, or have any
idea why one browser could fail to deliver credit card info, while
another works?

[David W. Hodgins]

Post by William Unruh
I am having problem s with using Google Chrome on Mageia 8 ( and
earlier). I use Lycamobile in the US as my cell phone provider. HOwever
almost always, if I try to pay (ie fill out all the credit card info
etc) on Chrome and submit it, Lycamobile claims that the transaction
failed. If I then go through the same system using Konqueror or Firefox,
the transaction works fine. I have tried to call my credit card company
to ask why the payment was refused, and thay have no record of the
transaction having been submitteed at all, so it is clear that it is
Lycamobile that was unhappy and not the credit card company.
Has anyone else seen something like this, or have any
idea why one browser could fail to deliver credit card info, while
another works?

I use chromium-browser-stable, not google chrome with my online banking and test
it with each update before it's released.

Most badly developed websites use features that were specific to internet explorer,
and now microsoft edge.

You may want to try installing and running it on Mageia 8.
https://www.microsoft.com/en-us/edge

I can confirm that apart from a few error messages during install, it does install
and works.

Regards, Dave Hodgins

[William Unruh]

Post by David W. Hodgins

Post by William Unruh
I am having problem s with using Google Chrome on Mageia 8 ( and
earlier). I use Lycamobile in the US as my cell phone provider. HOwever
almost always, if I try to pay (ie fill out all the credit card info
etc) on Chrome and submit it, Lycamobile claims that the transaction
failed. If I then go through the same system using Konqueror or Firefox,
the transaction works fine. I have tried to call my credit card company
to ask why the payment was refused, and thay have no record of the
transaction having been submitteed at all, so it is clear that it is
Lycamobile that was unhappy and not the credit card company.
Has anyone else seen something like this, or have any
idea why one browser could fail to deliver credit card info, while
another works?

I use chromium-browser-stable, not google chrome with my online banking and test
it with each update before it's released.

My online banking works with chrome, and my payment to other web sites
(eg Amazon) works. It is just this one site, Lycamobile, that does not
work, but it does work with Konqueror and Firefox. ( I would rather not
use Internet explorer or edge). I have not tried chromium.

Post by David W. Hodgins
Most badly developed websites use features that were specific to internet explorer,
and now microsoft edge.
You may want to try installing and running it on Mageia 8.
https://www.microsoft.com/en-us/edge
I can confirm that apart from a few error messages during install, it does install
and works.
Regards, Dave Hodgins

[Bit Twister]

Post by William Unruh
I am having problem s with using Google Chrome on Mageia 8 ( and
earlier). I use Lycamobile in the US as my cell phone provider. HOwever
almost always, if I try to pay (ie fill out all the credit card info
etc) on Chrome and submit it, Lycamobile claims that the transaction
failed. If I then go through the same system using Konqueror or Firefox,
the transaction works fine. I have tried to call my credit card company
to ask why the payment was refused, and thay have no record of the
transaction having been submitteed at all, so it is clear that it is
Lycamobile that was unhappy and not the credit card company.
Has anyone else seen something like this, or have any
idea why one browser could fail to deliver credit card info, while
another works?

Not in this case. All though I was surprised to see the results from
locate /chrome | grep -i kernel

I thought it funny that the last two major firefox releases are causing me
to always do a two factor auth. Got with the chase help desk and they
indicated I had to delete cookies on exit as the solution which is
odd since I had always set no cookies and delete upon exit.

I deleted the .mozilla/firefox and no longer had to do two factor auth
but the latest firefox release always requires the two factor auth
yet chrome did not cause the two factor auth.