VantivCardsRealtimeProviderProfile
Configuration settings for cards realtime processing through Vantiv
Avalible Field Groups:
Available Fields:
type
isActive
accountProcessingPolicy
connectionMode
settlementMode
isDebitCardProcessingEnabled
isSettlementInitationRequired
isReferralDeclineSupported
acquirerInstitutionID
networkRouting
username
password
merchantIdRetail
terminalIdRetail
merchantIdMoto
terminalIdMoto
merchantIdEcommerce
terminalIdEcommerce
merchantIdRestaurant
terminalIdRestaurant
connectionType
host
port
creditProcessingMode
Group: System
SubGroup:
Type: String
XML Representation: attribute
References: Processing Profile.Type
Attributes:
Constant, Required, Default: cards-realtime/vantiv-tandem
Default Value: cards-realtime/vantiv-tandem
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: Configuration
SubGroup:
Type: String
XML Representation: attribute
References: Retail Profile.Connection Mode CL
Attributes:
Required, Default: true
Default Value: true
Represents the type of connection mode for this profile.
Group: Configuration
SubGroup:
Type: String
XML Representation: attribute
References: Retail Profile.Settlement Mode CL
Attributes:
Required
Represents the type of settlement mode for this profile.
Group: System
SubGroup:
Type: Boolean
XML Representation: attribute
References: Retail Profile.Is Debit Card Processing Enabled
Attributes:
Default: true
Default Value: true
Indicates whether debit cards processing is possible using this profile.
Group: System
SubGroup:
Type: Boolean
XML Representation: attribute
References: Retail Profile.Is Settlement Initiation Required
Attributes:
Default: true
Default Value: true
Indicates whether settlements have to be explicitly initiated by the gateway.
Group: System
SubGroup:
Type: Boolean
XML Representation: attribute
References: Retail Profile.Is Referral Decline Supported
Attributes:
Default: true
Default Value: true
Is Referral Decline Supported
Group: Payment Facilitator
SubGroup:
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Acquirer Institution ID
Attributes:
Required, Default: 2284
Default Value: 2284
A code that identifies the institution receiving the request. This ID is used when it is not possible to route a message using the Account Number field. When this field is included, it takes precedence over all account number fields for routing.
Group: Payment Facilitator
SubGroup:
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Network Routing
Attributes:
Required, Default: B90000
Default Value: B90000
Zeros filled in the request message, debit Network ID will be included as response values.
Group: Merchant
SubGroup:
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.User Name
Attributes:
Default: sampleUser
Default Value: sampleUser
Name of the user in the system.
Group: Merchant
SubGroup:
Type: String(100)
XML Representation: attribute
References: Retail ISO8583 Profile.Password
Attributes:
Encrypted
Password associated with the appropriate username.
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: 123
Default Value: 123
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
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: 123
Default Value: 123
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 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: 123
Default Value: 123
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 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: 123
Default Value: 123
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: Authorization
SubGroup:
Type: String
XML Representation: attribute
References: Provider Account.Primary Connection Type
Attributes:
Required, Default: VT_HTTPS
Default Value: VT_HTTPS
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://cert.ssl53.com/AUTH
Default Value: https://cert.ssl53.com/AUTH
Host to be used for HTTPs based connectivity.
Group: Authorization
SubGroup:
Type: Integer
XML Representation: attribute
References: Provider Account.HTTP Port
Attributes:
Required, Default: 443
Default Value: 443
Port to be used for HTTPs based connectivity.
Group: System
SubGroup:
Type: Enum
XML Representation: attribute
References: Retail Profile.Supported Credit Policy Cl
Attributes:
Required, Default: CR
Default Value: CR
Represents the type of credit policy supported for this profile.
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.0003 | 322568 | {main}( ) | .../index.php:0 |
| 2 | 0.0039 | 727504 | include( '/var/www/html/unidoc/profile.php' ) | .../index.php:327 |
| 3 | 1.1897 | 1483680 | toSample( ) | .../profile.php:879 |
| 4 | 1.1897 | 1484056 | loadFields( ) | .../profile.php:76 |
| 5 | 1.1898 | 1484792 | 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.