EBICS is a corporate-to-bank file-transfer protocol used widely in Germany, France, Switzerland, and Austria. It is *not* a payment-message format — it is the secure transport layer that carries pain.001 / pain.008 XML files (and pulls camt.053 / camt.054 statements) between a corporate's treasury system and the bank.
The protocol has two flavours: EBICS T (Transfer) for plain file transport with channel-level signing, and EBICS TS (Transactional Signature) where each payment instruction is signed individually with a corporate user's secure key (typical for multi-signature corporate accounts).
Most EU banks publish their EBICS connectivity parameters openly — host URL, partner ID, user ID setup, key-management instructions. The corporate side runs an EBICS client (Linkit, BL Banking, b2-bank, Apollo) or a managed service.
iso-compliant is not an EBICS client; it produces the ISO 20022 *file* that the customer's EBICS client uploads. The split is intentional: keeping the bank-channel layer outside iso-compliant means the customer retains their existing bank relationships and the credentials never leave their stack.