Skip to content

Conversation

jplot
Copy link
Contributor

@jplot jplot commented Aug 27, 2024

No description provided.

@jplot
Copy link
Contributor Author

jplot commented Sep 26, 2024

Hi @tobischo,
You can start reviewing the code.
I'm waiting to finalize tests with our financial partner before putting the PR on ready.

@tobischo
Copy link
Collaborator

I am really excited to see that you also added EBICS 3 🤩

I had that on my list as a potential followup after your changes.
Will review as soon as I have time and also start testing whether the 2.5 cases still work that I am responsible
I might have access on a test API to 3.0 as well 🤔

Copy link
Collaborator

@tobischo tobischo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall this looks great.

I haven't tested it yet against an EBICS API, so I cannot speak to whether it is still working (yet).

I think it is missing some test cases, e.g. around the signature algorithm handling and using a different EBICS version

Communication Standard).

It supports EBICS 2.5.
It supports EBICS 2.4, 2.5 and 3.0.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the readme could reflect which one is the default when initializing a new or existing client and how to work with another version

@frantisekrokusek
Copy link
Contributor

@jplot do you need help finalizing this ?

@jplot
Copy link
Contributor Author

jplot commented Jan 2, 2025

@jplot do you need help finalizing this ?

I don't have a sandbox environment to test end-to-end operation.

@tobischo
Copy link
Collaborator

I haven't checked if it supports EBICS 2.4, but https://iso20022test.credit-suisse.com/login provides a testing environment for communication through EBICS

@tobischo tobischo mentioned this pull request Feb 26, 2025
@janz93
Copy link

janz93 commented Mar 11, 2025

Sadly the credit-suisse test ox does not work for ebics 3.0

Es gibt keine Testumgebung; insbesondere eignet sich der
EBICS-3.0-Zugang der Credit Suisse ISO 20022 Test
Platform nicht zum Testen von Direct Link

https://www.credit-suisse.com/media/assets/private-banking/docs/ch/unternehmen/unternehmen-unternehmer/umstellung-von-ebics-25-auf-30-de.pdf

@jplot
Copy link
Contributor Author

jplot commented Mar 27, 2025

@tobischo I have reallocated my work time to this project full-time, with the aim of integrating the features related to versions 'H003' and 'H005'.
To ensure compatibility with version 'H005', it was imperative to refactor the way we generate XML.

@tobischo
Copy link
Collaborator

tobischo commented Mar 27, 2025

Amazing 😃
Let me know when you think it is testable and I will try to at least test the data retrieval cases.
I am not sure I can promise testing the upload part 😅

@frantisekrokusek
Copy link
Contributor

@jplot We have some mandates with H003 servers so we can also do the testing part for you 😉

@jplot
Copy link
Contributor Author

jplot commented Apr 18, 2025

@frantisekrokusek If you have the possibility of writing more complete tests on the main branch, this would allow me to guarantee the integrity of the new system.

@jplot
Copy link
Contributor Author

jplot commented Apr 28, 2025

For version H003, I can only confirm that FDL, HAA, HAC, HEV, HIA, HKD, HPB, HPD, HTD, INI, PTK are supported.

@frantisekrokusek
Copy link
Contributor

@jplot we just finished our testing phase on our fork
master...pennylane-hq:epics:master

We have successfully initialized those French banks but only tested INI/HIA/HPB/FDL commands because our mandates do not have access to other commands.
image

@jplot
Copy link
Contributor Author

jplot commented Jun 18, 2025

StackEdit-06-18-2025_04_05_PM

@jplot
Copy link
Contributor Author

jplot commented Jun 18, 2025

Key Technical Points for H003 and H005 Versions

  • AuthSignature: We've observed that the AuthSignature function isn't working correctly on version H003. An investigation is needed to resolve this issue.
  • X.509 Certificate Generation: The implementation of X.509 certificate generation will become mandatory for version H005. Therefore, we must ensure this functionality is properly integrated.
  • Signature Functions (EMSAs): For version H005, the emsaPssEncode (reference A006) and emsaPkcs1V15Encode (reference A005) signature functions are missing. Their development is crucial for compliance and security.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants