1100 / 1110 Messages – Pre-Authorisations

The 1100 / 1110 message pair is used for pre-authorisation purposes, e.g. seeking approval for the delivery of goods or services where the final amount is not known at the time of the transaction. This is typically the case in hotel, ecommerce and unattended environments (for example petrol stations). The approval is mandatory to get access to the required goods or service or to validate in advance the payment means (credit card) - including the available funds that will be used by the customer at the time of purchase/sale.

Pre-authorisations and authorisations do not result in the cardholder being debited immediately. The cardholder will be debited when this transaction is cleared to the card schemes.

The transaction card details can be provided by a terminal's magnetic stripe reader, ICC reader or manually via the keyboard.

For a magnetic stripe or ICC read the Track 2 Data (Field 35) is used for authorisation, whereas for a manual entry the Primary Account Number (Field 2) and the Date of Expiration (Field 14) are used.

Field

Field Name

Required

Comments

 

Message Type ID

Mandatory

1100

 

Primary bitmap

Mandatory

 

2

PAN

Conditional

Primary Account Number. Required for keyed transactions where Field 35 is not available.

3

Processing code

Mandatory

See Field 3 description for valid values.

4

Transaction amount

Mandatory

The amount will be in the currency specified in Field 49.

6

Cardholder Billing Amount

Conditional

Must be included if DCC has been performed on the device. The amount will be in the currency specified in Field 51.

10

Conversion Rate

Conditional

Mandatory if Field 6 is present.

11

STAN

Mandatory

Unique reference number from the transaction initiator.

12

Transaction Local Date and Time

Mandatory

Date and time at terminal.

14

Expiration Date

Conditional

The date upon which the card expires. Present only if Field 35 (Track 2) is not provided. Keyed transactions only.

22

Point of Service Data

Mandatory

See Field 22 description for details.

28

Reconciliation Date

Mandatory

See Field 28 description for details.

29

Reconciliation Number

Mandatory

See Field 29 description for details.

32

Acquiring Institution ID

Mandatory

Provided by Elavon.

35

Track 2 Data

Conditional

This field shall be supplied if a magnetic stripe card is swiped through the POS reader or an ICC card is read through an ICC device reader. If this field is present Fields 2 and 14 should not be provided

37

Retrieval Reference Number

Mandatory

Unique partner transaction reference.

38

Approval Code

Conditional

Mandatory for completions and incremental pre-authorisations where approval code from (initial) pre-authorisation is populated.

41

Terminal Identification

Mandatory

Card Acceptor Terminal ID. The 8 digit terminal ID will be assigned and provided by Elavon.

42

Merchant ID

Mandatory

A unique ID for the establishment requesting the authorisation.

43

Card Acceptor Name/Address

Optional

Name/Address of establishment requesting the transaction.

48

Additional Private Data

Mandatory

Please refer to Field description and Appendix B.

49

Transaction Currency Code

Mandatory

ISO 4217 numeric currency code of the amount in Field 4.

51

Cardholder Billing Currency Code

Conditional

Required if Field 6 is present. ISO 4217 numeric currency code of the cardholder billing amount specified in Field 6.

52

PIN Data

Conditional

Encrypted PIN.

53

Security Related Information

Conditional

This field is mandatory when PIN data is present, except where DUKPT information is supplied in Field 63, Tag 01.

54

Amount, Other

Conditional

Must be included if there is a cash component of the overall transaction amount in Field 4. The amount will be in the currency specified in Field 49.

55

Integrated Circuit Card Data

Conditional

Must be supplied when the ICC has been used to process the transaction.

60

Reserved Private Data

Mandatory

If a partner supports DCC, Tag 01 (bytes 3 – 4) determine the number of supported currencies. Elavon will advise the partner of the appropriate values in Tag 01.

61

Reserved Private Data II

Conditional

Refer to Field Descriptions for available Tags.

63

Reserved Private Data III

Conditional

Tag 01 is mandatory if PIN Data is present and the DUKPT scheme is being used.

64

MAC

Conditional

Value calculated as described in Appendix B if MAC processing is supported.

 

 

Field

Field Name

Required

Comments

 

Message Type ID

Mandatory

1110 for Pre-authorisation / Update / Completion & Authorisation response.

 

Primary bitmap

Mandatory

 

2

PAN

Conditional

Echo if present in corresponding 1100.

3

Processing code

Mandatory

Echo value in corresponding 1100.

4

Transaction amount

Mandatory

Echo value in corresponding 1100 or partially approved amount.

6

Cardholder Billing amount

Conditional

Echo if present in corresponding 1100.

10

Conversion Rate

Conditional

Echo if present in corresponding 1100.

11

STAN

Mandatory

Echo value in corresponding 1100.

12

Transaction Local Date and Time

Mandatory

Echo value in corresponding 1100.

28

Reconciliation Date

Mandatory

Echo value in corresponding 1100.

29

Reconciliation Number

Mandatory

Echo value in corresponding 1100.

32

Acquiring Institution ID

Mandatory

Echo value in corresponding 1100.

37

Retrieval Reference No.

Mandatory

Echo value in corresponding 1100.

38

Approval Code

Conditional

Returned for approved and format error responses. See Field 38 description for more details

39

Response Code

Mandatory

Response from the authorisation.

41

Terminal Identification

Mandatory

Echo value in corresponding 1100.

42

Merchant ID

Mandatory

Echo value in corresponding 1100.

43

Card Acceptor Name / Address

Conditional

Echo value if present in corresponding 1100.

48

Additional Private Data

Mandatory

 

49

Transaction Currency Code

Mandatory

Echo value in corresponding 1100.

51

Cardholder Billing Currency Code

Conditional

Echo if present in corresponding 1100.

54

Amount, Other

Conditional

Original amount requested in a partial approval.

55

Integrated Circuit Card Data

Conditional

Returned for an ICC Transaction. Full details in Field 55 Description section.

63

Reserved Private Data III

Conditional

Only those tags relevant to response messages will be returned.

64

MAC

Conditional

Value calculated as described in Appendix B if MAC processing is supported.