Sub-Adquering Information

This field will be used by automations that use a provider's sub-acquiring service.
in sales transactions and the format of this field follows the TLV format (Tag, Length, Value – Identifier,
Size, Value), as follows:

<Id1><Tam1><Val1><Id2><Tam2><Val2>...<IdN><TamN><ValN>, where:
<id> - 2-byte field identifier, according to values ​​defined in
table below.
<size> - field size of 2 bytes.
<val> - field value.

Tag (Id)FormatMaximum SizeField
00Alphanumeric22Trade name
01Alphanumeric40Address
02Alphanumeric13City
03Alphanumeric2UF
04Alphanumeric3Country
05Numeric8ZIP code
06Numeric4MCC
07Numeric14EndCNPJ/CPFereço
08Numeric11Telephone
09Alphanumeric22Software
Descriptor
Ex: [0016SOFTWARE EXPRESS0122AVENIDA PAULISTA, 22020209SAO PAULO0302SP]

In the example above, the following fields were passed:

  • 00 (Invented name) with size 16 and value equal to SOFTWARE EXPRESS;
  • 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 noting that if any of the fields defined for a given acquirer is not passed through commercial automation, it will be sent blank to the authorizer. The list of which fields must be sent may vary from acquirer to acquirer.


Did this page help you?