Retail First Data Rapid Connect Profile

Encapsulates First Data Rapid Connect specific settings required for real-time transaction processing. Adds First Data Rapid Connect specific fields to the base fields of Billing Profile and Retail Profile.

Alternate ID assigned by FirstData Prepaid Closed Loop.
For additional information, please contact account representative.

ID of the application used for the transaction processing.

Identifier that represents the original source document reference number associated with car rental industry of the merchant.

Code used to classify a car rental industry of the merchant.

Unique ID of the merchant associated with eCommerce industry assigned by FirstData.
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.

ID of the terminal associated with lodging industry of the merchant.
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

Description of the file agreed upon by the client and American Express, at the time the Electronic Submission Addendum is completed.

Phone number used for resolving any processing issues.

Identifier that represents the original source document reference number.

Dynamic field that contains address of the merchant.

Dynamic field that contains address city of the merchant.

Dynamic field that contains address country code of the merchant.

Dynamic field that contains address county code of the merchant.

Dynamic field that contains name of the merchant.

Dynamic field that contains address state code of the merchant.

Dynamic field that contains address ZIP/postal code of the merchant.

URL of the eCommerce site.

Identifier that represents the original source document reference number associated with eCommerce industry of the merchant.

Code used to classify an eCommerce business of the merchant.

Unique ID of the merchant associated with eCommerce industry.
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.

ID of the terminal associated with eCommerce industry of the merchant.
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

Name of the file that is downloaded.

Unique ID assigned by FirstData to identify the group of merchants.

Indicates whether the test mode is active for the customer.

Identifier that represents the original source document reference number associated with lodging industry of the merchant.

Code used to classify a lodging industry of the merchant.

Unique ID of the merchant associated with lodging industry.
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.

ID of the terminal associated with lodging industry of the merchant.
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.

City of the merchant mailing address applied on the FirstData merchant profile.

Country code of the merchant mailing address.

Code received by a merchant from government that allows to accept EBT cards.

Unique ID assigned by FirstData to identify merchant.

Merchant name used as a DBA (Doing Business As) name on the FirstData merchant file.

State code of the merchant mailing address used on the FirstData merchant file.

Street of the merchant mailing address applied on the FirstData merchant file.

Tax ID collected by a merchant for the transaction processing.

ZIP or postal code of the merchant mailing address used on the FirstData merchant file.

Identifier that represents the original source document reference number associated with MOTO industry of the merchant.

Code used to classify a MOTO industry of the merchant.

Unique ID of the merchant associated with MOTO industry.
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.

ID of the terminal associated with MOTO industry of the merchant.
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

Identifier that represents the original source document reference number associated with petroleum industry of the merchant.

Code used to classify a petroleum industry of the merchant.

Unique ID of the merchant associated with petroleum industry. 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.

ID of the terminal associated with petroleum industry of the merchant.
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.

Identifier that represents the original source document reference number associated with restaurant industry of the merchant.

Code used to classify a restaurant industry of the merchant.

Unique ID of the merchant associated with restaurant industry.
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.

ID of the terminal associated with restaurant industry of the merchant.
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

Identifier that represents the original source document reference number associated with retail industry of the merchant.

Code used to classify a retail industry of the merchant.

Unique ID of the merchant associated with retail industry.
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.

ID of the terminal associated with retail industry of the merchant.
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

Additional security layer for online credit and debit card transactions.

Code that represents the specific ID of the product or service.

Unique ID assigned by FirstData to identify the terminal.

Rapid Connect ID assigned by FirstData for a specific version of vendor/merchant software.