FirstDataNashvilleCardsRealtimeProviderProfile

Type:  Struct
Abstract:  no
Status:  Active
Java Class:  FirstDataNashvilleCardsRealtimeProviderProfile
Configuration settings for Cards Realtime processing through FirstData Nashville.
Avalible Field Groups:
All    System Merchant Authorization Settlement Settings Payment Facilitator Configuration   
Available Fields:
type
Group: System
SubGroup:
Type: String(60)
XML Representation: attribute
References: Processing Profile.Type
Attributes: Constant, Required, Default: cards-realtime/firstdata-nashville
Default Value: cards-realtime/firstdata-nashville
Type of the Provider Profile.
Type of the Provider Profile.
isActive
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.
accountProcessingPolicy
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.
connectionMode
Group: Configuration
SubGroup:
Type: String(3)
XML Representation: attribute
References: Retail Profile.Connection Mode CL
Attributes: Required, Default: SSL
Default Value: SSL
Represents the type of connection mode for this profile.
isCreditEnabled
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.
authorizationExpirationPeriod
Group: System
SubGroup:
Type: Integer
XML Representation: attribute
References: Retail Profile.Authorization Expiration Period
Attributes: Default: 1
Default Value: 1
The number of days from the transaction request day that the unconfirmed authorization can remain unreversed even if settlement process occurs. When settlement happens and the transaction authorization period is not being reached (transaction is not expired), transaction is transfered into the next retail cycle.
isDebitCardProcessingEnabled
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.
isAutoCapture
Group: System
SubGroup:
Type: Boolean
XML Representation: attribute
References: Retail Profile.Is Auto Capture
Attributes: Default: false
Default Value: false
Indicates whether host (time initiated) capture is used to settle transactions with this processor.
tppId
Group: Payment Facilitator
SubGroup:
Type: String(11)
XML Representation: attribute
References: Retail ISO8583 Profile.TPP ID
Attributes: Default: 665887
Default Value: 665887
Third Party Processor ID - The TPP ID is mandatory on all Authorization requests submitted by Third Parties who have been issued one by First Data. If you were assigned a Third Party Processor ID, you are required to send this additional format record.
If you were not assigned a Third Party Processor ID, this record should not be sent.
applicationId
Group: Payment Facilitator
SubGroup:
Type: String(16)
XML Representation: attribute
References: Retail ISO8583 Profile.Application ID
Attributes:
Unique application identification number.
serviceId
Group: Payment Facilitator
SubGroup:
Type: String(3)
XML Representation: attribute
References: Retail ISO8583 Profile.Service ID
Attributes:
Digital number that represents the specific code of the product/service.
isTestMode
Group: Merchant
SubGroup: General
Type: Boolean
XML Representation: attribute
References: Retail ISO8583 Profile.Is Test Mode
Attributes: Default: false
Default Value: false
Indicates that this transaction should be processed in test mode, when it is handled by the processor.
merchantName
Group: Merchant
SubGroup: General
Type: String(19)
XML Representation: attribute
References: Retail ISO8583 Profile.Merchant Name
Attributes: Required
The DBA name of the merchant.
merchantTaxId
Group: Merchant
SubGroup: General
Type: String(15)
XML Representation: attribute
References: Retail ISO8583 Profile.Merchant Tax ID
Attributes:
Tax identifier of the merchant.
fnsNumber
Group: Merchant
SubGroup: General
Type: String(7)
XML Representation: attribute
References: Retail ISO8583 Profile.Merchant FNS Number
Attributes:
Merchant Food and Nutrition Service Number.

FNS Number: A seven-digit merchant number issued by the US Department of Agriculture Food and Nutrition Service that is used in EBT Food Stamps. This number must authorize merchants who wish to accept food stamp.

