These websites are using cookies. By further using the websites you agree with using cookies. Read information about how we use cookies and how you can refuse using them by setting your browser.

Tatra banka

26.5.2018 10:15

Multicash

Are you an international company and do you want to communicate with
several banks using only one application?

  • lower charge for payment order processing
  • payment orders imported directly from an accounting system in various formats
  • electronic account statements in the international format MT940
  • installation as a single-user or network version
Advantages

Advantages

  • lower price for payment order processing
  • security and protection at highest level
  • electronic account statement in SEPA XML SK standard
  • payment orders can be imported also directly from your accounting system in
    SEPA XML pain 001.001.03 formats for domestic payments
    and SKA for foreign payments
  • possibility of sending collection orders (both CORE and B2B)
  • monitoring of current account balance
  • file of payments can always be printed out
  • entering payment orders with future due date
  • the system can be installed both as a single user version or network version

Changes brought along with the end of temporary period 1 February 2016

Payment orders

  • Output file must be sent to the bank via SEPA module in SEPA XML format (pain.001.001.03) – other types will be rejected by the bank.
  • Sending payments from SKI module after 1 February 2016 will not be possible. Transition from SKI to SEPA module is necessary.
  • Neither SKA foreign module nor format of files for foreign payments will change.
  • SEPA payment - template

Electronic statements

  • SEPA XML SK standard (camt.053) statement which contains all settled items, not only SEPA payments, will be the only officially supported statement after 1 February 2016.
  • SEPA - STA (MT940) statement containing IBAN will be temporarily delivered to clients yet after 1 February 2016.
  • STA (MT940) statement not containing IBAN will not be delivered to clients after 1 February 2016. Transition to SEPA XML SK standard (camt.053) or conditionally to SEPA - STA (MT940) is required.
  • Format of SEPA XML statements will be updated to SEPA XML SK standard (minor changes which help adjust statements of other banks in the SR).
  • Distribution of other types of statements will be stopped as of 1 February 2016 (alternative possibility is to apply a convertor on client´s side).


Details

Details

  • The system can be installed as a single-user or network version
    The communication with the bank is carried out via a TCP/IP protocol (any internet connection) or public telephone network (analogue or ISDN modem). Multicash application enables you to communicate with the bank 24 hours a day with an unlimited number of connections.
  • Current balance on your account
    You receive information about the current balance on your accounts upon each connection with the bank.
  • Uncleared daily turnovers
    In the event of sent local payment orders you will receive, upon the next connection with the bank, details about these and all other turnovers that were realised in your accounts.
  • Payment order placement
    All types of payment orders can be imported directly from various accounting programs in SKI format for local payments and SKA format for foreign payments. In the case of the manual placement of payment orders a formal control of data is performed. You can use the database with the names of firms, account numbers, and bank codes.
  • Successful processing of payment orders
    Upon sending the file to the bank, you will receive information about the receipt and processing thereof, or the reason for transaction non-realisation. 
  • Account statement in international format
    We offer an electronic account statement in the international format MT940 that is always available on the following business day.
  • The file with payment orders can be printed anytime
    Each file with payment orders can be printed with details anytime.  
  • Simple communication
    When the client connects with the bank, all files prepared for the bank are automatically sent to the bank, and the files prepared for the client at the bank are sent to the client's PC.
Security

Security

Perfect security is one of the primary conditions for any direct banking system, since information that requires protection against misuse is mutually transmitted between the bank and clients.

System security is secured by:

  • User identity verification (authentication) on login to the application - each user logging into the MultiCash application has a unique identification. Therefore each user is assigned a login user name and password.

  • Integrity, authenticity and indisputableness - is secured among other things by electronic signature authenticity, ensuring that the data is protected against mishandling and that it can only be dispatched by/to the bank's authorised client. Sufficient message confidentiality is ensured by Triple DES encryption. Moreover, a control record of events in the form of control protocols is used on the part of both client and bank. These protocols enable easy verification of communication exchange, dispatched data content and successful processing, as well as other information which helps to identify payment-related data and users who entered, modified or dispatched payments.

  • Electronic signature - is based on asymmetric encryption. In each communication a pair of keys is used - a public and private key. The "EP" module on the client's computer generates this pair of keys. The public key is transmitted online to the other party in the communication (the bank). The private key is stored on a disk (USB or HDD) and is secured by EP password. If there is communication between parties, a message is sent from the client (= payment order) encrypted by the used private key. The other party to the communication (the bank) receives the message, and decodes it using the public key used when the report was sent to the bank. The party to the communication can only decode the message if it has the relevant public key for the private key.Final reports - are only sent upon communication completion. They describe the status or result of the transmission. The response codes accepted by the client are evaluated and represented in the attached protocol.

  • Limit messages - are transferred to the communication has finished. Contain messages that describe the status or outcome of transmission. Response codes received by the client side are evaluated and shown in the annexed protocol.

  • Hash value - is created by using the original file. This hash value is added to the EUZ file (EP file) with the date and time the original hash file was generated, the original file name, etc. EUZ file is "signed" using the private key, and the result of this "signature" is added to the EP file with the name of the person authorised to sign, the date and time of signature, EP type and version used, and other information.The hash value generates the control sum for a file of any length (= the original file). The hash value represents the basis for an electronic signature.
Technical requirements

Technical requirements

  • PROCESOR Pentium IV 1,4 GHz and higher or comparable processor from other producer
  • HARD DISK 1 GB of free space (disk space depends on number of installations and volume of transferred data)
  • 2 GB RAM
  • WIN Vista, WIN7, WIN8 operating system
  • FONTS (LATIN2) – required for using Slovak or Czech language
  • TCP/IP communication – Internet connection with direct access to port 2500
  • Free USB port
  • Printer (necessary for initialisation procedure)
  • CD drive, mouse, keyboard, monitor