e-SiTef

e-SiTef

  • Portal do Desenvolvedor
  • Fale Conosco
  • English

›Non SiTef Routings

REST Payment

  • Overview
  • Quick start
  • Transaction creation service
  • Payment effectuation service
  • Payment confirmation service
  • Transaction status query
  • Multiple transactions status query
  • Card query service
  • Payment with multiple payment methods service
  • Payment with multiple payment methods confirmation service
  • External origin payment confirmation service

REST Store

  • Overview

REST Cancel

  • Flow
  • Quick start
  • Cancel via host
  • Cancel external origin
  • Cancel creation service
  • Cancel service

REST Pre-Authorization

  • Overview
  • Quick start
  • Pre-Authorization Creation Service
  • Pre-Authorization effectuation service
  • Pre-Authorization Status Query
  • Pre-Authorization Editing Service
  • Pre-Authorization Editing External Origin Service
  • Pre-Authorization Increment Service
  • Card Query Service
  • Pre-Authorization Capture Service
  • Pre-Authorization Capture External Origin Service

REST Schedule

  • Overview
  • Quick start
  • Transaction creation service
  • Schedule activation service
  • Execution of the scheduled payments
  • Schedule editing flow
  • Quick start: schedule editing
  • Schedule editing creation service
  • Schedule editing service

REST Recharge

  • Overview
  • Quick start
  • Recharge creation service
  • List dealers service
  • List branch data service
  • Recharge effectuation service
  • Recharge confirmation service
  • Recharge query service

HTML Payment

  • Overview
  • Quick start
  • Initializing a payment transaction
  • Status notification
  • Transaction status query
  • Payment with card storage
  • Pages Customization
  • Payment link
  • Split Payment
  • Payment with multiple payment methods
  • 3DS 2.0 Integration

HTML Pre-Authorization

  • Overview

HTML Recharge

  • Overview
  • Quick start
  • Initializing a Recharge transaction

REST Generic Operations

  • Overview
  • Token creation service
  • Generic operation service

JavaScript Payment

  • Overview
  • Quick start
  • Transaction creation service
  • Virtual store's payment page
  • Transaction query service

JavaScript Store

  • Overview
  • Quick start
  • Transaction creation service
  • Virtual store's page

Merchant Web Page

  • Introduction
  • Access to web page
  • Two-Factor Authentication
  • User Configuration
  • Configure Authorizers
  • Transaction Report
  • Daily Summary Report
  • Store Report
  • Recharge Report
  • Analytical Report
  • Transaction Cancellation
  • Schedule
  • Configure Risk Analysis
  • Configure Order Authorizers
  • Users Administration
  • Generate Payment Link

Retry

  • Overview
  • Flow
  • Retry and Schedule

SiTef Routings

  • Bradescard
  • Cetelem
  • GetnetLac
  • Orbitall
  • Vero
  • Bin
  • Sipag

Non SiTef Routings

  • Banco do Brasil
  • Banrisul Vero
  • Cielo e-Commerce
  • EPX
  • e.Rede Rest
  • Fepas HUB
  • Getnet WS
  • GlobalPayments WS
  • IPG
  • Itaú Shopline
  • Mercado Pago
  • PagSeguro
  • PayPal
  • SafraPay
  • Stone WS

Digital Wallet

  • Overview
  • VEE Digital Wallet via CardSE
  • Pix via CardSE
  • Google Pay
  • Visa Checkout
  • Masterpass
  • Samsung Pay
  • Apple Pay
  • Configuration for Digital Wallets

Anti-Fraud Integration

  • Overview
  • Risk analysis service on the HTML Interface
  • Risk analysis response
  • Manual review flow
  • Fraud notification service
  • ClearSale
  • CyberSource
  • Konduto
  • Fraud Detect

General Information

  • Authorizers
  • Digital Certificates
  • API codes
  • Soft Descriptor
  • Signature authentication

Batch Registrations

  • Batch Store Registration
  • Batch Routing Configuration

REST Merchants Registration

  • Overview
  • Quick start
  • Token creation service
  • Merchant creation service
  • Merchant editing service
  • Merchant query service
  • Merchant status query service
  • List merchants service
  • API codes

3DS Server

  • Overview
  • Quick start
  • Transaction creation service
  • Authentication service
  • Transaction query service
  • Challenge messages
  • Decoupled notification
  • Initiating a 3DS Method
  • API codes

