-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decryption failed reading BTD with Monte dei Paschi di Siena banque in EBICS V3 #201
Comments
Hello @NanoNao what version of library do you use? |
Im using 2.x-dev |
For more information, the error occurs in “decryptOrderDataCompressed” when the “decryptByKey” method is called. I wonder if |
You can try to updated keyring by next:
And check if keyring file was modified. |
Thanks for your reply. I've already tried it. I even created a new ebics contract with the . But I always get this error. My main question is whether it's a problem with the lib or the data sent by the bank. |
|
I believe this is the error with the lib. Should be investigated this scenario. Does HPB responses correctly? |
I've just checked and it seems that the keys in my keyring are correct. In Also i can decode data send in HPB with this same methode, so we can exclude problème with myPrivateKey. |
It could happen with wrong password. Try to settle password by
|
I'm sorry for the response time, I've done a new test but I'm getting abnormal response times from the bank with timeouts on their side. Unfortunately, I'm still waiting for a reply from them. |
Hello everyone.
I'm currently trying to read a CFONB120 for a BTP response. Unfortunately, the library catches a LogicException with this error message “Decryption failed”. I use EBICS 3.0
I've already used this library with another bank and everything was OK. I've already tried to solve this problem with the bank. But nobody has an answer to this problem.
I don't really know where to start looking or what to look for. I don't even know if the problem is with the lib or the bank. Do you have any clues about this problem?
Thank you and have a nice day
Version : 2.x-dev
Not using password for this test.
The text was updated successfully, but these errors were encountered: