Prior Auth - Voice Auth Sale Message (Tran Type 07)
Simplify supports a Prior-Auth Sale (Completion) message from the POS process.
The Prior-Auth Sale transaction type is designed to record a previously authorized transaction for funding. It is also called a “post-authorized sale” or a “completion” transaction, and works in conjunction with the Authorization Only or a voice authorization transaction. See the Elavon Gateway Message Getting Started Guide for more information.
Prior Auth Sale Request
An example of a Prior-Auth Sale Request message (from the POS process to the Simplify application) is shown below.
| API Field #, Value | Description |
|---|---|
| 0001,07 | Transaction Type. A value of 07 indicates a Prior-Auth Sale. |
| 0002,8.00 | Transaction Amount. This should be the final amount to be processed. |
| 0003,ID:1111748353147271 | This must be the same value as Field 3 of the Auth Only response. |
| 0004,1218 | Expiration Date – MMYY. |
| 0006,CVI014 | The Authorization code from the Auth Only response or from the voice authorization. |
| 0007,1025 | This must be the same number as Field 7 of the Auth Only response. |
| 0011,xxx.. | Field 11 is defined as User Data. See Appendix F for the use of this field. |
| 0013,092815 | Transaction Date (current date) – MMDDYY. |
| 0014,143005 | Transaction Time (current time) – HHMMSS. |
| 0109,TERM1 | Terminal ID provided by Elavon. |
| 0110,205 | Cashier ID. |
| 0115,010 | Transaction Qualifier (010 = Credit tender). |
| 8002,RETL01 | Location Name provided by Elavon. |
| 8006,TSTLAR | Chain Code provided by Elavon. |
Prior-Auth Sale Response
An example of a Prior-Auth Sale Response message (from the Simplify application to the POS process) is shown below.
| API Field #, Value | Description |
|---|---|
| 0001,07 | Transaction Type |
| 0002,8.00 | Transaction Amount |
| 0003,ID:1111748353147271 | Account Token returned by Fusebox. |
| 0004,1208 | Expiration Date – MMYY. |
| 0006,CVI014 | Authorization code returned by Fusebox. |
| 0007,1025 | Transaction ID / Reference Number |
| 0009,0025 | Host Batch number |
| 0011,xxx.. | Field 11 is defined as User Data. See Appendix F for the use of this field. |
| 0013,092815 | Transaction Date (current date) – MMDDYY. |
| 0014,115745 | Transaction Time (current time) – HHMMSS. |
| 0030,1 | Online Indicator |
| 0034,E | Authorization Characteristics Indicator |
| 0035,0DF9 | Validation Code |
| 0036,111175957465103 | Host Transaction Identifier (may need to appear on receipt) |
| 0037,0 | Authorizer |
| 0039,2 | Compliance Data |
| 0042,0 | Compliance Data |
| 0043,223946 | System Trace Audit Number |
| 0049,A | Card Product Result Code |
| 0052,3 | Transponder / Proximity Indicator (3 = contactless, 5 = swiped) |
| 0070,00001025 | Customer Code |
| 0109,TERM1 | Terminal ID provided by Elavon |
| 0110,205 | Cashier ID |
| 0112,189 | Processor ID |
| 0115,010 | Transaction Qualifier |
| 0125,0624155745 | Retrieval Reference Number (may need to appear on receipt) |
| 0126,2 | Track Indicator (may need to appear on receipt) |
| 0128,6.00 | Original Authorization Amount |
| 0129,1 | Compliance Data |
| 0130,8.00 | Total Authorized Amount |
| 0131,00 | CPS Total Incremental Auths sent |
| 0132,0 | Authorization Reversal Sent |
| 1000,VI | Card Type |
| 1001,VISA | Card Name |
| 1003,0000 | Gateway Response Code |
| 1004,ACKNOWLEDGED | Host Response Message |
| 1008,466206******0005 | Masked Account Number (for printing on receipt) |
| 1010,COMPLETE | Gateway Response |
| 5002,80378002 | Device Serial Number |
| 7007,1111175588200494 | Transaction Link Identifier (a unique identifier to link transactions) |
| 8002,RETL01 | Location Name provided by Elavon |
| 8006,TSTLAR | Chain Code provided by Elavon |
Note: If the POS process times out waiting on a response to the Prior-Auth sale message, the POS process performs the Inquiry logic as described above. See Inquiry Message for details.
IMPORTANT: Voice Auth: In the case of a voice auth, the POS may not have an account number or token to send in Field 3. If Simplify does not receive an account number or a token in field 3, Simplify will prompt that account data must be entered at the PIN Pad (swiped or keyed). In this scenario, it is important that the POS documentation stress that the operator verifies that the account number for which voice auth was obtained matches the account number entered at the PIN Pad.