Itaú Shopline

e-SiTef allows integrating the merchant' site with payments through Itaú Shopline, where the buyer access his own account through Itaú interface to make the payment via boleto bancário, bank transfer or using Itaucard cards.

In this page, the nomenclature "Itaú Shopline" will be used to reference the acquirer on e-SiTef.

e-SiTef Interfaces Supported for Integration

The following interfaces for integration with Itaú Shopline are available:

  • HTML Payment
  • Reissue of boletos

Allowed Authorizers / Issuers

The following authorizers / issuers are available for integration with Itaú Shopline:

  • Itaú Shopline

Required credentials

The merchant must obtain with Itaú the credentials listed below, and pass them to Software Express.

FieldField descriptionFormat
codigoEmpresaCompany code (merchant) on Itaú.= 26 AN
chaveCryptography key for information exchange with Itaú Shopline.= 16 AN

Itaú Shopline Portal required configurations

Some configurations must be done on the merchant's account on Itaú Shopline for flawless integration with e-SiTef.

Return URL

For a correct operation of the payment confirmation, it is required the merchant logs on Itaú Bankline with his credentials and configure Shopline's Return URL field with the e-SiTef URL below:

Production environment
https://esitef-ec.softwareexpress.com.br/e-sitef/itau.se
UAT environment
https://esitef-homologacao.softwareexpress.com.br/itau.se

This URL is used for Itaú to confirm the payment on e-SiTef. There is a 60 characters limitation on Itaú Shopline for the URL, so be very careful when registering the URL, as it's different depending on the environment (UAT or Production).

Notice that updates on Itaú can take one business day to become available.

Below is a copy of the Itaú Shopline technical manual for accessing account data.

(Retrieved from Itaú Shopline technical manual)

On Itaú Bankline, the path to access this function is: Products and Services > Itaú Shopline > Account Data

(...)

