TRAVIC-Sign-Mobile is used together with EBICS or FinTS client applications (e. g. TRAVIC-Port). If a user for example tries to login to or release a payment with the client application, TRAVIC-Sign-Mobile asks him to confirm this action. For the PSD2-compliant release of a payment TRAVIC-Sign-Mobile displays this payment’s order data. As soon as the user verifies the release of the payment, TRAVIC-Sign-Mobile generates a signature (EBICS A00x or FinTS RAHxx) that matches the order. The keys, which are required for a PSD2-compliant release, are saved on the smartphone. The client application subsequently processes the response and releases or declines the order. Apart from this procedure, TRAVIC-Sign-Mobile also supports less strict procedures like a simple confirmation process.
TRAVIC-Sign-Mobile consists of a smartphone app (iOS/Android) and a server component. During the initial login, the app is stored in the server component with the smartphone and respective user identification. The communication that follows is always encrypted and signed. Information of the financial institution, which is displayed on the smartphone, is sent to the server with the address information of the recipient.