Hello Everyone,
We are sorry for the late reply to this thread. HTTP 500 / internal errors are thrown when:
- Request sent to us cause an unexpected error
- Requests sent to us, hit a problem on our end.
On sandbox, that is more common, sadly, as the sandbox is also our sandbox.
By default, for example in live, when a 500er is thrown, we use asynchronous flows to still process the request and usually it completes later on (later is defined as seconds). However the initial response to the merchant account is that 500er. Best then is checking via GET calls, a few seconds later, if the action was completed such as is the transaction now completed, refunded etc.
You can use unique request headers in your API calls, that way no double refund or execute can occur.
As for one merchant, in this thread, the issue was caused by an unconfirmed email address, when the account was created via the developer portal, the email was not confirmed which then let to the 500er. It should have thrown a different, readable error, but did not due to something on our end. But that issue is resolved.
If you have 500er on a constant base, such as my example mentioned here, then it is advised to contact us via a ticket and to provide the API caller sandbox account as well as the debug ID, the latter should not be older than a week. We can then take a closer look with you.
I hope this helps.
Stefan
... View more