FirstDataTransArmorStrongAuthTokenizationProviderProfile

Type:  Struct
Abstract:  no
Status:  Active
Java Class:  FirstDataTransArmorStrongAuthTokenizationProviderProfile
Configuration settings for FistData-StrongAuth token register profile.
Avalible Field Groups:
All    System TransArmor StrongAuth   
Available Fields:
type
Group: System
SubGroup:
Type: String
XML Representation: attribute
Attributes: Constant, Required, Default: tokenization/transarmor-compass-strongauth
Default Value: tokenization/transarmor-compass-strongauth
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
XML Representation: attribute
References: Processing Profile.Account Processing Policy
Attributes: Default: VMXDN---AU
Default Value: VMXDN---AU
Type of processing policy for the account.
isTestMode
Group: System
SubGroup:
Type: Boolean
XML Representation: attribute
References: Token Register FirstData StrongAuth Profile.Is Test Mode
Attributes: Default: false
Default Value: false
Indicates whether test mode is active in the system.
tokenTypeTA
Group: TransArmor
SubGroup: Payment Facilitator
Type: String
XML Representation: attribute
References: Token Register FirstData StrongAuth Profile.Token Type
Attributes: Required, Default: LBMN
Default Value: LBMN
Merchant Specific Token Value issued by First Data.
Left justified/space filled.

There are two Token types available.
The First is a single use, one time only Token. This token is used one time for a specific transaction and cannot be reused for multiple transactions (sometimes referred to as an F-Token).
The second Token type is a Reusable Token (sometimes referred to as an R-Token). The Reusable Token can be reused by the merchant multiple times for multiple transactions. The merchant is allowed to use the Reusable Token an unlimited number of times as it has no limitation of being tied to just one transaction.
divisionNumberTA
Group: TransArmor
SubGroup: Payment Facilitator
Type: String
XML Representation: attribute
References: Token Register FirstData StrongAuth Profile.Division Number
Attributes: Required, Default: 123456789
Default Value: 123456789
First Data assigns a unique Division Number to process each international currency. A single Division Number can support different transaction types and methods of payment in the same currency.
tppIdTA
Group: TransArmor
SubGroup: Payment Facilitator
Type: String
XML Representation: attribute
References: Token Register FirstData StrongAuth Profile.TPP ID
Attributes: Required, Default: SML224
Default Value: SML224
Left justified/space filled.

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.
applicationIdTA
Group: TransArmor
SubGroup: Payment Facilitator
Type: String
XML Representation: attribute
References: Token Register FirstData StrongAuth Profile.Application ID
Attributes: Required, Default: 998745546
Default Value: 998745546
Identification number of the used application.
terminalIdTA    
Group: TransArmor
SubGroup: Settings
Type: String
XML Representation: attribute
References: Token Register FirstData StrongAuth Profile.Terminal ID
Attributes: Required, Default: 123456789
Default Value: 123456789
Identifies a processing device associated to a Point of Sale division. (Mandatory)

Left justified/space filled.

Note: The Terminal ID must be provided by the merchant and assigned to each terminal device (pos entry point) and must be unique when the transaction is face to face.
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.
merchantIdTA
Group: TransArmor
SubGroup: Settings
Type: String
XML Representation: attribute
References: Token Register FirstData StrongAuth Profile.Merchant ID
Attributes: Required, Default: 123456789
Default Value: 123456789
Merchant’s location ID. (Optional)

