Secure transactions for portals
The financial services industry has developed a multitude of security procedures for banking and payment services, based on cryptographic processes. Chip cards, TAN generators or secoder represent current state-of-the-art of security procedures. Signatures based on standards of the German Banking Industry Committee (Deutsche Kreditwirtschaft) such as FinTS and EBICS as well as token-based solutions such as the SWIFT 3SKey are supported.
One of our core responsibilities at PPI AG is to offer these types of security for portals such as an internet banking portal. This development started with HBCI in the mid-1990’s; PPI AG was involved right from the start. Increasing Internet criminality continually raises the pressure to use these procedures.
Less Involvement of the Hotline
It is equally important that portals run smoothly on all operating systems and browsers being used by private users. TRAVIC-Sign has proven its ability to operate stably for years. Installation as a C-plugin means the hotline is less involved with problems connected with Java-based applets, namely, a high dependence on system software and the release statuses, especially during automatic upgrades of Java versions and browser releases.
Dealing with Certificates
In addition to providing security procedures on all platforms, TRAVIC-Sign supports the secure messaging procedure that can be used to securely download or exchange certificates onto chip cards from trust centres, as well as a series of automated administration procedures, such as:
- changing the transport PIN
- PUK release after a card is blocked
Multiple chip cards and hardware/software tokens are supported. The use of hardened browsers (Coronic, Kobil, PROMON) is accepted practice.
Simple integration into portals, including transfer of the look & feel, are additional benefits.