Description

For this solution it is necessary to use the routine ConfiguraIntSiTefInterativoEx, as the parameter will be used additional feature that does not exist in the ConfiguraIntSiTefInterativo routine

long ConfiguraIntSiTefInterativoEx (IPSiTef, IdStore, IdTerminal, Reserved, AdditionalParameters)

In the last parameter (AdditionalParameters) the following information must be sent:

[DadosSubAdquirencia=<SubAcquiringData>]

where

<DadosSubAdquirencia>=<Id1><Size1><Val1><Id2><Tam2><Val2>...<IdN><TamN><ValN>

• <id> - 2-byte field identifier, according to values ​​defined in the table below

• <size> - field size of 2 bytes.

• <val> - field value.

Tag	Format	Maximum Size	Field
00	Alphanumeric	22	Trade name (Merchant Name)
01	Alphanumeric	48	Address
02	Alphanumeric	13	City
03	Alphanumeric	2	UF
04	Alphanumeric	3	Country
05	Alphanumeric	10	Zip code
06	Numeric	4	MCC (Merchant Category Code)
07	Numeric	14	CNPJ/CPF
08	Numeric	11	Telephone
09	Alphanumeric	22	Id (Establishment Identification Code)
10	Alphanumeric	99	email
11	Alphanumeric	60	Corporate Name/Full Name
12	Alphanumeric	1	Person Type (F or J)
13	Alphanumeric	15	Facilitator Merchant ID NOTE: - This field does not refer to the data “Payment Facilitator ID”. These are different data. - At the moment, the “Facilitator Merchant ID” field is for the exclusive use of the PagSeguro network.

Below are presented 3 possible formatting models for the Trade Name field (tag 00) and the way in which it is composed is described, aiming to standardize this information:

SSS*NNNNNNNNNNNNNNNNNN

or SSSSSSSNNNNNNNNNNNNNN or SSSSSSSSSSSSNNNNNNNNNN

Where:

S = Identification of the sub-acquirer, which must be size 3, 7 or 12 and, necessarily, must be complemented with whites if necessary (based on one of the 3 possible models).

* = Mandatory separator in case of sub-acquirer

N = Name that will identify the establishment on the cardholder's invoice. Being extreme It is important that this information allows the establishment to be clearly identified on the customer's invoice, thus avoiding possible transaction fallback.

Remembering that the definition of the total field size is 22 positions, resulting in the following possible formatting: 318 or 714 or 12*9 (according to the models presented previously).

This standard, to be followed by the application, is necessary due to the different treatments of this information from authorizers.

Example:

[DadosSubAdquirencia=0022STL*SOFTWARE EXPRESS 0122AVENIDA PAULISTA, 22020209SAO PAULO0302SP]

In the example above, the following fields were passed (according to the standard “IDTAMVAL”):

• 00 (Trade name) with size 22 (default 318) and value equal to: “STL” (sub-acquirer identification), (separator) and “SOFTWARE EXPRESS” (Invented Name, with two blanks for size complement);
• 01 (Address) with size 22 and value equal to AVENIDA PAULISTA, 2202;
• 02 (City) with size 09 and value equal to SAO PAULO;
• 03 (UF) with size 02 and value equal to SP.

It is worth mentioning that if any of the defined fields is not passed through commercial automation, it will be sent with blanks to the authorizer. The list of which fields must be sent may vary depending on the acquirer for acquirer.