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
The problem arises only for the Complete/Reverse payments steps because they use the PHP file_get_contents function to perform the web request, while the Authorize functionality is performed by the user browser, which will fallback and complete the certificate chain in such cases.
A way to disable SSL verification for test gateway only is needed to allow new users to perform the onboarding technical tests and promote their project into production payment gateway.
This could be achieved by conditionally (only in DEBUG/TEST modes) adding the following parameters on the request() function stream context options for the CompletionRequest and ReversalRequest classes:
https://www.ssllabs.com/ssltest/analyze.html?d=ecomt.victoriabank.md&latest
Compare to the production gateway configuration: https://www.ssllabs.com/ssltest/analyze.html?d=egateway.victoriabank.md&latest
The problem arises only for the Complete/Reverse payments steps because they use the PHP
file_get_contents
function to perform the web request, while the Authorize functionality is performed by the user browser, which will fallback and complete the certificate chain in such cases.A way to disable SSL verification for test gateway only is needed to allow new users to perform the onboarding technical tests and promote their project into production payment gateway.
This could be achieved by conditionally (only in DEBUG/TEST modes) adding the following parameters on the
request()
function stream context options for theCompletionRequest
andReversalRequest
classes:The text was updated successfully, but these errors were encountered: