FirstDataBuyPassCardsRealtimeProviderProfile
Configuration settings for Cards Realtime processing through FirstData BuyPass.
Avalible Field Groups:
merchantIdRetail
terminalIdRetail
datawireIdRetail
merchantIdMoto
terminalIdMoto
datawireIdMoto
merchantIdEcommerce
terminalIdEcommerce
datawireIdEcommerce
merchantIdRestaurant
terminalIdRestaurant
datawireIdRestaurant
merchantIdPetroleum
terminalIdPetroleum
datawireIdPetroleum
Group: Settings
SubGroup: Retail
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Retail Merchant ID
Attributes:
Default: 654888
Default Value: 654888
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.
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.
Group: Settings
SubGroup: Retail
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Retail Terminal ID
Attributes:
Default: A1
Default Value: A1
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.
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.
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.
Group: Settings
SubGroup: Retail
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Retail Datawire ID
Attributes:
Default: 00010793427311253266
Default Value: 00010793427311253266
Datawire ID of the retail industry.
Group: Settings
SubGroup: MOTO
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Moto Merchant ID
Attributes:
Default: 654888
Default Value: 654888
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.
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.
Group: Settings
SubGroup: MOTO
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Moto Terminal ID
Attributes:
Default: A1
Default Value: A1
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
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.
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.
Group: Settings
SubGroup: MOTO
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Moto Datawire ID
Attributes:
Default: 00010793427311253266
Default Value: 00010793427311253266
Datawire ID of the MOTO.
Group: Settings
SubGroup: eCommerce
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Ecommerce Merchant ID
Attributes:
Default: 654888
Default Value: 654888
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.
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.
Group: Settings
SubGroup: eCommerce
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Ecommerce Terminal ID
Attributes:
Default: A1
Default Value: A1
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
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.
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.
Group: Settings
SubGroup: eCommerce
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Ecommerce Datawire ID
Attributes:
Default: 00010793427311253266
Default Value: 00010793427311253266
Datawire ID of the e-commerce.
Group: Settings
SubGroup: Restaurant
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Restaurant Merchant ID
Attributes:
Default: 654888
Default Value: 654888
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.
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.
Group: Settings
SubGroup: Restaurant
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Restaurant Terminal ID
Attributes:
Default: A1
Default Value: A1
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
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.
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.
Group: Settings
SubGroup: Restaurant
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Restaurant Datawire ID
Attributes:
Default: 00010793427311253266
Default Value: 00010793427311253266
Datawire ID of the restaurant.
Group: Settings
SubGroup: Petroleum
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Petroleum Merchant ID
Attributes:
Default: 654888
Default Value: 654888
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.
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.
Group: Settings
SubGroup: Petroleum
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Petroleum Terminal ID
Attributes:
Default: A1
Default Value: A1
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
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.
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.
Group: Settings
SubGroup: Petroleum
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Petroleum Datawire ID
Attributes:
Default: 00010793427311253266
Default Value: 00010793427311253266
Datawire ID of the petroleum industry.
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 | ||||
| # | Time | Memory | Function | Location |
| 1 | 0.0008 | 323296 | {main}( ) | .../index.php:0 |
| 2 | 0.0117 | 738496 | include( '/var/www/html/unidoc/profile.php' ) | .../index.php:327 |
| 3 | 0.6537 | 1418864 | toSample( ) | .../profile.php:859 |
| 4 | 0.6537 | 1419240 | loadFields( ) | .../profile.php:76 |
| 5 | 0.6540 | 1419976 | mysql_fetch_array ( ) | .../profile.php:31 |
<profile/>"<profile/>"
JSON Sample:
{ }
XURL Sample:
?
Copyright ©
MyntPay. All Rights Reserved.
All Logos and Trademarks used or mentioned on this page are copyrighted property of their respective owners and are used for display purposes only.