Retail ISO8583 Profile

Encapsulates specific settings required for real-time transaction processing. Adds specific fields to the base fields of Billing Profile and Retail Profile.

A code that identifies the institution receiving the request. This ID is used when it is not possible to route a message using the Account Number field. When this field is included, it takes precedence over all account number fields for routing.

Identification number of the sub-merchant for merchant's aggregator.

Aggregator Name

Header element of the application.

Unique application identification number.

Short information about the application used for transaction.

Datawire ID of the card rental.

A code that identifies the type of business or services conducted by the service establishment.

On a 0400 (Debit/EBT) reversal message, this field must match the original 0200 (Debit/EBT) request.

Contains a code assigned to a merchant location. Merchants must use the First Data-assigned Merchant ID. The Merchant ID does not
conform to the standard definition of alphanumeric fields: it is right-justified and zero-filled on the left.

On a 0100 VRU Authorization only, the Merchant ID can be the First Data internal number or a merchant external number.

On a 0400 reversal message, this field must match the original 0100/0200 request.

Settlement 80 byte Merchant number. (Used in FirstData OmniPay)

Contains a code that identifies a merchant terminal. A unique code must be assigned to each terminal/POS device (e.g., a register) in a merchant location.
This code will be returned on the host response. In certain instances, the Terminal ID may be assigned by the merchant; in other instances, First Data assigns it.

The Terminal ID does not conform to the standard definition of alphanumeric fields: it is right justified and zero-filled on the left.

On a 0400 reversal message, this field must match the original 0100/0200 request

The Charge Descriptions are agreed upon by the client and American Express, at the time the Electronic Submission Addendum is completed.

The check digits is a validation character associated with the message authentication working key. The check digit is used to distinguish a MAC synch (31) reversal error from a MAC verification (30) reversal error when MAC authentication fails.

Country code of the merchant.
Needs to state 3 digit alpha-numeric country code.

Service phone of the customer used for discussing any processing issues.

Delivery point code assigned by a processor.

Dynamic merchant city address.

Dynamic merchant mailing country code.

Dynamic merchant name.

Dynamic merchant mailing state code.

Dynamic merchant street address.

Dynamic merchant's mailing address ZIP or postal code.

Dynamic sub-merchant identification number.

Merchant's connection URL used for e-commerce transactions processing.

Specific identifier of the ecommerce industry profile assigned by a processor.

Datawire ID of the e-commerce.

A code that identifies the type of business or services conducted by the service establishment.

On a 0400 (Debit/EBT) reversal message, this field must match the original 0200 (Debit/EBT) request.

Contains a code assigned to a merchant location. Merchants must use the First Data-assigned Merchant ID. The Merchant ID does not
conform to the standard definition of alphanumeric fields: it is right-justified and zero-filled on the left.

On a 0100 VRU Authorization only, the Merchant ID can be the First Data internal number or a merchant external number.

On a 0400 reversal message, this field must match the original 0100/0200 request.

Settlement 80 byte Merchant number. (Used in FirstData OmniPay)

Contains a code that identifies a merchant terminal. A unique code must be assigned to each terminal/POS device (e.g., a register) in a merchant location.
This code will be returned on the host response. In certain instances, the Terminal ID may be assigned by the merchant; in other instances, First Data assigns it.

The Terminal ID does not conform to the standard definition of alphanumeric fields: it is right justified and zero-filled on the left.

On a 0400 reversal message, this field must match the original 0100/0200 request

Email address of the provider.

Name of the file.

Header Merchant ID.

Indicates that this transaction should be processed in test mode, when it is handled by the processor.

Key Serial Number.

Base Derivation Key ID (BDK ID) (If fewer than nine positions, pad on
LEFT with ‘F’s.)

Terminal Lane Number.

MasterCard regulations mandate that each POS device have a unique terminal identifier. This value is forwarded to MasterCard as the terminal identifier.

Datawire ID of lodging.

A code that identifies the type of business or services conducted by the service establishment.

On a 0400 (Debit/EBT) reversal message, this field must match the original 0200 (Debit/EBT) request.

Contains a code assigned to a merchant location. Merchants must use the First Data-assigned Merchant ID. The Merchant ID does not
conform to the standard definition of alphanumeric fields: it is right-justified and zero-filled on the left.

On a 0100 VRU Authorization only, the Merchant ID can be the First Data internal number or a merchant external number.

On a 0400 reversal message, this field must match the original 0100/0200 request.

Settlement 80 byte Merchant number. (Used in FirstData OmniPay)

Contains a code that identifies a merchant terminal. A unique code must be assigned to each terminal/POS device (e.g., a register) in a merchant location.
This code will be returned on the host response. In certain instances, the Terminal ID may be assigned by the merchant; in other instances, First Data assigns it.

The Terminal ID does not conform to the standard definition of alphanumeric fields: it is right justified and zero-filled on the left.

On a 0400 reversal message, this field must match the original 0100/0200 request

An identifier assigned by MasterCard to identify a specific merchant who is registered with MasterCard for specific fees, special interchange treatment, or participation in select acceptance programs.

BIN accosiated with MasterCard cards.

City associated with this merchant account.

Code of the country associated with this merchant account.

Merchant Email

Merchant Food and Nutrition Service Number.

FNS Number: A seven-digit merchant number issued by the US Department of Agriculture Food and Nutrition Service that is used in EBT Food Stamps. This number must authorize merchants who wish to accept food stamp.

Note: If not supplied, space-fill so number can be obtained from First Data Terminal Control file.

Identifier of the merchant group.

The DBA name of the merchant.

Abbreviation of the merchant's full name.

Identifier of the merchant assigned by a processor.

State code associated with this merchant account.

