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

PagSeguro

This document describes the integration with PagSeguro payment platform, as well as explaining about the configurations that must be made at e-SiTef environment.

ATTENTION: in UAT environment, the behavior of PagSeguro will be simulated by e-SiTef in order to make the UAT process more reliable and adequate, as PagSeguro's sandbox environment does not provide yet all the functionalities available in Production.

Therefore, the behavior of transactions made with PagSeguro authorizer in e-SiTef's UAT environment may not reflect the behavior of PagSeguro's production environment.

Despite the efforts to keep the simulator always updated, changes made by PagSeguro can occur without prior notice to the e-SiTef team.

Supported Interfaces

  • HTML Payment
  • REST Cancel
  • Merchant's Portal Cancel

e-SiTef required configurations

Before performing PagSeguro transactions with e-SiTef, the configuration steps below must be followed:

PagSeguro's account data

  • The Merchant must have an active account in PagSeguro. More information at PagSeguro website (in portuguese)
  • Following table shows PagSeguro credentials that must be retrieved by the merchant, which will be registered in e-SiTef later:
ParameterDescriptionMandatory
emailClient identificationYES
tokenAccess tokenYES

Insert account data in e-SiTef

  • Having the PagSeguro account data above, the merchant must request to the e-SiTef support team:

    • activation of PagSeguro as an active authorizer on e-SiTef.
    • a username and password for accessing e-SiTef's Merchant's Portal, if not taken already.
  • As soon as the PagSeguro authorizer is associated with the store, the merchant must access the Merchant's Portal and inform PagSeguro's account data in the "Configuração de Autorizadoras" (Authorizers Configuration) menu.

Authorizer Code for PagSeguro in e-SiTef

To make payments with the pre-defined authorizer, send code 403, which refers to PagSeguro authorizer.

Parameters for transaction via PagSeguro

The parameters used to make a payment transaction with PagSeguro must be sent to e-SiTef in JSON format, using the following URL:

https://esitef-homologacao.softwareexpress.com.br/e-sitef/init.se

For further details concerning HTML Payment Interface, refer to the specific section in this document.

ATTENTION: Transactions that start a dispute on PagSeguro will remain with status confirmed (CON) on e-SiTef as well as their possible results (refund or confirmed payment). It is up to the client to verify the transaction status with PagSeguro.

Below are listed the parameters that the merchant is able to send to e-SiTef to allow the client to make a payment on PagSeguro.

ParameterDescriptionFormatMandatory
additional_data
extra_infoAdditional information.< 1024NO
currencyCurrency in which the payment will be made, using ISO 4217 format. Currently, the only available option is BRL (Real).< 1024NO
extra_amountSpecify an extra amount that must be added to or subtracted from the payment total value. This amount may represent an extra tax to be charged in the payment or a discount to be granted, if the amount is negative.

Format: cents.
Example: 123456 (R$1234, 56) or -123456 (R$-1234,56)
< 1024NO
additional_data
.items[]
idItem identification.< 1024NO
titleItem title.< 1024YES
quantityItem quantity.< 1024YES
unit_priceUnit price of the item in cents.< 1024YES
descriptionItem description.< 1024NO
shipping_costThe shipping cost of every item being paid.< 1024NO
weightThe weight (in grams) of every item being paid. Used to calculate the shipping cost, if it is not informed.

Example: 3000 (3kg)
< 1024NO
additional_data
.payer
namePayer name.< 1024NO
surnamePayer surname.< 1024NO
emailPayer e-mail.< 1024NO
phone_area_codePayer area code.< 1024NO
phone_numberPayer phone number.< 1024NO
identification_typePayer identification type.
Only the value CPF is accepted.
< 1024NO
identification_numberPayer identification number.< 1024NO
address_street_namePayer address.< 1024NO
address_street_numberPayer address number.< 1024NO
born_dateDate of birth of the payer. ISO 8601 format.< 1024NO
additional_data
.shipment
costTotal shipment amount of the order.
Format: cents.
Example: 123456 (R$1234, 56)
< 1024NO
typeShipment type to be used to deliver the product.

Accepted values:
1 – Regular order (PAC)
2 – SEDEX
3 – Shipment type not specified.
< 1024NO
additional_data
.shipment
.receiver_address
zip_codeReceiver address ZIP.

Format: 8-digit number.
Example: 12345678
< 1024NO
street_numberReceiver address number.< 1024NO
street_nameReceiver address.< 1024NO
floorReceiver address floor number.< 1024NO
apartmentReceiver address apartment number.< 1024NO
districtReceiver address district.< 1024NO
complementReceiver address complement (block, apartment, etc.).< 1024NO
cityReceiver address city.< 1024NO
stateReceiver address state.

Example: SC (Santa Catarina), SP (São Paulo), etc.
< 1024NO
countryReceiver address country.

Currently only BRA value is allowed.
< 1024NO
additional_data
.extra_param
.metadata[]
keyAllows adding extra information, grouped or not, in your payment request.

Only the values described in here are accepted.
< 1024NO
valueAllows specifying values for the metadata defined in your payment request.< 1024NO
groupAllows grouping two or more metadata, e.g. CPF and name for the same passenger.< 1024NO

PagSeguro payment flow

After submitting the transaction creation data and selecting the PagSeguro payment method, the following UI flow will be initiated:

  • A PagSeguro LightBox window will be opened in the browser to make the payment:

