A bank is the primary entity in an EBICS transaction. It hosts the server with which a partner and users who are associated with the partner can perform EBICS transactions.
- Bank ID (Host ID)
- Bank Name
- Bank URL
- Is RSA preferred
- Bank contact information
- E-mail address
- Public keys of authentication and encryption certificates
- Key versions of authentication and encryption certificates
An integral part of the bank configuration is the bank ID or host ID. After a contract is signed, the bank shares the bank ID or host ID together with the URL of the bank with the partner. An EBICS Client admin creates a bank profile using the information shared by the bank with the partner. If the bank URL uses a secure HTTP protocol, then an HTTPS certificate is required. The HTTPS certificate for the bank is created on Sterling B2B Integrator and configured using EBICS Client.
- An EBICS Client user submits an HPB order type to download the public bank keys.
- After successful validation of the user's authentication and identification keys, the bank sends an HPB response. The HPB response contains the public bank keys. The keys are stored in the database of EBICS Client and hash value of the keys is generated.
- The bank provides hash values of the public part of the keys to the user through a channel independent of EBICS. For example, a portal, mail, or the website of the bank.
- The user copies the hash values from the portal and validates the bank keys using the EBICS Client dashboard interface.
- The hash values shared by the bank are compared with the internally generated hash values. If the hash values match, the status of the bank is set to Activated. If the hash values of the bank and user do not match, the user is prompted to revalidate the bank keys.