You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
case 400:
thrownewOpenPayU_Exception_Request($message, $message->getStatus().' - '.$statusDesc, $statusCode);
break;
This will also ensure backwards compatibility as the core of: OpenPayu_Exception($message->getStatus().' - '.$statusDesc, $statusCode) is stil built by the parent::__construct call
The text was updated successfully, but these errors were encountered:
When a request towards PayU is made, if invalid, a proper http response message will be returned from payu specifying why the message failed.
The way the response if verified is by throwing an exception if an invalid http status is received.
If the issue was with the request data an OpenPayu_Exception will be thrown:
But the OpenPayuException doesn't receive further the response message which may contain usefull data, therefore losing that data for the final user.
My proposal is that of a new type of exception:
And when building the exception:
This will also ensure backwards compatibility as the core of: OpenPayu_Exception($message->getStatus().' - '.$statusDesc, $statusCode) is stil built by the parent::__construct call
The text was updated successfully, but these errors were encountered: