Introduction

The libraries CliSiTefI and CliSiTef offer business automation developers a set of routines (API ́s) for integration with the SiTef server. The SiTef server, in turn, offers a wide range of payment services with the most diverse authorizers.

The libraries CliSiTefI and CliSiTef are available for a range of platforms, typically in the form of dynamic libraries.

It has entry points through which business automation configures it, requests a payment, requests a managerial role or paying a bill.

Entry points are at CliSiTefI and this is what must be loaded by the user application.

The CliSiTef is for the exclusive use of CliSiTefI e não pode ser carregada ou chamada diretamente sob risco de, eventualmente, desestabilizar o ambiente. Neste documento, qualquer referência a CliSiTef deve ser entendida como o conjunto destas duas bibliotecas.

Target Audience

Commercial automation developers with CliSiTef.

Goals

Present a description of the library that interfaces with the available payment method services on SiTef.

Presentation

CliSiTef provides a quick and simple way to make SiTef functionalities available to applications in general. Its main features are:

Non-intrusive as it is the automation itself that manages your screens. No overlapping of screens occurs own interface which, if it existed, would most of the time not be compatible with the visual layout of the main client application; Allows the automation application to restrict the transactions available for a given payment since, in practical life, negotiation takes place with the customer and once the payment method is closed, number of installments, etc., must not be modified by mistake when executing the TEF; Allows complete freedom in the inclusion of new products and payment methods, following developments of SiTef, without the need to make any changes to the automation or, if it is essential (for example, example by the inclusion of new access peripherals such as bar code readers), that it is minimum.

Note: CliSiTef has, for each functionality, two entry points (routines). Choosing which of the interfaces will be used by the application depends on the programmer's personal taste and whether the environment used by For development purposes, it imposes some type of restriction on the call to CliSiTef. In particular, we are referring to the type of data manipulated by the programming environment. If it only accepts ASCII data, The interface named below in this document as “A” must necessarily be used.