Attention: Any information updated in this environment will be available for usage 1 (one)business day after the update. To access Itaú Bankline, it is required to go to Itaú site (http://www.itau.com.br/) and type:

  • Agency data, Current Account and Electronic Password on Itaú Bankline Enterprise access bar;
  • or Operator User data and Electronic Password on Itaú Bankline Enterprise Plus access bar.

Payment Flow with Itaú Shopline

After configuring this payment method for the merchant, the payment flow occurs the following way:

  1. User starts a payment via e-SiTef.
  2. The list of authorizers configured for the merchant is presented to the user.
  3. User selects Itaú Shopline payment method.
  4. At this moment a new window will open redirecting the user to Itaú Shopline.
  5. User starts the payment process on Itaú Shopline's website.
  6. User finishes the payment on Itaú Shopline's environment.
  7. Itaú Shopline redirects user to e-SiTef, according to the configured return URL.
  8. Upon receiving the user redirect, e-SiTef makes a query to Itaú and updates the transaction status.
  9. If the merchant has configured auto redirection, user is redirected to the Success or Failure URL configured on e-SiTef.
  10. In the end, if there is auto redirection, the user returns to the merchant website.

In the image below we can see in the diagram the flow described above:

An exception case to that flow is the case in which the Return URL was not registered on Itaú. Therefore, there will not be user redirection after the payment is finalized on Itaú Shopline.

Another possible case is starting a transaction with a pre-fixed authorizer, in which steps 2 and 3 are not necessary.

Thus, we suggest the configuration described in Return URL is made correctly, to allow a better shopping experience to the user.

Status Notification

For each transaction status update on e-SiTef, resulting from communication between e-SiTef and Itaú, it is sent to the merchant server a Status Notification. For further details about that functionality, see the HTML Payment in Status Notification.

Parameters for transaction via Itaú Shopline

The parameters used to create a payment transaction with Itaú Shopline are the same presented in HTML Payment on item Initializing a payment transaction.

Order Id

To use the Itaú Shopline payment method, it is required that the order id is always different for every transaction, and has eight digits only. This order id cannot repeat for 60 days (according to information from Itaú on 12/2010), and must be numeric. If the merchant submits more than eight or containing alphanumeric characters, e-SiTef will:

  • Remove all non-numeric characters.
  • Keep the last eight remaining digits (to the right).
  • Submit “0” if nothing remains.

Important: e-SiTef will not verify if the ids are repeating, and Itaú Shopline could even accept repeated order ids, however errors might happen, like non-paid new orders return as confirmed by Itaú. e-SiTef does not take responsibility for repeated order ids.

Itaú Shopline Payments via Boleto Bancário

In case the user selects Itaú Shopline payment via boleto bancário, the payment confirmation can take up to one business day to happen on Itaú, and keep itself in Pending status on e-SiTef during that period.

As Itaú does not inform e-SiTef when the payment of the boleto was done, e-SiTef can take more than one day to confirm, as the probe that updates the status of the boleto payments is executed just at dawn. In that case, the redirection to the success URL by e-SiTef, for the boleto selection case, will happen by the moment Itaú generates the boleto. It is up to the merchant to verify the transaction final status on e-SiTef.

If it is verified that the boleto date is beyond the days configured for cancellation, then the transaction status will be changed to Expired, so that the boleto payment status queries on Itaú are finished. If a payment transaction with Expired status on e-SiTef is made on Itaú environment, once Itaú notifies e-SiTef that the payment was done successfully, the transaction will be resumed and the payment will be made normally; if the payment is made with success, the transaction status is changed from Expired to Confirmed.

Pay attention to the fact that, for each transaction status update on e-SiTef, a POST will be submitted to the merchant's Status Notification URL registered on e-SiTef.

So that the customer can make a boleto bancário payment, it's necessary that the store submits to e-SiTef the following information:

FieldDescriptionFormatMandatory
identification_numberCustomer identification number (CPF or CNPJ)

If the customer identification number is greater than 11 digits the field will be considered CNPJ.
< 20 NYES
name
Customer full name.

For Itaú Shopline, name and surname plus a white space between them must have, at most, 200 alphanumeric characters.
< 200 AN
YES
surname
address_street_name
Customer address.

For Itaú Shopline, the street name, number and complement of the address plus the white spaces between them must have, at most, 200 alphanumeric characters.
< 200 AN
YES
address_street_number
address_street_complement
address_zip_codeCustomer ZIP= 8 NYES
cityCustomer city< 100 ANYES
stateCustomer state= 2 ANYES
neighborhoodCustomer neighborhood< 15 ANYES

Below is a usage example on e-SiTef's HTML Interface, with the request JSON object sent on the POST:

JSON
{
"merchant_id":"codigoDaLoja",
"merchant_usn":"98765",
"order_id":"abc123456",
"redirect":"A",
"authorizer_id":"7",
"amount":"1000",
"installments":"1",
"installment_type":"4",
"additional_data":{
"payer":{
"name":"Jose",
"surname":"Silva",
"identification_number":"09719224703",
"address_street_name":"Rua Jose Ninguem",
"address_street_number":"11",
"address_street_complement":"ap 12",
"address_zip_code":"01230120",
"city":"Sao Paulo",
"state":"SP",
"neighborhood":"Campos Eliseos"
}
}
}

Reissue of boletos

It is possible to make available to customers the reissue of Itaú Shopline boletos.

That functionality is available through the URL:

Production environment
https://esitef-ec.softwareexpress.com.br/e-sitef/reissue.se?nit=XXX
UAT environment
https://esitef-homologacao.softwareexpress.com.br/e-sitef-hml/reissue.se?nit=XXX

You must inform as a POST parameter the nit used in the original payment transaction, made via Itaú Shopline. The access itself to that URL already allows a direct visualization of the reissued boleto with the same data of the first emission.

If the payment transaction is not in the expected state, it is present an error message.

Attention

The IP address must never be used instead of the domain esitef-ec.softwareexpress.com.br (or esitef-homologacao.softwareexpress.com.br for Certification and Test environment). The IP address can change at any moment without notice, so it is important to always use the domain to access e-SiTef.

← IPGMercado Pago →
  • e-SiTef Interfaces Supported for Integration
  • Allowed Authorizers / Issuers
  • Required credentials
  • Itaú Shopline Portal required configurations
    • Return URL
  • Payment Flow with Itaú Shopline
    • Status Notification
  • Parameters for transaction via Itaú Shopline
  • Reissue of boletos
e-SiTef
Relacionamento com o cliente
+55 (11) 3170-5300+55 (11) 4766-8000comercial@softwareexpress.com.br
Acessos
Portal do DesenvolvedorPortal e-SiTefVersão para impressão
Copyright © 2021 Software Express Informática Ltda - Todos os direitos reservados