CORS issue

Describe the bug A CORS issue is present with the log API while this is not a breaking bug, it is ugly and would cause strict front-end testing to fail.

This is using "@adyen/adyen-web": "^4.2.1"

To Reproduce Steps to reproduce the behavior:

1. Use the adyen-web UMD module

Expected behavior No errors should be produced by using our module.

Screenshots

Desktop (please complete the following information):

• OS: all
• Browser: all
• Version: 4.2.1

Smartphone (please complete the following information):

• Device: all
• OS: all
• Browser: all

[RIAEvangelist]

The docs stuff and CA will end up being brought inhouse to the DevEX / Devadvocacy teams.

For the CORS issue itself though, a nice way to help devs with this would be a

try{
    fetch(...)
}catch(e){
    console.log(...info to cors fix..., link);
}

Perhaps even a global fetch interface for the class that wrapped all calls in a single handler to document errors. We can use fancy logs to include actual links to make solutions very dev-friendly to reduce the overhead on docs and customer support for this sort of issue.

[nickcaballero]

Agreed, I ran into this same issue recently and happened to realize that the origin was missing.