|
|
|||
|
Central debit card authorisation system
|
|||
|
It supports for the following functions the communication protection, card and account validation and backend interface processing for the banks own cards.
Currently the authorisation of magnatic strips and chips version SECCOS 5.0 and SECCOS 6.0 is supported.
Request processing
The incoming messages, from own terminals as well as from acquirer gateways, are checked and authorised. To document the authorisation, technical and account related log files are kept during processing. The ISO converter, which is a central input and output component for all messages, converts different message formats (ISO 8583, etc.) to one internal working structure. At the end of processing, this structure contains all relevant information to create outgoing message in the desired output format. The customized Repository contains the base information upon which authorisation components are to be processed. This centrally controlled authorisation process as well as the modular construction of the authorisation system easily facilitates an extension and redesign of the functions. Designed as a service oriented architecture (SOA), our system economically adjusts to the requirements of the future.
Transaction security
As a part of the transaction security,
|
|
Card- and account validationParts of the card- and account validation are:
Backend processingThe existing central components can be economically and easily combined through the open interfaces of the system (parametric user exits). e.g.
Response
The EMV response can be customized according to the issuer’s requirements.
Advice messagesRelevant information about limits and locks is provided to the gateways for independent offline authorisation.
What are the benefits of
|
|
|
|
|||
|
|
|||