"Lightbox PagSeguro"

  • If the transaction is aborted, the following screen will be shown:

"Aborted transaction"

  • If the transaction is confirmed, the following screen will be shown:

"Confirmed payment case"

  1. If the transaction is not confirmed, the following screen will be shown:

"Loading screen"

Status Notification – specific data

In Status Notification for payments made with PagSeguro, the following fields are additionally returned:

ParameterDescriptionFormat
pagseguro_status_paymentTransaction status in PagSeguro.
1 = Awaiting payment
2 = Under analysis
3 = Paid
4 = Available
5 = In dispute
6 = Returned
7 = Cancelled
< 15 AN
pagseguro_typeTransaction type in PagSeguro. Typically, type 1 = Payment< 5 AN
pagseguro_cancellation_sourceCancellation source in PagSeguro, only when the pagseguro_status_payment parameter is equal to 7.
INTERNAL = PagSeguro
EXTERNAL = Financial Institutions
< 10 AN
pagseguro_discount_amountDiscount amount granted.< 10 AN
pagseguro_fee_amountTotal amount of fees charged.< 10 AN

Attention: the data presented is returned by PagSeguro, so e-SiTef does not have control over them. Besides that, they may not always be returned.

Refund Transaction - REST Cancel

In order to refund a PagSeguro transaction, use the Cancel REST interface. For further details, refer to the specific section on this document.

Merchant's Portal

For general guidelines about the Merchant's Portal, please refer to the specific section on this document.

Merchant's Portal access URL – Production:

https://esitef-ec.softwareexpress.com.br/e-sitef-loja

Merchant's Portal access URL – UAT:

https://esitef-homologacao.softwareexpress.com.br/e-sitef-loja/

  • To refund a PagSeguro transaction, go to the Merchant's Portal and access the "Cancelamento" (Cancel) menu, as exemplified below:

"Cancel Menu"

  • Look for the transaction you wish to refund using the filters:

"Transactions List"

  • Click the transaction you wish to refund; the following screen will open:

"Transaction Details"

  • Verify if the data are correct and click on "Cancelar Pagamento" (Cancel payment) and then confirm it. If the transaction is successfully refunded, a refund receipt similar to the one below will be presented:

"Successful Cancel"

Appendices

Key values for Metadata

ValueDescriptionFormat
PASSENGER_CPFPassenger CPF[0-9]{11}
PASSENGER_PASSPORTPassenger passport.+
PASSENGER_NAMEPassenger name.+
ORIGIN_CITYOrigin city.+
DESTINATION_CITYDestination city.+
ORIGIN_AIRPORT_CODEOrigin airport code.+
DESTINATION_AIRPORT_CODEDestination airport code.+
GAME_NAMEGame name.+
PLAYER_IDPlayer ID.+
TIME_IN_GAME_DAYSTime in game[0-9]+
MOBILE_NUMBERMobile number([0-9]{2})?([0-9]{2})([0-9]{4,5}[0-9]{4})

JSON Sample

{
    "merchant_id": "CODIGO_LOJA",
    "order_id": "1123456",
    "redirect": "M",
    "authorizer_id": "600",
    "amount": "2000",
    "installments": "1",
    "back_url": {
        "url_success": "relative success url registered on e-SiTef",
        "url_failure": "relative failure url registered on e-SiTef",
        "url_cancel": "relative cancel url registered on e-SiTef"
    },
    "additional_data": {
        "extra_info": "dados extras",
        "currency":"BRL",
        "items": [
            {
                "description": "descricao",
                "id": "123",
                "quantity": "2",
                "title": "Produto 1",
                "unit_price": "1000",
                "weight": "4000",
                "shipping_cost": "1000"
            },
            {
                "description": "descricao",
                "id": "1234",
                "quantity": "3",
                "title": "Produto 2",
                "unit_price": "2000",
                "weight": "3000",
                "shipping_cost": "1000"
            }
        ],
        "payer": {
            "name": "João",
            "surname": "Silva",
            "email": "joao.silva@exemplo.com",
            "phone_area_code": "11",
            "phone_number": "78945123",
            "identification_type": "CPF",
            "identification_number": "12345678906",
            "address_street_name": "Rua do Exemplo",
            "address_street_number": "123",
            "born_date": "12/12/1900"
        },
        "shipment": {
            "cost": "2000",
            "type": "1",
            "receiver_address": {
                "zip_code": "12345678",
                "street_number": "Rua do Exemplo",
                "street_name": "123",
                "floor": "3",
                "apartment": "901",
                "city": "São Paulo",
                "complement": "Sobreloja 3",
                "country": "BRA",
                "district": "Jardim do Exemplo",
                "state": "SP"
            }
        },
        "extra_param": {
            "metadata": [
                {
                    "key": "PASSENGER_CPF",
                    "value": "12345678901",
                    "group": "1"
                },
                {
                    "key": "PASSENGER_PASSPORT",
                    "value": "1594825512",
                    "group": "1"
                }
            ]
        }
    }
}
← Mercado PagoPayPal →
  • Supported Interfaces
  • e-SiTef required configurations
    • PagSeguro's account data
    • Insert account data in e-SiTef
  • Authorizer Code for PagSeguro in e-SiTef
  • Parameters for transaction via PagSeguro
  • PagSeguro payment flow
  • Status Notification – specific data
  • Refund Transaction - REST Cancel
  • Merchant's Portal
  • Appendices
    • Key values for Metadata
    • JSON Sample
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