EPICS is a ruby implementation of the EBICS (Electronic Banking Internet Communication Standard)
The client supports the complete initialization process comprising INI, HIA and HPB including the INI letter generation. It offers support for the most common download and upload order types (STA HAA HTD HPD PKT HAC HKD C52 C53 CD1 CDD CCT)
Add this line to your application's Gemfile:
Or install it yourself as:
$ gem install epics
In case you are new to EBICS, you'll have to complete a initialization process with your bank. Epics can help you to generate all the necessary keys and directly store them for later use, but first you'll have to to lift some contractually work with your bank.
Once the paperwork is done, your bank should provide you with:
- a URL to their EBICS Server
- a HOST ID
- a PARTNER ID
- n User IDs (this depends on the bank and your needs)
Take this parameters and start setting up one UserID (repeat this for every user you want to initialize):
e = Epics::Client.setup("my-super-secret", "https://ebics.sandbox", "SIZBN001", "EBIX", "EPICS")
To use the keys later, just store them in a file
e.save_keys("/home/epics/my.key") # or store the json elsewhere, but store it! for gods sake :D
It is really important to keep your keys around, once your user has been initialized you'll have to start over when you loose the keys!
Submit the keys to your bank:
e.INI # sends the signature key e.HIA # sends the encryption and authentication keys
The next step is to print the INI letter and post it to your bank:
e.save_ini_letter( 'My Banks Name', "/home/epics/ini.html" )
Open the generated HTML file in your favorite browser and print it out (skipping header and footer sounds like a solid setting here ;) In case your having difficulties with the encoding, try forcing your browser to use UTF-8.
Put the INI letter in a envelope and mail it to your bank!
Done! ... Well not completly :)
Once the bank confirms that your user is completely initialized. You'll have to download the public keys of your bank:
### see below for client creation e.HPB
Then again, save the keys or store the json somewhere safe.
You're now ready to go. Maybe try:
To get a list of all supported order types.
Need help? Having questions?
We have many years of experience in developing innovative applications for the finance sector and integration application with financial institutions. - you might want to have a look at our portfolio
If you need help we are happy to provide consulting or development services. Contact us: [email protected]
Create a client
# read the keys from a file e = Epics::Client.new(File.open('/tmp/my.key'), 'passphrase', 'url', 'host', 'user', 'partner') # or provide a string hoding the key data keys = File.read('/tmp/my.key') e = Epics::Client.new(keys, 'passphrase', 'url', 'host', 'user', 'partner')
- INI (Sends the public key of the electronic signature.)
- HIA (Sends the public authentication (X002) and encryption (E002) keys.)
Currently this EPICS implementation supports the following order types:
- HPB (fetch your bank's public keys)
- STA (statements in MT940 format)
- HAA (available order types)
- HTD (user properties and settings)
- HPD (the available bank parameters)
- PKT (customer usage report in text format)
- HAC (customer usage report in xml format)
- ... more coming soon
puts e.STA('2014-09-01', '2014-09-11') # result is a MT940 feed :20:1 :25:/PL12124012551111000015237873 :28C:00152 :60F:C081130PLN000000002535,03 :61:0810021002DN000000001273,23N641NONREF :86:641^00PRZELEW MI
- CD1 (Uploads a SEPA Direct Debit document of type COR1)
- CDD (Uploads a SEPA Direct Debit document of type CORE)
- CCT (Uploads a SEPA Credit document)
- ... more coming soon
puts e.CD1("i-am-PAIN-xml") # res is a the transaction id and id of the order # if the XML is a file in your FS, read it first and give if epics to consume puts e.CD1(File.read("/where/the/xml/is/stored.xml"))
Once you have a client, go ahead and start playing! There are 3 convinence methods that are hiding some strange names from you:
- debit( xml ) (submits a PAIN.008.003.02 document via CDD)
- credit( xml ) (submits a pain.001.003.03 document)
- statements( from, to ) (fetches an account statement via STA)
If you need more sophisticated EBICS order types, please read the next section about the supported functionalities.
Issues and Feature Requests
Railslove is commited to provide the best developer tools for integrating with financial institutions. Epics is one of our many tools and services. If you are missing some features or something is not working as expected please create an issue.
This gem provides a full implementation of the Electronic Banking Internet Communication Standard and works with any bank that supports this standard. Please ask your bank if they support EBICS and what order types are available.
Besides EBCIS being a standard, some server implementations are slighty different. Is Epics working with your institution? Please help us to grow this list of supported banks:
- Deutsche Bank
- Sparkasse KölnBonn
- Commerz Bank
- EBICS specification
- Common Integrative Implementation Guide to Supplement the EBICS Specification (pdf)
- Die Deutsche Kreditwirtschaft
- Contact [email protected] for information about the CLA
- Fork it ( https://github.com/[my-github-username]/epics/fork )
- Create your feature branch (
git checkout -b my-new-feature)
- Commit your changes (
git commit -am 'Add some feature')
- Push to the branch (
git push origin my-new-feature)
- Create a new Pull Request
2014 - built with love by Railslove and released under the GNU LESSER GENERAL PUBLIC LICENSE. We have built quite a number of FinTech products. If you need support we are happy to help. Please contact us at [email protected].