Special Field Requirements

The GMCIF file has fields which contain information critical to the successful processing of the file. Detailed below is a list of these fields with a full explanation of their purpose and data requirements.

SE Number – Contained in Settlement Batch Record (SBR)

Service Establishment Number (Merchant ID Number). Assigned to a merchant by Elavon. Identifies the merchant’s profile and settlement currency requirement.

SOC Number – Contained in Transaction Currency Header Record (THR)

This is the Summary of Charge number which is created by the processor/merchant and creates an association to the currency of the transactions contained within each Transaction Currency Header Record batch in the file. This is used for management information and financial reporting. The SOC number must be unique for each merchant ID, and can only be used once within a 12 month period. This number provides the information required by the Elavon processing system to produce reporting and reconciliation data.

The suggested formula for the creation of the 8-digit SOC number is as follows:

• 3-digit Julian date of file creation + the last digit of the current year
• 4-digit sequential number, incremented by 1 per THR record

Example for January 15, 2009 = 01590001
Example for October 17, 2011 = 29010001

Approval code – Contained in Transaction Detail Record (TDR)

If the transaction was online approved, the authorisation code must be stored here.

If the transaction is manually entered, without an authorisation requested, it must be space-filled. It is prohibited to store an approval code generated by the merchant. Only the authorization code received from the acquiring institution is allowed to be placed in this field.

MOTO/ECI and CVV2 and Cash Back Fields

These fields are available after special agreements.

US and Canadian Transactions

Each State or Province requires its own batch. The State or Province Code must be consistent for all records in a batch. For example:

US Transactions

Canadian Transactions

Payment Facilitator

A settlement batch must not combine Payment Facilitator and non-Payment Facilitator transactions. If the Host identifies an issue within a record in a Payment Facilitator batch the entire batch will be rejected.