Left justified/space filled.
datawireIdTA
Group: TransArmor
SubGroup: Settings
Type: String
XML Representation: attribute
References: Token Register FirstData StrongAuth Profile.Datawire ID
Attributes: Default: 123456789
Default Value: 123456789
connectionTypeTA
Group: TransArmor
SubGroup: Realtime
Type: String
XML Representation: attribute
References: Provider Account.Primary Connection Type
Attributes: Constant, Required, Default: FD_VXN
Default Value: FD_VXN
Type of connectivity to use to exchange messages/files with a processor.
connectionTypeRealtimeSA
Group: StrongAuth
SubGroup: Realtime
Type: String
XML Representation: attribute
References: Provider Account.Primary Connection Type
Attributes: Constant, Required, Default: StrongAuth
Default Value: StrongAuth
Type of connectivity to use to exchange messages/files with a processor.
hostRealtimeSA
Group: StrongAuth
SubGroup: Realtime
Type: String
XML Representation: attribute
References: Provider Account.Http Host
Attributes: Required, Default: token.mybank.com:8181
Default Value: token.mybank.com:8181
Host to be used for HTTPs based connectivity.
domainIdRealtimeSA
Group: StrongAuth
SubGroup: Realtime
Type: Long
XML Representation: attribute
References: Token Register FirstData StrongAuth Profile.Domain ID
Attributes: Required, Default: 1234
Default Value: 1234
Verified by Visa defines three domains for the authentication process:
  • Issuer Domain – where the Issuer is responsible for determining whether authentication is available for the card account presented in a purchase.
  • Acquirer Domain – where the Acquirer accepts Internet transaction data from the merchant and passes it to Visa.
  • Interoperability/Visa Domain – operated by Visa, where transaction information is exchanged and stored using 3-D Secure as the common protocol.
usernameRealtimeSA
Group: StrongAuth
SubGroup: Realtime
Type: String
XML Representation: attribute
References: Token Register FirstData StrongAuth Profile.Username
Attributes: Required, Default: sampleUser
Default Value: sampleUser
The special name, that allows you to enter the system.
pa$$wordRealtimeSA
Group: StrongAuth
SubGroup: Realtime
Type: String
XML Representation: attribute
References: Token Register FirstData StrongAuth Profile.Password
Attributes: Required, Encrypted, Default: sampleUser
Default Value: sampleUser
Password of the user in the system.

The cardholder is allowed a limited number of password attempts, typically 3 to 5, as defined by the Issuer ACS.
If unable to correctly enter the password, the cardholder may access the password hint that was established during registration. If the password is entered correctly, the transaction continues. If the cardholder is not registered, the ACS briefly displays a processing window and the transaction continues as an attempted authentication. If the password is incorrectly entered more times than the Issuer limit, a failed Payer Authentication Response is returned to the merchant.
connectionTypeBatchSA
Group: StrongAuth
SubGroup: Batch
Type: String
XML Representation: attribute
References: Provider Account.Secondary Connection Type
Attributes: Constant, Required, 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).
hostBatchSA
Group: StrongAuth
SubGroup: Batch
Type: String
XML Representation: attribute
References: Provider Account.FTP Host
Attributes: Required, Default: ftp.mybank.com
Default Value: ftp.mybank.com
Host used for FTP/sFTP based connectivity.
portBatchSA
Group: StrongAuth
SubGroup: Batch
Type: Integer
XML Representation: attribute
References: Provider Account.FTP Port
Attributes: Required, Default: 22
Default Value: 22
Port used for FTP/sFTP based connectivity.
usernameBatchSA
Group: StrongAuth
SubGroup: Batch
Type: String
XML Representation: attribute
References: Provider Account.Username
Attributes: Required, Default: sampleUser
Default Value: sampleUser
Username used for HTTPs based connectivity.
passwordBatchSA
Group: StrongAuth
SubGroup: Batch
Type: String
XML Representation: attribute
References: Provider Account.Password
Attributes: Required, Encrypted, Default: samplePassword
Default Value: samplePassword
Password used for HTTPs based connectivity.
requestPathBatchSA
Group: StrongAuth
SubGroup: Path
Type: String
XML Representation: attribute
References: Provider Account.Outbox
Attributes: Required, Default: in
Default Value: in
Location from which response files are downloaded for processing. If value is not defined, the responses are downloaded from the upload location.
responsePathBatchSA
Group: StrongAuth
SubGroup: Path
Type: String
XML Representation: attribute
References: Provider Account.Inbox
Attributes: Required, Default: out
Default Value: out
Location where files are uploaded for processing.
ownerType
Group: System
SubGroup:
Type: String
XML Representation: attribute
Attributes: Transient

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.0003324752{main}( ).../index.php:0
20.0043729648include( '/var/www/html/unidoc/profile.php' ).../index.php:327
31.12731489984toSample( ).../profile.php:879
41.12731490360loadFields( ).../profile.php:76
51.12741491096mysql_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.