Pre-Authorization Capture Service

The capture of the Pre-Authorization is intended to effect the Pre-Authorization, which may be in the total amount or lower than the total value of the Pre-Authorization. This will depend on the business rule of the Virtual Store application.

The flow should be: do the pre-authorization operation and if the result is approved, the capture service should be called to complete the flow. The capture will be accomplished in the moment defined by the application business rule.

In the capture operation, the parameter amount may have a value equal to or less than the pre-authorization parameter amount.

For GetNetLac via SiTef routing, the installment can also be done at the pre-authorization and in this case, the capture should expect a installmente number equal or more than the sent previously. If the pre-auth is a sale spot, the capture can not be installed.

Call details

Resources: /v1/preauthorizations/capture/{nit}
HTTP Method: POST
Request format: JSON
Response format: JSON
Header parameters:

Parameter	Description	Format	Mandatory
`Content-Type`	Fixed value `application/json`	= 15 AN	YES
`merchant_id`	Merchant code on e-SiTef. The production and certification codes will be different.	< 15 AN	YES
`merchant_key`	Merchant authentication key on e-SiTef. The production and certification keys will be different.	< 80 AN	YES

Example

Request:

curl
--request POST "https://esitef-homologacao.softwareexpress.com.br/e-
sitef/api/v1/preauthorizations/capture/1234567890abcdefghijklmnopqrstuvwx
yz1234567890abcdefghijklmnopqr"
--header "Content-Type: application/json"
--header "merchant_id: xxxxxxxx"
--header "merchant_key: xxxxxxxxxxx"
--data-binary
{
   "amount":"100",
   "installments":"1",
   "installment_type":"4",
   "card":{
      "number":"xxxxxxxxxxxxxxxx",
      "expiry_date":"1222",
      "security_code":"123"
   },
   "acquirer":{
      "submerchant_split":[
         {
            "submerchant_code":"empresa01",
            "submerchant_amount":"10"
         },
         {
            "submerchant_code":"empresa02",
            "submerchant_amount":"20"
         },
         {
            "submerchant_code":"empresa03",
            "submerchant_amount":"20"
         },
         {
            "submerchant_code":"empresa04",
            "submerchant_amount":"30"
         },
         {
            "submerchant_code":"empresa05",
            "submerchant_amount":"30"
         }
      ]
   }
}
--verbose

Response:

{
   "code":"0",
   "message":"OK. Transaction successful.",
   "capture":{
      "status":"CON",
      "nit":"1234567890abcdefghijklmnopqrstuvwxyz1234567890abcdefghijklmnopqr",
      "order_id":"orderID",
      "customer_receipt":"=== CUSTOMER RECEIPT ===",
      "merchant_receipt":"=== MERCHANT RECEIPT ===",
      "authorizer_id":"2",
      "acquirer_id":"1005",
      "acquirer_name":"Redecard",
      "authorizer_code":"000",
      "authorizer_message":"Transacao OK.",
      "authorizer_date":"09/11/2018T19:40",
      "authorizer_merchant_id":"000000000000000",
      "authorization_number":"212195",
      "esitef_usn":"180921015287704",
      "merchant_usn":"20190101",
      "sitef_usn":"212195",
      "host_usn":"999212195",
      "amount":"100",
      "payment_type":"C",
      "issuer":"2"
   }
}

Request parameters

