Steps to reproduce
Norwegian online stores uses the Norwegian standard for authentication, called BankID.
BankID is used as authentication, verifying the customers ID and adding an extra security layer while using debit and credit cards online.
Authenticating debit and credit cards on different online stores with BankID in Edge failes and returns an error, however in Internet Explorer it works fine.
Steps to reproduce:
- Go ta a Norwegian online-store
- Select merchandise
- Check out
- Enter debit or credit card information
- Sign with BankID
Last step failes, returning the BankID error code BID-5000 (a general error code which may include communcation error towards merchant)
Comments and activity
Thanks for filing this bug! Unfortunately, in it’s currently form, it’s not actionable since we do not have a BankID to test with. While we look into seeing if we can find someone on the team with one, would you mind providing us with a bit more information such as the websites that you’ve tried checking out on? Thanks!
- Microsoft Edge Team
Changed Assigned To to “Steven K.”
The problem is not solved. BankID can successfully log into the Bank, but the payment on websites throws the code “BID-5000” with message. "Try again later, if the problem persist contact your bankID provider". The providers in my case "DNB", “Scandiabanken” and “Norwegian” only has one solution. Switch to another browser. In Internet Explorer, chrome and Firefox the Signing with BankID works without issues.
You are welcome to contact me for further testing.
Also, a new release from BankID (v. 2.1) is underway and will be deployed very soon.
I will stay in contact with our customer support and give an update when the new BankID release is in production.
Thanks for the update!
I’ll wait for now and hopefully it works out with the next update.
- Microsoft Edge Team
Changed Status to “Needs root cause”
Changed Status from “Needs root cause”
Hi everyone! Unfortunately, we have not been able to secure a BankID to test this scenario with. Are folks on this thread able to confirm if this is still an issue on the most recent April update? We’d love to get to the bottom of this if so. Thanks in advance!