webcompat
gateway.cashflows.com - site is not usable
URL: https://gateway.cashflows.com
Browser / Version: Firefox 123.0 Operating System: Windows 10 Tested Another Browser: Yes Other
Problem type: Site is not usable Description: Page not loading correctly Steps to Reproduce: Simply, any time I encounter a Cashflows enabled website (it is a payment gateway), I am unable to proceed because there is an error between the retailer I am transferring from at point of 'click to pay' by credit/debit card on transfer to Cashflows to enter the credit/debit card details. Hence, I can never enter the card details to begin the payment process itself, as this page always results in an error.
The error page that comes up is indicated as Cashflows' error page, on gateway.cashflows.com. It does not provide any useful information, nor error codes, about why the error occurred other than saying that "The payment could not be found" (obviously due to the triggered error), but it is definitely Cashflows branded on the above mentioned URL.
This only ever happens with Cashflows, all other purchases on other websites with different payment gateways proceed normally.
This is becoming more and more frustrating for me as Cashflows expands across more websites over time. As many sites use a single credit/debit card payment merchant, Cashflows has an increasingly negative impact on my ability to complete transactions, especially as I have to rely on the Internet for all of my shopping. Effectively, I am finding myself Increasingly blocked from shopping online, with obvious detriment to myself.
Cashflows has taken little interest in this when I have let them know this is a problem, and the retailers concerned are siding with Cashflows by and large, since they have little technical knowledge anyway, give or take a few who have attempted to communicate with Cashflows but have then taken Cashflows' line or gone silent on me, all leaving me completely in limbo. Again, this is extremely frustrating, as I am powerless to do anything.
I have checked all of my Firefox settings, extensions (including removing all of them), as well as starting with a clean fresh profile with no extensions or anything added, and everything set to default in the settings. Nothing resolved this issue within Firefox, not even in its most basic default setup.
I have also installed the Brave Browser to test whether it would work in a Chrome environment. With Brave, I am able to complete those same transactions. Like a ping-pong ball however, Cashflows would have me believe that it is a problem with Firefox, rather than their setup between themselves and the retailers. As stated before, I am able to transact with other non-Cashflows enabled websites without issue. This problem is unique to Cashflows.
I'm using Windows 10 with the current version of Firefox, although this has been occurring with multiple iterations of Firefox for more than a year now.
Please investigate and fix this problem, or notify me what the issue is that needs to be forwarded to Cashflows to get this fixed, as it would be unacceptable for any payment merchant/service to continue in this way. Payments are essential services; they should work across all browsers regardless.
I rely on Firefox for security and privacy. I do not appreciate being frequently told/stonewalled by organisations with profit interests in my data to switch to other less secure browsers, not even to your closer competitors. Browser choice is, and should be, a personal choice.
Sincerely therefore, I hope Firefox will take this issue very seriously and with the high degree of urgency it deserves.
Thank you
Browser Configuration
- None
From webcompat.com with ❤️
Thanks for the report @tigersof . Do you have an example of an site with Cashflow enabled in the payment process, that fails? Also, does it happen on Chrome?
[qa_12/2024]
Example website: https://supercompetitions247.co.uk
I don’t know about Chrome. It doesn’t happen in Brave (Chromium), if that helps.
On 18 Mar 2024, at 12:32, softvision-raul-bucata @.***> wrote:
Thanks for the report @tigersof https://github.com/tigersof . Do you have an example of an site with Cashflow enabled in the payment process, that fails? Also, does it happen on Chrome?
[qa_12/2024]
— Reply to this email directly, view it on GitHub https://github.com/webcompat/web-bugs/issues/134733#issuecomment-2003790408, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATXNUJEVMFR5OJH2IHAWGN3YY3NGDAVCNFSM6AAAAABEZSPQBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBTG44TANBQHA. You are receiving this because you were mentioned.
@tigersof Thanks for the update. A valid payment method is needed, unfortunately. Does it happen in Firefox Nightly, latest version?
[inv_12/2024]
Yes, developer edition 125, it works. Still doesn’t work with latest Firefox version 124.
On 22 Mar 2024, at 12:41, softvision-raul-bucata @.***> wrote:
@tigersof https://github.com/tigersof Thanks for the update. A valid payment method is needed, unfortunately. Does it happen in Firefox Nightly, latest version?
[inv_12/2024]
— Reply to this email directly, view it on GitHub https://github.com/webcompat/web-bugs/issues/134733#issuecomment-2015015814, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATXNUJG32EHWPO5QQPV3G43YZQRGXAVCNFSM6AAAAABEZSPQBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVGAYTKOBRGQ. You are receiving this because you were mentioned.
I don’t use Nightly Edition, or is that the same as Developer Edition?! Technically, I don’t use this either, it just happens to also be installed. I use regular Firefox that most consumer users would use and therefore need it to work properly there.
On 22 Mar 2024, at 12:41, softvision-raul-bucata @.***> wrote:
@tigersof https://github.com/tigersof Thanks for the update. A valid payment method is needed, unfortunately. Does it happen in Firefox Nightly, latest version?
[inv_12/2024]
— Reply to this email directly, view it on GitHub https://github.com/webcompat/web-bugs/issues/134733#issuecomment-2015015814, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATXNUJG32EHWPO5QQPV3G43YZQRGXAVCNFSM6AAAAABEZSPQBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVGAYTKOBRGQ. You are receiving this because you were mentioned.
Nightly receives more updates. Try this for both Nightly and Release:
What I would do usually to test this kind of issue, is:
- Type
about:profilesin the url bar. - Choose
Create a new profile. - Call it
deletemeor anything you please. - Then start it. (this way you will be sure that nothing is interfering, no ghost caching etc.)- make sure account sync is not performed, as the extensions will be imported in the new profile.
- Test.
Note: You can return to your old profile at any given time by accessing "about:profiles" in the address bar
[inv_13/2024]
Hi, thanks for your help. I’m not a developer, have no idea what Nightly is and am up to capacity with installations at the minute. When I used the Developer Edition, because it happens to be loaded on my machine, it required a brand new profile as none was set up when I tested whether the site works in it (and the URL does work here). Is that not enough?
I don’t use synch function, it was a brand new base profile, no settings changed or extensions added whatsoever. I also don’t use the blue-iconed Developer version for general browsing. Instead, I use the standard orange-iconed Firefox for that, which is the one that doesn’t work with this URL.
On 28 Mar 2024, at 13:57, softvision-raul-bucata @.***> wrote:
Nightly receives more updates. Try this for both Nightly and Release:
What I would do usually to test this kind of issue, is:
Type about:profiles in the url bar. Choose Create a new profile. Call it deleteme or anything you please. Then start it. (this way you will be sure that nothing is interfering, no ghost caching etc.)- make sure account sync is not performed, as the extensions will be imported in the new profile. Test. Note: You can return to your old profile at any given time by accessing "about:profiles" in the address bar
[inv_13/2024]
— Reply to this email directly, view it on GitHub https://github.com/webcompat/web-bugs/issues/134733#issuecomment-2025250664, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATXNUJG2CSTOLLSMD5U2EU3Y2QHSZAVCNFSM6AAAAABEZSPQBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRVGI2TANRWGQ. You are receiving this because you were mentioned.
That might have shed some extra light on the issue, but if you state that dev edition works, the next release update will also work (dev edition is one step ahead of release, basically).
For this project, we perform testing on Firefox Nightly's latest version. Since the issue is not reproducible using Firefox Nightly or Dev edition, this will be closed as "Won't fix" We apologize for the inconvenience, but if the issue only occurs on the Release/Beta version most likely it will be fixed on the next Release version. Please re-open the issue or comment on this issue if the issue is still reproducible on the next release and we will gladly investigate this further.
Please keep us posted.
Closing this as WONTFIX
[inv_13/2024]
ok, thanks.
On 28 Mar 2024, at 14:55, softvision-raul-bucata @.***> wrote:
That might have shed some extra light on the issue, but if you state that dev edition works, the next release update will also work (dev edition is one step ahead of release, basically).
For this project, we perform testing on Firefox Nightly's latest version. Since the issue is not reproducible using Firefox Nightly or Dev edition, this will be closed as "Won't fix" We apologize for the inconvenience, but if the issue only occurs on the Release/Beta version most likely it will be fixed on the next Release version. Please re-open the issue or comment on this issue if the issue is still reproducible on the next release and we will gladly investigate this further.
Please keep us posted.
Closing this as WONTFIX
[inv_13/2024]
— Reply to this email directly, view it on GitHub https://github.com/webcompat/web-bugs/issues/134733#issuecomment-2025427813, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATXNUJCON7XMJOVV7HMMHD3Y2QONLAVCNFSM6AAAAABEZSPQBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRVGQZDOOBRGM. You are receiving this because you were mentioned.