Troubleshooting: Difference between revisions
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
Before contacting support, please run through the list of common pitfalls. This will save both you and us a lot of time. Here we go with the list. | Before contacting support, please run through the list of common pitfalls. This will save both you and us a lot of time. Here we go with the list. | ||
==Authentication error upon request== | |||
==Mixing up sandbox and live accounts == | ==Mixing up sandbox and live accounts == | ||
Revision as of 11:49, 6 February 2017
Troubleshooting - list of common pitfalls
Before contacting support, please run through the list of common pitfalls. This will save both you and us a lot of time. Here we go with the list.
Authentication error upon request
Mixing up sandbox and live accounts
It is very easy to mix up Live and Sandbox environments. Since the two systems are totally separated, you can have an account with the same e-mail address in both systems. Double check, if you can not log on.
Forgot to update POSKey to live
It is very easy to mix up Live and Sandbox environments. A very common mistake is to not update the POSKey to the Live server when going live. Same goes to URL-s.
Shop not approved
Log on to Barion Web App and check if your shop is approved and open. The Sandbox server does it automatically, but the Live requires human approval.
Authentication error upon request
If you have managed to avoid all problems mentioned above, yet you still receive an API response showing 'Authentication error', check your request JSON for errors. Broken multibyte strings or unescaped special characters can render the JSON unparseable, which prevents the Barion API from identifying your POSKey, resulting in an authentication error.