Enabling special settings per transaction

In certain transactions, it is possible to include new functionalities and characteristics to the transactional flow, allowing greater flexibility of operation without these functionalities are not linked to a medium specific payment.

To do so, simply add a new field to the "ParamAdic" parameter, present in the functions that initiate the payment process or Banking Correspondent (IniciaFuncaoSiTefInterativo and CorrespondenteBancarioSiTefInterativo). The format of this field is Following:

{<Feature1>;<Feature2>;...;<Featuren>;};

Note that in this format the features are enclosed in braces ('{' and '}'), while constraints are enclosed in square brackets ('[' and ']').

Example: in the sales process exemplified in item 5.1, suppose that the sales value can be changed during the flow, and that the sales application automation wants to carry out its treatment, then the value of the parameter "ParamAdic" should be:

[10;17;18;19;27;28;34;35;];{TrataPagamentoExtendido=1;}

Next, we describe the functionalities provided in this field.

Functionality	Description
Customer Code=xxxxxx	Customer code for a given store, limited to 36 characters, to be linked in SiTef Web reports.
ExecutaAteLeituraCartao=0	If a .CHA key file is present on the Sitef server, then CliSiTef behaves as follows: If CliSiTef is not communicating with Sitef, instead of returning a communication error, CliSiTef continues the transaction flow until card reading. To inhibit this behavior, use the functionality below.
HabilitaVendaViaCodigoBarras=1	This parameter informs CliSiTef that the option of selling credit through cards engraved in bar codes must be enabled in the current transaction. Remembering that in addition to this configuration, the menu option (3025) must also be enabled.
ItemMenuIdentificado=1	The automation application informs CliSiTef that it is prepared to handle the menu command with identified items (command 42).
	When this parameter is enabled, CliSiTef replaces the use of command 21 with command 42, in most menus used in navigation.
{MKRede=A,B,C,D}	Configuration valid only for CliSiTef Reduced Redecard.
NOTE: This configuration must be passed between curly braces ({}) separately, that is, it must not be concatenated with any other configuration separated by a semicolon (;)	Parameters A,B,C,D are key indices Redecard encryption at POS's. These parameters will override the key indexes received in service 3. Parameters C and D will only be implemented from version (4.0.104.1, to be confirmed). If any key is not configured, the parameter must be passed with a value of -1. Example: {MKRede=-1,-1,-1,2} will configure only the key related to DUKPT 3DES encryption.
	A = DES master key index
	B = 3DES master key index
	C = DUKPT DES treatment record index
	D = DUKPT 3DES treatment record index
{MKRedeDados=A,B,C,D}	Same as MKRede (See description above),
NOTE: This configuration must be passed in braces ({}) separately, that is, it must not be concatenated with any other configuration separated by semicolons (;)	except that the encryption keys will be used to encrypt tracks.
NumCartaoCripto=<Encrypted card>	Providing the additional field “NumCartaoCripto”, with the encrypted card, disables the capture of the entered card number. This parameter depends on the correct configuration of the .cha key file on the SiTef server, that is, with the corresponding encryption keys.
RedeDestino=nnnn	This configuration allows you to force the transaction to be carried out by a specific network (nnnn = 4 numeric digits). See item 0 - Credit/debit transactions with a card without BIN.
TrataConsultaSaqueComSaque=1	Initially designed for Banco Ibi transactions, this parameter allows you to link, in a single transaction, the “Withdrawal Consultation” and “Withdrawal”.
	If this parameter is passed, the administrative menu will only offer the option “Withdrawal Consultation”.
TrataPagamentoExtendido=1	This function informs that the automation application is prepared to handle minor receipt information (no balance to be received with another form of payment) or excess (change must be returned to the customer).
	This function also enables the receipt of fields 137 (Balance to be paid) and 138 (Amount actually received).
ValidadeCartao=<AAMM or MMAA>	Delivering the additional field “ValidadeCartao”, with the card's expiration date, disables its capture, however the use of the value passed through the additional parameter is conditioned on the successful passage of the field “ NumCartaoCrypto”.
ValorIncluiTaxa=1	This parameter informs that the automation application included the value of the boarding or service tax in the purchase price.
	If a fee is requested during the capture flow, the value that was added to the sale must be passed on by the automation.
FiscalDocType=x	Indicates the type of Tax Document issued by “Commercial Automation”.
	Where x:
	0 - Tax Coupon (Tax Coupon - Legacy)
	1 - NFC-e (Consumer Invoice - Electronic)
	2 – SAT-CF-e (Tax Coupon - Electronic)
	NOTE: . In the absence of this “functionality”, CliSiTef assumes that the “Tax Document” issued is of type ‘0’ (Tax Coupon - Legacy).
	. Any value of 'x' different from those defined, the transaction will be aborted by CliSiTef indicating invalid parameters.
ChaveAcessoDocFiscal=<Key data>	Electronic Tax Document access key (size 44 digits). It is necessary to inform when “TipoDocFiscal” is equal to ‘1’ or ‘2’.
	NOTE: . In the absence of this “functionality” for “TipoDocFiscal” equal to ‘1’ or ‘2’, or in the presence of the “functionality” for “TipoDocFiscal” equal to ‘0’, the transaction will be aborted by CliSiTef indicating invalid parameters.
	Examples:
	{TipoDocFiscal=0}
	{TypeDocFiscal=1;ChaveAcessoDocFiscal=1111111111222222222233333333334444}
	{TypeDocFiscal=2;ChaveAcessoDocFiscal=5555555555666666666677777777778888}
CPFColetado=XXXXXXXXXXX	The default collection of the CPF is carried out by PinPad, when requested in the transaction. If the commercial automation has already captured it previously, or already has it for some reason, and does not want the user to have to re-enter the data on the pinpad, it must be passed via additional parameters.
	Initially intended for use with Digital Wallets, the need for use with other products arose.
	Example:
	{CPFColetado=99966633300;}
	SPLITPAY:Estab1=Amount1
	IMPORTANT: The main seller's establishment code must not be part of the Split establishments, which must only contain data from secondary sellers.
	The establishment code must be a valid CNPJ of maximum 15 digits, and the value, 12 digits, considering the last 2 digits as decimal places. Smaller fields will be completed with leading zeros. Formatted fields will only be considered digits. The associated value is optional.
	The character ‘|’ serves as a separator when there are several sets of data.
	Examples:
	{SPLITPAY:1222555000101=500|111222111000101=000000001000|111.222.333/0001-01=15,00|111.222.444/0001-01;};