Skip to content

Latest commit

 

History

History
81 lines (49 loc) · 4.18 KB

HOWTO.md

File metadata and controls

81 lines (49 loc) · 4.18 KB

Setup

  • The docker image contains jar file and dependencies of java-ebics-client.
  • First step is to contact your bank to request EBICS access and sign the needed documents.
  • They might ask for an IP address and only allow requests from this address.
  • Find your banks EBICS parameters, eg EBICS parameters for Zürcher Kantonalbank (in German)
  • In addition your bank will provide you with more parameters such as user id.
  • Put those parameters in the $HOME/ebics/client/ebics.txt properties file.

Usage

Start command line tool in the container:

docker run e36io/ebics-service java -cp "./ebics-cli-1.2.jar:lib/*" org.kopi.ebics.client.EbicsClient --help

Create $HOME/ebics and $HOME/ebics/out to store parameter (ebics.txt) files, keys and output to a local directory.

Once you configured ebics.txt you can create the user and send the INI and HIA request.

docker run -v $HOME/ebics:/root/ebics e36io/ebics-service -cp "ebics-cli-1.2.jar:lib/*" --create

docker run -v $HOME/ebics:/root/ebics e36io/ebics-service -cp "ebics-cli-1.2.jar:lib/*" --ini --hia"

Then you need to print the generated initialization letters, they are generated in text format. Afer printing, send those letters to your bank - they need that to create the Ebics login. The letters are in ./client/users/<userId>/letters/

After this you can send the HPB request to fetch the bank parameters.

docker run -v $HOME/ebics:/root/ebics e36io/ebics-service -cp "ebics-cli-1.2.jar:lib/*" --hpb

Then you need to compare the if the bank encryption keys from the HPB request match with the keys you see in your documents.

Now the client is ready to use, you can fetch the account data with a STA request

docker run -v $HOME/ebics:/root/ebics e36io/ebics-service -cp "ebics-cli-1.2.jar:lib/*" --sta -o /root/ebics/out/sta-test.txt

The successful setup is shown by:

2021-05-22 07:53:48,251  INFO - Configuration initialization
2021-05-22 07:53:48,254  INFO - Loading user 4444444
2021-05-22 07:53:48,355  INFO - The user 4444444 was loaded successfully

Set up docker based development environment and test

FAQ

Setup with your bank

You need to talk with your bank and exchange the letters in paper before you can start. The Ebics security protocol is defined like that.

What configurations are possible?

Check out application*.yml files here. With spring boot you can use environment variables, yaml, property and other strategies to add your configurations to the project or docker container.

ERROR - Cannot download the requested file

Daily statements can only be retrieved once - then you get an error if you request again. This Ebics "error" sticks, until you have a new transaction on your accounts.

ERROR - Command not supported

Not all banks support the full set of commands, or you need to configure a differnt command to retrieve your daily statement. For example your bank does not support Zipping the daily statements (Z53 vs C53) - please see OrderType.java for supported commands and compare that with the list of supported commands of your bank.

XML Validation Errors & Debugging ebics XML files

Put the XSD files (Schema) in the same directory as your generated files. Now open the generated files with VS Code using the XML Plugin from RedHat - it will help you if your Ebics interface just quits with a validation error and without further details.