DirectAmexCardsRealtimeProviderProfile

Type:  Struct
Abstract:  no
Status:  Active
Configuration settings for cards realtime processing through Amex directly
merchantCategoryCodeRetail
Group: Settings
SubGroup: Retail
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Retail Merchant Category Code
Attributes: Default: 4569
Default Value: 4569
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
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.
merchantCategoryCodeMoto
Group: Settings
SubGroup: MOTO
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Moto Merchant Category Code
Attributes: Default: 1111
Default Value: 1111
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.


Moto Merchant Category Code
merchantIdMoto
Group: Settings
SubGroup: MOTO
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Moto Merchant ID
Attributes: Default: motoId123
Default Value: motoId123
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.
merchantCategoryCodeEcommerce
Group: Settings
SubGroup: eCommerce
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Ecommerce Merchant Category Code
Attributes: Default: 2222
Default Value: 2222
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
XML Representation: attribute
References: Retail ISO8583 Profile.Ecommerce Merchant ID
Attributes: Default: ecommerceId123
Default Value: ecommerceId123
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.
merchantCategoryCodeRestaurant
Group: Settings
SubGroup: Restaurant
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Restaurant Merchant Category Code
Attributes: Default: 3333
Default Value: 3333
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
XML Representation: attribute
References: Retail ISO8583 Profile.Restaurant Merchant ID
Attributes: Default: restaurantId123
Default Value: restaurantId123
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.

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.0009323296{main}( ).../index.php:0
20.0116738496include( '/var/www/html/unidoc/profile.php' ).../index.php:327
30.63221359104toSample( ).../profile.php:859
40.63221359480loadFields( ).../profile.php:76
50.63251360216mysql_fetch_array ( ).../profile.php:31
<profile/>

"<profile/>"

JSON Sample:

{
 
}

XURL Sample:

?