FirstDataNashvilleCardsRealtimeProviderProfile

Type:  Struct
Abstract:  no
Status:  Active
Configuration settings for Cards Realtime processing through FirstData Nashville.
merchantCategoryCodeRetail
Group: Settings
SubGroup: Retail
Type: String(4)
XML Representation: attribute
References: Retail ISO8583 Profile.Retail Merchant Category Code
Attributes:
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.
merchantIdRetail
Group: Settings
SubGroup: Retail
Type: String(22)
XML Representation: attribute
References: Retail ISO8583 Profile.Retail Merchant ID
Attributes:
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.
terminalIdRetail    
Group: Settings
SubGroup: Retail
Type: String(12)
XML Representation: attribute
References: Retail ISO8583 Profile.Retail Terminal ID
Attributes:
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

Terminal override field.
For this processor, this field corresponds to the field Processor Terminal ID. If terminal processing is supported with this integration, the value of this field will be taken from Terminal table.
datawireIdRetail
Group: Settings
SubGroup: Retail
Type: String(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Retail Datawire ID
Attributes:
Datawire ID of the retail industry.
merchantCategoryCodeMoto
Group: Settings
SubGroup: MOTO
Type: String(4)
XML Representation: attribute
References: Retail ISO8583 Profile.Moto Merchant Category Code
Attributes:
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.
merchantIdMoto
Group: Settings
SubGroup: MOTO
Type: String(22)
XML Representation: attribute
References: Retail ISO8583 Profile.Moto Merchant ID
Attributes:
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.
terminalIdMoto    
Group: Settings
SubGroup: MOTO
Type: String(12)
XML Representation: attribute
References: Retail ISO8583 Profile.Moto Terminal ID
Attributes:
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
Terminal override field.
For this processor, this field corresponds to the field Processor Terminal ID. If terminal processing is supported with this integration, the value of this field will be taken from Terminal table.
datawireIdMoto
Group: Settings
SubGroup: MOTO
Type: String(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Moto Datawire ID
Attributes:
Datawire ID of the MOTO.
merchantCategoryCodeEcommerce
Group: Settings
SubGroup: eCommerce
Type: String(4)
XML Representation: attribute
References: Retail ISO8583 Profile.Ecommerce Merchant Category Code
Attributes:
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.
merchantIdEcommerce
Group: Settings
SubGroup: eCommerce
Type: String(22)
XML Representation: attribute
References: Retail ISO8583 Profile.Ecommerce Merchant ID
Attributes:
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.
terminalIdEcommerce    
Group: Settings
SubGroup: eCommerce
Type: String(12)
XML Representation: attribute
References: Retail ISO8583 Profile.Ecommerce Terminal ID
Attributes:
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
Terminal override field.
For this processor, this field corresponds to the field Processor Terminal ID. If terminal processing is supported with this integration, the value of this field will be taken from Terminal table.
datawireIdEcommerce
Group: Settings
SubGroup: eCommerce
Type: String(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Ecommerce Datawire ID
Attributes:
Datawire ID of the e-commerce.
urlEcommerce
Group: Settings
SubGroup: eCommerce
Type: String(32)
XML Representation: attribute
References: Retail ISO8583 Profile.Ecomm Url
Attributes:
Merchant's connection URL used for e-commerce transactions processing.
merchantCategoryCodeRestaurant
Group: Settings
SubGroup: Restaurant
Type: String(4)
XML Representation: attribute
References: Retail ISO8583 Profile.Restaurant Merchant Category Code
Attributes:
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.
merchantIdRestaurant
Group: Settings
SubGroup: Restaurant
Type: String(22)
XML Representation: attribute
References: Retail ISO8583 Profile.Restaurant Merchant ID
Attributes:
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.
terminalIdRestaurant    
Group: Settings
SubGroup: Restaurant
Type: String(12)
XML Representation: attribute
References: Retail ISO8583 Profile.Restaurant Terminal ID
Attributes:
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
Terminal override field.
For this processor, this field corresponds to the field Processor Terminal ID. If terminal processing is supported with this integration, the value of this field will be taken from Terminal table.
datawireIdRestaurant
Group: Settings
SubGroup: Restaurant
Type: String(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Restaurant Datawire ID
Attributes:
Datawire ID of the restaurant.
merchantCategoryCodeLodging
Group: Settings
SubGroup: Lodging
Type: String(4)
XML Representation: attribute
References: Retail ISO8583 Profile.Lodging Merchant Category Code
Attributes:
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.
merchantIdLodging
Group: Settings
SubGroup: Lodging
Type: String(22)
XML Representation: attribute
References: Retail ISO8583 Profile.Lodging Merchant ID
Attributes:
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.
terminalIdLodging    
Group: Settings
SubGroup: Lodging
Type: String(12)
XML Representation: attribute
References: Retail ISO8583 Profile.Lodging Terminal ID
Attributes:
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
Terminal override field.
For this processor, this field corresponds to the field Processor Terminal ID. If terminal processing is supported with this integration, the value of this field will be taken from Terminal table.
datawireIdLodging
Group: Settings
SubGroup: Lodging
Type: String(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Lodging Datawire ID
Attributes:
Datawire ID of lodging.
merchantCategoryCodeCarRental
Group: Settings
SubGroup: Car Rental
Type: String(4)
XML Representation: attribute
References: Retail ISO8583 Profile.Car Rental Merchant Category Code
Attributes:
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.
merchantIdCarRental
Group: Settings
SubGroup: Car Rental
Type: String(22)
XML Representation: attribute
References: Retail ISO8583 Profile.Car Rental Merchant ID
Attributes:
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.
terminalIdCarRental    
Group: Settings
SubGroup: Car Rental
Type: String(12)
XML Representation: attribute
References: Retail ISO8583 Profile.Car Rental Terminal ID
Attributes:
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
Terminal override field.
For this processor, this field corresponds to the field Processor Terminal ID. If terminal processing is supported with this integration, the value of this field will be taken from Terminal table.
datawireIdCarRental
Group: Settings
SubGroup: Car Rental
Type: String(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Car Rental Datawire ID
Attributes:
Datawire ID of the card rental.

XML Sample:


( ! ) Warning: mysql_fetch_array() expects parameter 1 to be resource, boolean given in /var/www/html/unidoc/profile.php on line 31
Call Stack
#TimeMemoryFunctionLocation
10.0008323296{main}( ).../index.php:0
20.0125738496include( '/var/www/html/unidoc/profile.php' ).../index.php:327
31.13311503200toSample( ).../profile.php:859
41.13311503576loadFields( ).../profile.php:76
51.13351504312mysql_fetch_array ( ).../profile.php:31
<profile/>

"<profile/>"

JSON Sample:

{
 
}

XURL Sample:

?