Street address associated with this merchant account.

Tax identifier of the merchant.

ZIP/Postal code associated with this merchant account.

Specific identifier of the MOTO industry profile assigned by a processor.

Datawire ID of the MOTO.

A code that identifies the type of business or services conducted by the service establishment.

On a 0400 (Debit/EBT) reversal message, this field must match the original 0200 (Debit/EBT) request.

Contains a code assigned to a merchant location. Merchants must use the First Data-assigned Merchant ID. The Merchant ID does not
conform to the standard definition of alphanumeric fields: it is right-justified and zero-filled on the left.

On a 0100 VRU Authorization only, the Merchant ID can be the First Data internal number or a merchant external number.

On a 0400 reversal message, this field must match the original 0100/0200 request.

Settlement 80 byte Merchant number. (Used in FirstData OmniPay)

Contains a code that identifies a merchant terminal. A unique code must be assigned to each terminal/POS device (e.g., a register) in a merchant location.
This code will be returned on the host response. In certain instances, the Terminal ID may be assigned by the merchant; in other instances, First Data assigns it.

The Terminal ID does not conform to the standard definition of alphanumeric fields: it is right justified and zero-filled on the left.

On a 0400 reversal message, this field must match the original 0100/0200 request

Zeros filled in the request message, debit Network ID will be included as response values.

Password associated with the appropriate username.

Specific identifier of the pertoleum industry profile assigned by a processor.

Datawire ID of the petroleum industry.

A code that identifies the type of business or services conducted by the service establishment.

On a 0400 (Debit/EBT) reversal message, this field must match the original 0200 (Debit/EBT) request.

Contains a code assigned to a merchant location. Merchants must use the First Data-assigned Merchant ID. The Merchant ID does not
conform to the standard definition of alphanumeric fields: it is right-justified and zero-filled on the left.

On a 0100 VRU Authorization only, the Merchant ID can be the First Data internal number or a merchant external number.

On a 0400 reversal message, this field must match the original 0100/0200 request.

Settlement 80 byte Merchant number. (Used in FirstData OmniPay)

Contains a code that identifies a merchant terminal. A unique code must be assigned to each terminal/POS device (e.g., a register) in a merchant location.
This code will be returned on the host response. In certain instances, the Terminal ID may be assigned by the merchant; in other instances, First Data assigns it.

The Terminal ID does not conform to the standard definition of alphanumeric fields: it is right justified and zero-filled on the left.

On a 0400 reversal message, this field must match the original 0100/0200 request

Mode of the processing.

Building number of the processor's mailing address.

City of the processor's mailing address.

Enumerates possible values of ISO8583 Profile.

Country code of the processor's mailing address.

Identification number of the processor.

Name associated with the processor profile.

Phone number of the processor for discussing any processing issues.

Street of the processor's mailing address.

ZIP/postal code of the processor's mailing address.

Specific identifier of the restaurant industry profile assigned by a processor.

Datawire ID of the restaurant.

A code that identifies the type of business or services conducted by the service establishment.

On a 0400 (Debit/EBT) reversal message, this field must match the original 0200 (Debit/EBT) request.

Contains a code assigned to a merchant location. Merchants must use the First Data-assigned Merchant ID. The Merchant ID does not
conform to the standard definition of alphanumeric fields: it is right-justified and zero-filled on the left.

On a 0100 VRU Authorization only, the Merchant ID can be the First Data internal number or a merchant external number.

On a 0400 reversal message, this field must match the original 0100/0200 request.

Settlement 80 byte Merchant number. (Used in FirstData OmniPay)

Contains a code that identifies a merchant terminal. A unique code must be assigned to each terminal/POS device (e.g., a register) in a merchant location.
This code will be returned on the host response. In certain instances, the Terminal ID may be assigned by the merchant; in other instances, First Data assigns it.

The Terminal ID does not conform to the standard definition of alphanumeric fields: it is right justified and zero-filled on the left.

On a 0400 reversal message, this field must match the original 0100/0200 request

Specific identifier of the retail industry profile assigned by a processor.

Datawire ID of the retail industry.

A code that identifies the type of business or services conducted by the service establishment.

On a 0400 (Debit/EBT) reversal message, this field must match the original 0200 (Debit/EBT) request.

Contains a code assigned to a merchant location. Merchants must use the First Data-assigned Merchant ID. The Merchant ID does not
conform to the standard definition of alphanumeric fields: it is right-justified and zero-filled on the left.

On a 0100 VRU Authorization only, the Merchant ID can be the First Data internal number or a merchant external number.

On a 0400 reversal message, this field must match the original 0100/0200 request.

Settlement 80 byte Merchant number. (Used in FirstData OmniPay)

Contains a code that identifies a merchant terminal. A unique code must be assigned to each terminal/POS device (e.g., a register) in a merchant location.
This code will be returned on the host response. In certain instances, the Terminal ID may be assigned by the merchant; in other instances, First Data assigns it.

Unique secure code.

Digital number that represents the specific code of the product/service.

Type of the terminal used for the transaction.

Identification number of the token requestor.

Type of the token code.

Third Party Processor ID - The TPP ID is mandatory on all Authorization requests submitted by Third Parties who have been issued one by First Data. If you were assigned a Third Party Processor ID, you are required to send this additional format record.
If you were not assigned a Third Party Processor ID, this record should not be sent.

Identification number of the key in TransArmor.

Type of the token for TransArmor.

File header that contains Transaction Code, PSP Name, File Creation Date, File Reference, File Identification and Test/Prod Identifier.

Name of the user in the system.

BIN accosiated with Visa cards.

An identifier assigned by Visa to identify a merchant who is registered with Visa for specific fees, special interchange treatment, or participation in select acceptance programs.