Note: If not supplied, space-fill so number can be obtained from First Data Terminal Control file.
tokenRequestorId
Group: Merchant
SubGroup: General
Type: String(11)
XML Representation: attribute
References: Retail ISO8583 Profile.Token Requestor ID
Attributes:
Identification number of the token requestor.
merchantStreet
Group: Merchant
SubGroup: Address
Type: String(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Merchant Street
Attributes: Required
Street address associated with this merchant account.
merchantCity
Group: Merchant
SubGroup: Address
Type: String(12)
XML Representation: attribute
References: Retail ISO8583 Profile.Merchant City
Attributes: Required
City associated with this merchant account.
countryCode
Group: Merchant
SubGroup: Address
Type: String(2)
XML Representation: attribute
References: Retail ISO8583 Profile.Merchant Country Code
Attributes: Required
Code of the country associated with this merchant account.
merchantState
Group: Merchant
SubGroup: Address
Type: String(3)
XML Representation: attribute
References: Retail ISO8583 Profile.Merchant State
Attributes: Required
State code associated with this merchant account.
merchantZip
Group: Merchant
SubGroup: Address
Type: String(9)
XML Representation: attribute
References: Retail ISO8583 Profile.Merchant Zip Code
Attributes: Required
ZIP/Postal code associated with this merchant account.
chargeDescription
Group: Merchant
SubGroup: Descriptor
Type: String(23)
XML Representation: attribute
References: Retail ISO8583 Profile.Charge Description
Attributes: Required
The Charge Descriptions are agreed upon by the client and American Express, at the time the Electronic Submission Addendum is completed.
customerServicePhone
Group: Merchant
SubGroup: Descriptor
Type: String(13)
XML Representation: attribute
References: Retail ISO8583 Profile.Customer Service Phone
Attributes: Required
Service phone of the customer used for discussing any processing issues.
merchantCategoryCodeRetail
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.
merchantIdRetail
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.
terminalIdRetail    
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.

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.
datawireIdRetail
Group: Settings
SubGroup: Retail
Type: String(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Retail Datawire ID
Attributes:
Datawire ID of the retail industry.
merchantCategoryCodeMoto
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.
merchantIdMoto
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.
terminalIdMoto    
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
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.
datawireIdMoto
Group: Settings
SubGroup: MOTO
Type: String(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Moto Datawire ID
Attributes:
Datawire ID of the MOTO.
merchantCategoryCodeEcommerce
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.
merchantIdEcommerce
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.
terminalIdEcommerce    
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
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.
datawireIdEcommerce
Group: Settings
SubGroup: eCommerce
Type: String(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Ecommerce Datawire ID
Attributes:
Datawire ID of the e-commerce.
urlEcommerce
Group: Settings
SubGroup: eCommerce
Type: String(32)
XML Representation: attribute
References: Retail ISO8583 Profile.Ecomm Url
Attributes:
Merchant's connection URL used for e-commerce transactions processing.
merchantCategoryCodeRestaurant
Group: Settings
SubGroup: Restaurant
Type: String(4)
XML Representation: attribute
References: Retail ISO8583 Profile.Restaurant 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.
merchantIdRestaurant
Group: Settings
SubGroup: Restaurant
Type: String(22)
XML Representation: attribute
References: Retail ISO8583 Profile.Restaurant 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.
terminalIdRestaurant    
Group: Settings
SubGroup: Restaurant
Type: String(12)
XML Representation: attribute
References: Retail ISO8583 Profile.Restaurant 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
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.
datawireIdRestaurant
Group: Settings
SubGroup: Restaurant
Type: String(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Restaurant Datawire ID
Attributes:
Datawire ID of the restaurant.
merchantCategoryCodeLodging
Group: Settings
SubGroup: Lodging
Type: String(4)
XML Representation: attribute
References: Retail ISO8583 Profile.Lodging 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.
merchantIdLodging
Group: Settings
SubGroup: Lodging
Type: String(22)
XML Representation: attribute
References: Retail ISO8583 Profile.Lodging 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.
terminalIdLodging    
Group: Settings
SubGroup: Lodging
Type: String(12)
XML Representation: attribute
References: Retail ISO8583 Profile.Lodging 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
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.
datawireIdLodging
Group: Settings
SubGroup: Lodging
Type: String(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Lodging Datawire ID
Attributes:
Datawire ID of lodging.
merchantCategoryCodeCarRental
Group: Settings
SubGroup: Car Rental
Type: String(4)
XML Representation: attribute
References: Retail ISO8583 Profile.Car Rental 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.
merchantIdCarRental
Group: Settings
SubGroup: Car Rental
Type: String(22)
XML Representation: attribute
References: Retail ISO8583 Profile.Car Rental 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.
terminalIdCarRental    
Group: Settings
SubGroup: Car Rental
Type: String(12)
XML Representation: attribute
References: Retail ISO8583 Profile.Car Rental 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
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.
datawireIdCarRental
Group: Settings
SubGroup: Car Rental
Type: String(20)
XML Representation: attribute
References: Retail ISO8583 Profile.Car Rental Datawire ID
Attributes:
Datawire ID of the card rental.
connectionTypeAuthorization
Group: Authorization
SubGroup:
Type: String(30)
XML Representation: attribute
References: Provider Account.Primary Connection Type
Attributes: Required, Default: FD_VXN
Default Value: FD_VXN
Type of connectivity to use to exchange messages/files with a processor.
hostAuthorization
Group: Authorization
SubGroup:
Type: String(160)
XML Representation: attribute
References: Provider Account.Http Host
Attributes:
Host to be used for HTTPs based connectivity.
portAuthorization
Group: Authorization
SubGroup:
Type: Integer
XML Representation: attribute
References: Provider Account.HTTP Port
Attributes:
Port to be used for HTTPs based connectivity.
connectionTypeSettlement
Group: Settlement
SubGroup: Connectivity
Type: String(30)
XML Representation: attribute
References: Provider Account.Secondary Connection Type
Attributes: Constant, Default: SFTP
Default Value: SFTP
Secondary/additional type of connectivity used to exchange messages/files with a provider. The value is used when more than one protocol is involved in communication process (for example, real time authorization and batch settlement).
hostSettlement
Group: Settlement
SubGroup: Connectivity
Type: String(100)
XML Representation: attribute
References: Provider Account.FTP Host
Attributes: Default: my.ftp-host.com
Default Value: my.ftp-host.com
Host used for FTP/sFTP based connectivity.
portSettlement
Group: Settlement
SubGroup: Connectivity
Type: Integer
XML Representation: attribute
References: Provider Account.FTP Port
Attributes: Default: 22
Default Value: 22
Port used for FTP/sFTP based connectivity.
usernameSettlement
Group: Settlement
SubGroup: Connectivity
Type: String(50)
XML Representation: attribute
References: Provider Account.Username
Attributes:
Username used for HTTPs based connectivity.
passwordSettlement
Group: Settlement
SubGroup: Connectivity
Type: String(100)
XML Representation: attribute
References: Provider Account.Password
Attributes: Encrypted, Default: samplePassword
Default Value: samplePassword
Password used for HTTPs based connectivity.
filename
Group: Settlement
SubGroup: Connectivity
Type: String(50)
XML Representation: attribute
References: Retail ISO8583 Profile.Filename
Attributes: Default: filename
Default Value: filename
Name of the file.
secureCode
Group: Settlement
SubGroup: Connectivity
Type: String(4)
XML Representation: attribute
References: Retail ISO8583 Profile.Secure Code
Attributes: Default: 6584
Default Value: 6584
Unique secure code.
requestPathSettlement
Group: Settlement
SubGroup: Path
Type: String(100)
XML Representation: attribute
References: Provider Account.Outbox
Attributes: Default: outbox
Default Value: outbox
Location from which response files are downloaded for processing. If value is not defined, the responses are downloaded from the upload location.
responsePathSettlement
Group: Settlement
SubGroup: Path
Type: String(100)
XML Representation: attribute
References: Provider Account.Inbox
Attributes: Default: inbox
Default Value: inbox
Location where files are uploaded for processing.
keyNameSSH
Group: Settlement
SubGroup: SSH
Type: String(100)
XML Representation: attribute
References: Provider Account.SSH Private Key File Name
Attributes: Default: samplePrivateKey.ssh
Default Value: samplePrivateKey.ssh
Name of the private SSH key to be used for FTP/sFTP based connectivity (for sFTP communication)
passphraseSSH
Group: Settlement
SubGroup: SSH
Type: String(100)
XML Representation: attribute
References: Provider Account.SSH Pass Phrase
Attributes: Encrypted, Default: samplePhrase
Default Value: samplePhrase
Passphrase of the private SSH key used for FTP/sFTP 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
#TimeMemoryFunctionLocation
10.0005322568{main}( ).../index.php:0
20.0049727504include( '/var/www/html/unidoc/profile.php' ).../index.php:327
31.18511801776toSample( ).../profile.php:879
41.18511802152loadFields( ).../profile.php:76
51.18521802888mysql_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.