Overview

introduction

The usual ways for Transaction Status Inquiry and Handling of Pending Transactions require the use of SiTef® or SiTef-Conciliation reports.

These options do not allow the automation of operations.

To get around this problem, an online consultation and dispute resolution service was created, which will be accessed by an "App Server" (developed by the integrator/Client) allowing the listing, status validation and resolution of pending SiTef-Conciliation transactions.

The WebService uses an Application Server based on Jetty, responsible for treating HTTPS requests. On this server, the services for handling pending issues and checking the status of transaction via REST protocol are displayed. For authentication and authorization, the Basic Authentication protocol is used (using the SiTef-Conciliation user login) for each request.

Goals

This documentation aims to present the definition of interfaces and technical criteria necessary for use of the Query WebService.

Target Audience

This documentation is intended for the integrator/customer development team, or any interested in using the Query and pending resolution of transactions service.

Caveat

This available process of confirming or undoing a TEF transaction allows the transactions have their status changed on the SiTef® server.

The effecting of this change in the acquiring network will depend on the business rule adopted by each network.For example, we have networks that commit any pending transaction on the third day, other networks cancel a debit transaction if it is not effected on the same day. We also have networks where if a transaction is not resolved at the time of sale, the change will depend on a message originating from the acquiring network, this message we call a probe.

Therefore, in order to make this process effective, we suggest carrying out this process at least once a day.