FirstDataBuyPassCardsRealtimeProviderProfile

Type:  Struct
Abstract:  no
Status:  Active
Configuration settings for Cards Realtime processing through FirstData BuyPass.
type
Group: System
SubGroup:
Type: String(60)
XML Representation: attribute
References: Processing Profile.Type
Attributes: Constant, Required, Default: cards-realtime/firstdata-buypass
Default Value: cards-realtime/firstdata-buypass
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
XML Representation: attribute
References: Retail Profile.Connection Mode CL
Attributes: Required, Default: SSL
Default Value: SSL
Pattern: CONNECTION_MODE
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.
applicationId
Group: Payment Facilitator
SubGroup:
Type: String(16)
XML Representation: attribute
References: Retail ISO8583 Profile.Application ID
Attributes: Default: 9899456C95
Default Value: 9899456C95
Unique application identification number.
tppId
Group: Payment Facilitator
SubGroup:
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.TPP ID
Attributes: Required, Default: 777987
Default Value: 777987
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.
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
XML Representation: attribute
References: Retail ISO8583 Profile.Merchant Name
Attributes: Required, Default: merchant-name999
Default Value: merchant-name999
The DBA name of the merchant.
descriptor
Group: Merchant
SubGroup: Descriptor
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Charge Description
Attributes: Required, Default: description
Default Value: description
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
XML Representation: attribute
References: Retail ISO8583 Profile.Customer Service Phone
Attributes: Required, Default: 5002214498
Default Value: 5002214498
Service phone of the customer used for discussing any processing issues.
merchantIdRetail
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.
terminalIdRetail    
Group: Settings
SubGroup: Retail
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Retail Terminal ID
Attributes: Default: A1
Default Value: A1
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
XML Representation: attribute
References: Retail ISO8583 Profile.Retail Datawire ID
Attributes: Default: 00010793427311253266
Default Value: 00010793427311253266
Datawire ID of the retail industry.
merchantIdMoto
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.
terminalIdMoto    
Group: Settings
SubGroup: MOTO
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Moto Terminal ID
Attributes: Default: A1
Default Value: A1
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
XML Representation: attribute
References: Retail ISO8583 Profile.Moto Datawire ID
Attributes: Default: 00010793427311253266
Default Value: 00010793427311253266
Datawire ID of the MOTO.
merchantIdEcommerce
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.
terminalIdEcommerce    
Group: Settings
SubGroup: eCommerce
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Ecommerce Terminal ID
Attributes: Default: A1
Default Value: A1
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
XML Representation: attribute
References: Retail ISO8583 Profile.Ecommerce Datawire ID
Attributes: Default: 00010793427311253266
Default Value: 00010793427311253266
Datawire ID of the e-commerce.
merchantIdRestaurant
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.
terminalIdRestaurant    
Group: Settings
SubGroup: Restaurant
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Restaurant Terminal ID
Attributes: Default: A1
Default Value: A1
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
XML Representation: attribute
References: Retail ISO8583 Profile.Restaurant Datawire ID
Attributes: Default: 00010793427311253266
Default Value: 00010793427311253266
Datawire ID of the restaurant.
merchantIdPetroleum
Group: Settings
SubGroup: Petroleum
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Petroleum 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.
terminalIdPetroleum    
Group: Settings
SubGroup: Petroleum
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Petroleum Terminal ID
Attributes: Default: A1
Default Value: A1
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.
datawireIdPetroleum
Group: Settings
SubGroup: Petroleum
Type: String
XML Representation: attribute
References: Retail ISO8583 Profile.Petroleum Datawire ID
Attributes: Default: 00010793427311253266
Default Value: 00010793427311253266
Datawire ID of the petroleum industry.
connectionType
Group: Authorization
SubGroup:
Type: String
XML Representation: attribute
References: Provider Account.Primary Connection Type
Attributes: Required, Default: FDBP_VXN
Default Value: FDBP_VXN
Type of connectivity to use to exchange messages/files with a processor.
host
Group: Authorization
SubGroup:
Type: String(160)
XML Representation: attribute
References: Provider Account.Http Host
Attributes: Default: http://my-host.com
Default Value: http://my-host.com
Host to be used for HTTPs based connectivity.
port
Group: Authorization
SubGroup:
Type: Integer
XML Representation: attribute
References: Provider Account.HTTP Port
Attributes: Default: 443
Default Value: 443
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
#TimeMemoryFunctionLocation
10.0003324240{main}( ).../index.php:0
20.0042729184include( '/var/www/html/unidoc/profile.php' ).../index.php:327
31.20431529824toSample( ).../profile.php:879
41.20431530200loadFields( ).../profile.php:76
51.20441530936mysql_fetch_array ( ).../profile.php:31
<profile/>

"<profile/>"

JSON Sample:

{
 
}

XURL Sample:

?