Incremental Authorization Message (Tran Type 75)

Simplify supports an Incremental Authorization message from the POS process if tokenization is implemented.

See the Lodging Integration Guide for more description and requirements for the Incremental Authorization message.

Sample Incremental Authorization Message

Request

An example of an Incremental Authorization Request message (from the POS process to the Simplify application) is:

API Field #, Value Description
0001,75 Field 1 is the Transaction Type. A value of 75 indicates an Incremental Authorization message
0002,19.00 Field 2 is the Transaction Amount
0003,ID:1111748353147271 This must be the same value as Field 3 of the Auth Only response
0004,1208 Field 4 is the Expiration Date – MMYY
0007,1123 Field 7 is a Transaction ID / Reference Number (Must match ID in original authorization request.)
0011,xxx.. Field 11 is defined as User Data. See Appendix F for the use of this field
0013,092815 Field 13 is the Transaction Date (current date) – MMDDYY
0014,143005 Field 14 is the Transaction Time (current time) – HHMMSS
0109,TERM1 Field 109 is the Terminal ID provided by Elavon
0110,205 Field 110 is the Cashier ID
0115,010 Field 115 is the Transaction Qualifier (010 = Credit tender)
1008,ID: Field 1008 is set to the value ‘ID:’ to request that an account Token be returned by Fusebox
8002,RETL01 Field 8002 is the Location Name provided by Elavon
8006,TSTLAR Field 8006 is the Chain Code provided by Elavon

Note: For the message from Simplify to Fusebox, Simplify will populate the Account Data fields (and PIN and KSN fields for Debit transactions).

Response

An example of an Incremental Authorization Response message (from the Simplify application to the POS process) is:

API Field #, Value Description
0001,01 Note that the Tran Type in the response is a 01 (Auth Only response) – not a 75
0002,19.00 Field 2 is the Transaction Amount
0003,ID:1120064425266606 This is the account token returned by Fusebox
0004,1208 Field 4 is the Expiration Date – MMYY
0006,CVI130 Field 6 is the Authorization code returned by Fusebox
0007,1123 Field 7 is a Transaction ID / Reference Number (Must match ID in original authorization request.)
0009,0102 Host Batch number
0011,xxx.. Field 11 is defined as User Data. See Appendix F for the use of this field
0013,092815 Field 13 is the Transaction Date (current date) – MMDDYY
0014,143005 Field 14 is the Transaction Time (current time) – HHMMSS
0030,1 Online Indicator
0032,010512 Authorization Transaction Date
0033,161934 Authorization Transaction Time
0034,E Authorization Characteristics Indicator
0035,BF66 Validation Code
0036,112006976774166 Host Transaction Identifier (may need to appear on receipt)
0037,0 Authorizer
0039,2 Compliance Data
0042,0 Compliance Data
0043,211605 System Trace Audit Number
0049,A Card Product Result Code
0052,3 Transponder / Proximity Indicator (3 = contactless, 5 = swiped)
0070,00001123 Customer Code
0109,TERM1 Terminal ID provided by Elavon
0110,205 Cashier ID
0112,189 Processor ID
0115,010 Field 115 is the Transaction Qualifier
0125,0106211934 Retrieval Reference Number (may need to appear on receipt)
0126,2 Track Indicator (may need to appear on receipt)
0129,1 Compliance Data
0130,19.00 Total Authorized Amount
0131,00 CPS Total Incremental Auths sent
0140,A Merchant Currency Trigraph
1000,VI Card Type
1001,VISA Card Name
1003,0000 Gateway Response Code
1004,APPROVAL Host Response Message
1005,0010600008014593613999 Merchant Number
1008,400555******4460 Masked Account Number (for printing on receipt)
1009,AA Host Response Code
1010,COMPLETE Gateway Response Message
5002,80378002 Device Serial Number
7007,1112006767740668 7007,1112006767740668 Transaction Link Identifier. A unique identifier to link transactions
8002,RETL01 Field 8002 is the Location Name provided by Elavon
8006,TSTLAR Field 8006 is the Chain Code provided by Elavon

Notes:

If the POS process times out waiting for a response to the Incremental Authorization message, the POS process should perform the Inquiry logic. See Inquiry Messagefor details.

If account data is entered manually and CVV2 / AVS prompting is enabled for the tender type used in the transaction (typically, for credit only), the online response will include two additional fields:

API Field #, Value Description
0050,**** CVV2 4 bytes (masked)
0700,94588 AVS 5-9 bytes (true zip code)