ElavonEUCardsRealtimeProviderProfile
Configuration settings for Cards Realtime processing through ElavonEU.
Avalible Field Groups:
authorizationCurrencyCode
captureCurrencyCode
merchantIdRetail
terminalIdRetail
merchantIdMoto
terminalIdMoto
merchantIdEcommerce
terminalIdEcommerce
merchantIdLodging
terminalIdLodging
Group: Settings
SubGroup:
Type: String(3)
XML Representation: attribute
References: Processing Profile.Authorization Currency Code CL
Attributes:
Required, Default: EUR
Default Value: EUR
Pattern:
ALPHA
Represents the type of currency used for authorization.
Group: Settings
SubGroup:
Type: String(3)
XML Representation: attribute
References: Processing Profile.Capture Currency Code CL
Attributes:
Required, Default: EUR
Default Value: EUR
Pattern:
ALPHA
Represents the type of currency used for capture.
Group: Settings
SubGroup: Retail
Type: String(22)
XML Representation: attribute
References: Retail ISO8583 Profile.Retail Merchant ID
Attributes:
Pattern:
ALPHANUMERIC
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(12)
XML Representation: attribute
References: Retail ISO8583 Profile.Retail Terminal ID
Attributes:
Pattern:
ALPHANUMERIC
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: MOTO
Type: String(22)
XML Representation: attribute
References: Retail ISO8583 Profile.Moto Merchant ID
Attributes:
Pattern:
ALPHANUMERIC
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(12)
XML Representation: attribute
References: Retail ISO8583 Profile.Moto Terminal ID
Attributes:
Pattern:
ALPHANUMERIC
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(22)
XML Representation: attribute
References: Retail ISO8583 Profile.Ecommerce Merchant ID
Attributes:
Pattern:
ALPHANUMERIC
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(12)
XML Representation: attribute
References: Retail ISO8583 Profile.Ecommerce Terminal ID
Attributes:
Pattern:
ALPHANUMERIC
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: Lodging
Type: String(22)
XML Representation: attribute
References: Retail ISO8583 Profile.Lodging Merchant ID
Attributes:
Pattern:
ALPHANUMERIC
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: Lodging
Type: String(12)
XML Representation: attribute
References: Retail ISO8583 Profile.Lodging Terminal ID
Attributes:
Pattern:
ALPHANUMERIC
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.
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.0009 | 323296 | {main}( ) | .../index.php:0 |
| 2 | 0.0115 | 738496 | include( '/var/www/html/unidoc/profile.php' ) | .../index.php:327 |
| 3 | 0.6346 | 1376456 | toSample( ) | .../profile.php:859 |
| 4 | 0.6346 | 1376832 | loadFields( ) | .../profile.php:76 |
| 5 | 0.6350 | 1377568 | 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.