I am using Opencart 2.3 version and installed an extension of Authorize.net AIM. I configured the API details and Facing getting an error of (Test Mode) The supplied currency code is either invalid, not supported, not allowed for this merchant or doesn't have an exchange rate.
Here is the screenshot of settings I configured
Can anyone help me where I am wrong?
Thanks in advance.
Related
I am getting empty array when call paypal setExpresschecout function with sandbox credential.
if i put live credential then its work fine.
This problem occur from last couple of week. before that the code worked fine on both live and sandbox credential.
Anyone have any idea?? Please Help.
Did you check which version of SSL/TLS your are using to make the API call?
PayPal recently upgraded to TLS 1.2 as you can see on their developer blog:
https://devblog.paypal.com/upcoming-security-changes-notice/#tls
For now it's only on the sandbox but they are going to do this on the live environment in the future.
It means if you're using TLS 1.1 or 1.0 for your API call it won't work anymore.
I had to update my test server because it was impossible to call their API anymore.
Current Prestashop version 1.6.0.6 .
Latest Paypal Modul installed 3.7.2 .
Paypal Modul is installed correctly.
Error-Description: I can not upload a screenshot due to lack of reputation. You can see it by clicking this link
When I want to order via Paypal I do get the error message:
Error occurred:
Please try to contact the merchant:
PayPal response:
->
Please suggest a way to get rid of this error.
Hi you need to upload to the latest version of paypal (3.8.1) in modules. 3.7.2 is no longer working.
I’m integrating paypal Api for my company with NVP mode. The Application must be run on Websphere application Server.
In paypal SDK core, it actually uses in class SSLUtil (line 37) : KeyManagerFactory.getInstance("SunX509"). this does not work on IBM JRE.
WAS uses IbmX509.
What can I do if I don’t want to modify the paypal class?
Thank you for you answer?
regards!
Stevens
Please use the following branch for you to get the fix. Please build and use that core with the SDK.
https://github.com/paypal/sdk-core-java/tree/fix-keymanagerfactory-ibm
Changed the SSLUtil Class as follows which should fix it for IBM as well as Oracle JRE.
KMF = KeyManagerFactory.getInstance(KeyManagerFactory.getDefaultAlgorithm());
We have made it agnostic of JRE provider.
Good Morning all
I am looking for help on a licensing issue in SOAP UI.
I have a purchased license od SOAP UI pro and tried to activate the license on my new Windowa-7/64 bit DELL system.
i am unable to activate it in SOAP UI pro 4.5.2.
http://www.soapui.org/Getting-Started/i ... enses.html
Every time I try to activate online now this is the message I receive an error message
Error
Unable to activate license.
The license can not be activated as the number of allowed copies has been exceeded.
How can I get my new license activated?
The problem can be resolved if you put an old version of soap ui first and then start updating the license file with the new one.
I am using 4.6 Soap Ui pro and faced it again.
This might not be an issue of Soap Ui , but is the problem of updating the old license (which is expired ) or adding a new license in the existing Soap Ui with the new license.
please let me know , if there is some doubts .
Contact SoapUI support http://www.soapui.org/Support/support-overview.html . I think they can help you.
Maybe you should use an online tool that is more adapted to SOAP tests and does not require that you install anything. Try https://www.wsdltophp.com. Why using a installed software to do online stuffs (SOAP) when online tool exists?
Up until today, I have been successfully developing with PayPal's sandbox using the new PayPal PHP SDK which comes preconfigured to use this sandbox URL:
https://api.sandbox.paypal.com/2.0/
(URL in Chrome currently returns: "Error 107 (net::ERR_SSL_PROTOCOL_ERROR): SSL protocol error.")
But today my webapp is crashing due to a SSL handshake failure:
Uncaught exception 'PPConnectionException' with message 'error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure' in ./paypal-sdk-1.0.92/lib/PPHttpConnection.php:185
The only event that has occurred since yesterday (when my webapp was last working) was I reset my sandbox "seller" account, which may have reset the API credentials according to this post. Since I've updated the API credentials manually, and have verified them to be correct, I cannot say if they were ever wrong at this point.
After lots of searching, I found other web articles that say the URL should be:
https://api-3t.sandbox.paypal.com/2.0/
(URL in Chrome returns a SOAP response.)
So I changed my PayPal PHP SDK's included URL from https://api.sandbox.paypal.com/2.0/ to https://api-3t.sandbox.paypal.com/2.0/ and it is working perfectly again. What happened here? Is the non-"3t" sandbox URL simply broken right now?
EDIT: After the feedback received from #Win and #JoelP, I have filed a bug report through the PayPal SDK github so someone at PayPal can explain what changed today and fix the SDK to have the correct URL when using Signature credentials.
EDIT 2: PayPal fixed the issue a few days ago. It's going to be available in the next release. https://github.com/paypal/SDKs/issues/22#issuecomment-8660682
Thanks for the help everyone.
Differences are between Certificate and Signature
Signature is the preferred way of accessing PayPal API.
The issue is fixed and the code has been pushed to master branch. You should see the refreshed bundles of the sdk out on x.com in the next couple of days.
Refer GitHub issue here https://github.com/paypalx/SDKs/issues/22
Thanks,
Prasanna.
I can't answer the question but I can say that I have just discovered the same problem. I confirm that jimp's workaround of changing the SDK's service endpoint config to :
service.EndPoint="https://api-3t.sandbox.paypal.com/2.0/"
solved my issue. (This is in the Paypal SDK config/sdk_config.ini file).
In my case I am using the PHP SDK. I have not changed anything on my sandbox account. My best guess is that the original URL is simply down for a while. (Firefox shows the "Secure Connection Failed" alert).