Parameter	Description	Format	Mandatory
`amount`	Purchase amount specified by store (in cents) on transaction creation.	< 12 N	YES
`discount`	Discount amount in cents. In case of pre-authorizations with promotional values when using Visa Checkout, VISA suggests that this field should be submitted additionally.	< 12 N	NO
`installments` (*)	Installments number, `1` for sale spot	< 2 N	YES
`installment_type`	Along with the installments field, indicates installment. Possible values for `installment_type` are: `3`: Installments with interest `4`: Installments without interest (adopt this as default on spot sales)	= 1 N	YES
`promo_code`	Visa Checkout promotion code used in pre-authorization. In case of pre-authorizations with promotional values when using Visa Checkout, VISA suggests that this field should be submitted additionally.	AN	NO
`subtotal`	Subtotal amount, in cents. In case of pre-authorizations with promotional amounts by using Visa Checkout, VISA suggests that this field be submitted additionally.	< 12 N	NO
`card`	Sending card data is mandatory on SiTef routed transactions with the exception of the Cetelem acquirer. Only one of these fields must be used: `number`, `token` or `wallet_transaction_id`
`number`	Customer's card number (PAN).	< 19 N	COND.
`token`	Used for recurring pre-authorizations, when the card is already stored at e-SiTef database.	= 88 AN	COND.
`wallet_transaction_id`	Wallet Visa Checkout transaction ID.	< 25 AN	COND.
`initial_wallet_transaction_id`	Informs if the Wallet ID (`wallet_transaction_id`) is being used for the first time. If it's the first time, send `true`, otherwise, send `false`. Required only for Visa Checkout. Default value: `true`	< 5 AN	COND.
`expiry_date`	Card expiry date in `MMYY` format.	= 4 N	COND.
`security_code`	Card security code.	< 5 N	COND.
`acquirer.` `submerchant_split[]`	It consists of an array for split payments, unique to BIN and Sipag routing, both via SiTef. Allows the division of parts of the total payment amount among other companies. The maximum number of items allowed in this array is 5 items. Each item consists of the `submechant_code` and `submerchant_amount` fields.
`submerchant_code`	store code BIN/Sipag	< 15 AN	NO
`submerchant_amount`	transaction amount for merchant	< 12 N	NO
`mcc`	The MCC (Merchant Category Code) is a code that classifies the business by the type of goods or services it provides.	< 4 N	NO
`subacquirer_merchant_id`	It is the merchant identification for the subacquirer.	< 22 AN	NO

Response parameters

Parameter	Description	Format
`code`	e-SiTef response code. Anything besides `0` means failure. See more information at the Response Code document	< 4 N
`message`	e-SiTef response message.	< 500 AN
`capture`
`acquirer_id`	Acquirer/routing ID used in transaction.	< 4 N
`acquirer_name`	Acquirer/routing name used in transaction.	< 100 AN
`amount`	Purchase amount specified by store (in cents) on transaction creation.	< 12 AN
`authorization_number`	Authorization number	< 6 AN
`authorizer_code`	Authorizer responde code.	< 10 AN
`authorizer_date`	Authorizer pre-auth effectuation date, returned by the authorizer on the format `DD/MM/AAAA’T’HH:mm`. Example: `13/07/2017T16:03`	= 16 AN
`authorizer_id`	Authorizer ID use in transaction.	< 4 N
`authorizer_merchant_id`	Merchant ID from authorizer.	< 100 AN
`authorizer_message`	Reponse message from authorizer.	< 500 AN
`customer_receipt`	Customer receipt.	< 4000 AN
`eci`	Eletronic Commerce Indicator (pre-authorization security level indicator on transactions via Cielo e-Commerce).	< 3 AN
`esitef_usn`	e-SiTef pre-authorization's unique sequential number.	= 6 N
`host_usn`	Authorizer NSU.	< 15 AN
`issuer`	Issuer code returned by the authorizer.	< 5 AN
`merchant_receipt`	Merchant receipt.	< 4000 AN
`merchant_usn`	Unique sequential number sent by store at the transaction creation.	< 12 AN
`nit`	e-SiTef pre-authorization transaction ID.	= 64 AN
`order_id`	Order ID sent by the store at transaction creation.	< 40 AN
`payment_type`	Payment type from the selected authorizer: `B` = boleto, `C` = credit, `D` = debit, `P` = Private Label credit card, `T` = bank transfer, `G` = gift card, `O` = other payment methods, `W` = Boleto NR via Web Service	= 1 AN
`sitef_usn`	SiTef pre-authorization's unique sequential number.	= 6 N
`status`	e-SiTef pre-authorization transaction status.	= 3 AN
`tid`	Acquirer/routing transaction ID. This field is only returned in transactions with external acquirer's.	< 40 AN
`xid`	XID field returned on 3DS authentications or certain acquirers/routings.	< 40 AN