FirstDataOmnipayCardsRealtimeProviderProfile
Avalible Field Groups:
Available Fields:
merchantCategoryCodeRetail
merchantIdRetail
merchantNumberRetail
terminalIdRetail
datawireIdRetail
merchantCategoryCodeMoto
merchantIdMoto
merchantNumberMoto
terminalIdMoto
datawireIdMoto
merchantCategoryCodeEcommerce
merchantIdEcommerce
merchantNumberEcommerce
terminalIdEcommerce
datawireIdEcommerce
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.
On a 0400 (Debit/EBT) reversal message, this field must match the original 0200 (Debit/EBT) request.
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.
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(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Retail Merchant Number
Attributes:
Settlement 80 byte Merchant number. (Used in FirstData OmniPay)
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.
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
Group: Settings
SubGroup: Retail
Type: String(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Retail Datawire ID
Attributes:
Datawire ID of the retail industry.
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.
On a 0400 (Debit/EBT) reversal message, this field must match the original 0200 (Debit/EBT) request.
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.
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(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Moto Merchant Number
Attributes:
Settlement 80 byte Merchant number. (Used in FirstData OmniPay)
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
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
Group: Settings
SubGroup: MOTO
Type: String(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Moto Datawire ID
Attributes:
Datawire ID of the MOTO.
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.
On a 0400 (Debit/EBT) reversal message, this field must match the original 0200 (Debit/EBT) request.
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.
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(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Ecommerce Merchant Number
Attributes:
Settlement 80 byte Merchant number. (Used in FirstData OmniPay)
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
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
Group: Settings
SubGroup: eCommerce
Type: String(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Ecommerce Datawire ID
Attributes:
Datawire ID of the e-commerce.
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.0126 | 738496 | include( '/var/www/html/unidoc/profile.php' ) | .../index.php:327 |
| 3 | 0.9151 | 1416232 | toSample( ) | .../profile.php:859 |
| 4 | 0.9151 | 1416608 | loadFields( ) | .../profile.php:76 |
| 5 | 0.9154 | 1417344 | 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.