WorldPayCardsRealtimeProviderProfile
Configuration settings for Cards Realtime processing through WorldPay.
Avalible Field Groups:
Available Fields:
type
isActive
accountProcessingPolicy
isCreditEnabled
merchantIdRetail
terminalIdRetail
retailCheckDigit
merchantIdMoto
terminalIdMoto
motoCheckDigit
merchantIdEcommerce
terminalIdEcommerce
ecommerceCheckDigit
merchantIdRestaurant
terminalIdRestaurant
restaurantCheckDigit
merchantIdPetroleum
terminalIdPetroleum
petroleumCheckDigit
connectionType
host
port
Group: System
SubGroup:
Type: String
XML Representation: attribute
Attributes:
Constant, Required, Default: cards-realtime/worldpay
Default Value: cards-realtime/worldpay
Group: System
SubGroup:
Type: Boolean
XML Representation: attribute
References: Processing Profile.Is Active
Attributes:
Default: true
Default Value: true
Indicates whether the record is active in the system.
Group: System
SubGroup:
Type: String(10)
XML Representation: attribute
References: Processing Profile.Account Processing Policy
Attributes:
Required, Default: VMXD——*U
Default Value: VMXD——*U
Type of processing policy for the account.
Group: System
SubGroup:
Type: Boolean
XML Representation: attribute
References: Processing Profile.Is Credit Enabled
Attributes:
Default: true
Default Value: true
Indicates whether the credit operation is allowed.
Group: Settings
SubGroup: Retail
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Retail Merchant ID
Attributes:
Default: 658999456654
Default Value: 658999456654
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: 66548787
Default Value: 66548787
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 Check Digit
Attributes:
Default: 1
Default Value: 1
Specific identifier of the retail industry profile assigned by a processor.
Group: Settings
SubGroup: MOTO
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Moto Merchant ID
Attributes:
Default: 658999456654
Default Value: 658999456654
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: 66548787
Default Value: 66548787
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 Check Digit
Attributes:
Default: 1
Default Value: 1
Specific identifier of the MOTO industry profile assigned by a processor.
Group: Settings
SubGroup: eCommerce
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Ecommerce Merchant ID
Attributes:
Default: 658999456654
Default Value: 658999456654
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: 66548787
Default Value: 66548787
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 Check Digit
Attributes:
Default: 1
Default Value: 1
Specific identifier of the ecommerce industry profile assigned by a processor.
Group: Settings
SubGroup: Restaurant
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Restaurant Merchant ID
Attributes:
Default: 658999456654
Default Value: 658999456654
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: 66548787
Default Value: 66548787
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 Check Digit
Attributes:
Default: 1
Default Value: 1
Specific identifier of the restaurant industry profile assigned by a processor.
Group: Settings
SubGroup: Petroleum
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Petroleum Merchant ID
Attributes:
Default: 658999456654
Default Value: 658999456654
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: 66548787
Default Value: 66548787
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 Check Digit
Attributes:
Default: 1
Default Value: 1
Specific identifier of the pertoleum industry profile assigned by a processor.
Group: Authorization
SubGroup:
Type: String
XML Representation: attribute
References: Provider Account.Primary Connection Type
Attributes:
Constant, Default: WP
Default Value: WP
Type of connectivity to use to exchange messages/files with a processor.
Group: Authorization
SubGroup:
Type: String
XML Representation: attribute
References: Provider Account.Http Host
Attributes:
Required, Default: https://tpdev.lynksystems.com:6661
Default Value: https://tpdev.lynksystems.com:6661
Host to be used for HTTPs based connectivity.
Group: Authorization
SubGroup:
Type: Integer
XML Representation: attribute
References: Provider Account.HTTP Port
Attributes:
Required, Default: 6661
Default Value: 6661
Port to be used for HTTPs based connectivity.
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.0004 | 323064 | {main}( ) | .../index.php:0 |
| 2 | 0.0046 | 727968 | include( '/var/www/html/unidoc/profile.php' ) | .../index.php:327 |
| 3 | 1.1452 | 1466416 | toSample( ) | .../profile.php:879 |
| 4 | 1.1452 | 1466792 | loadFields( ) | .../profile.php:76 |
| 5 | 1.1453 | 1467528 | mysql_fetch_array ( ) | .../profile.php:31 |
<profile/>"<profile/>"
JSON Sample:
{ }
XURL Sample:
?
Copyright ©
TidyPay. 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.