It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
I'm trying to pay for a purchase with a debit card, but when I click on the payment option in checkout, the option just won't load. I disabled adblockers and script blockers, tried it with two different browsers, but the frame just won't load. Anyone else have this problem?
No posts in this topic were marked as the solution yet. If you can help, add your reply
Tested just now and it works for me.
• Try GOG Galaxy if you still have it installed.
• You can inadvertently recreate a problem in different browsers by using the same add-ons or settings. If you have Firefox, you can type about:profiles into the address bar to create a new profile and launch it in a new window. This gets you a clean setup with default settings (unless you're using certain Linux distributions; double-check your Add-ons Manager in that case)
• Firewalls or similar security software might also be to blame by blocking content from the payment processor.
I just bought a game, a few minutes ago, with my credit card. Maybe try again?
Post edited December 25, 2022 by maxleod
Alright, found the problem. Ad and script blockers have this 'power button', that disables them from blocking addresses. It seems that GOG has decided that it's not enough for them. The blockers have to be literally disabled from running in the browser settings before they allow for the payment option frame to load.

The change has been made in the last few months. Not a good look for GOG, imo.
avatar
nathanielHiggers: Ad and script blockers have this 'power button', that disables them from blocking addresses.
That's supposed to disable blocking on the current site. It doesn't always allow third-party requests. Refer to the add-on developer for support.
Whenever a site is seemingly broken, always test with a clean slate.
avatar
nathanielHiggers: It seems that GOG has decided that it's not enough for them.
GOG isn't to blame and the problem is exactly what I first I suspected: your browser add-ons or settings.
If you use uMatrix, you should disable HTTP referrer spoofing for the gog.com domain.
While investigating further to prepare a detailed bug report, I noticed that an option of uMatrix stayed active despite disabling content filtering on the domain: HTTP referrer spoofing when requests come from third-party websites. By disabling this behaviour for the gog.com domain, everything is back on tracks. I got tricked because I thought whitelisting the domain would disable all of uMatrix behaviours, but I noticed the change by fully disabling the extension instead.
source