Void Transaction Message (Tran Type 11)
In some transactions, the customer may wish to void a Sale transaction after it has already been completed. The POS can accomplish this by sending a Void Transaction message to Simplify.
The Void Transaction must include certain fields that were returned in the Sale authorization responses:
API Field #, Value | Description |
---|---|
0002 | Transaction Amount |
0003 | Token |
0007 | Reference Number |
0109 | Terminal ID |
Void Request
An example of a Void Request message (from the POS process to the Simplify application) is:
API Field #, Value | Description |
---|---|
0001,11 | A value of 11 indicates a Void Sale |
0002,125.98 | This must be the same value as Field 2 of the Sale Authorization response |
0003,ID:1102571965098318 | This must be the same value as Field 3 of the Sale Authorization response |
0004,1215 | Expiration Date – MMYY |
0007,1025 | This must be the same number as Field 7 of the Sale Authorization response. |
0011,xxx.. | Field 11 is defined as User Data. See Appendix F for the use of this field. |
0109,TERM1 | Terminal ID provided by Elavon. This must be the same number as Field 109 of the Sale Authorization response |
0110,205 | Cashier ID |
0115,010 | Transaction Qualifier (010 = Original transaction was a Credit Tender) |
8002,RETL01 | Field 8002 is the Location Name provided by Elavon |
8006,TSTLAR | Field 8006 is the Chain Code provided by Elavon |
Void Response
An example of a Void Response message (from Simplify to the POS process) is:
API Field #, Value | Description |
---|---|
0001,11 | Field 1 is the Transaction Type. A value of 09 indicates a Return. |
0002,125.98 | Field 2 is the Transaction Amount |
0003,ID:1102571965098318 | This is the account token returned by Fusebox |
0006,CMC663 | Field 6 is the Authorization code returned by Fusebox |
0007,1025 | Field 7 is a Transaction ID / Reference Number. (Must increment on every new request) |
0009,0020 | Fusebox – Host Batch number |
0011,xxx.. | Field 11 is defined as User Data. See Appendix F for the use of this field. |
0030,1 | Fusebox – Online Indicator |
0032,100814 | Fusebox – Authorization Transaction Date |
0033,105319 | Fusebox – Authorization Transaction Time |
0034,M | Fusebox – Authorization Characteristics Indicator |
0035,1008 | Validation Code |
0036,MCC0DFA9A | Host Transaction Identifier (may need to appear on receipt) |
0037,0 | Fusebox – Authorizer |
0043,022284 | System Trace Audit Number |
0047,5;1;1;1;1;*;*;0;0;1;*;C | POS Data Code |
0052,5 | Transponder / Proximity Indicator (3 = contactless, 5 = swiped) |
0054,90 | POS Entry Mode |
0109,TERM1 | Field 109 is the Terminal ID provided by Elavon |
0110,205 | Field 110 is the Cashier ID |
0112,400 | Fusebox – Processor ID |
0115,010 | Field 115 is the Transaction Qualifier |
0125,1008145319 | Retrieval Reference Number (may need to appear on receipt) |
0126,0 | Track Indicator (may need to appear on receipt) |
0128,1.00 | Original Authorization Amount |
0129,0 | Fusebox – Compliance Data |
0130,1.00 | Authorized Amount |
0131,00 | CPS Total Incremental Auths sent |
0132,0 | Authorization Reversal Sent |
0140,USD | Fusebox – Merchant Currency Trigraph |
0141,840 | Terminal Currency Code |
0651,0000000 | Reversal data (for reversal, if needed) |
1000,MC | Card Type |
1001,MASTERCARD | Card Name |
1003,0000 | Gateway Response Code |
1004,ACKNOWLEDGED | Host Response Message |
1005,0031940008024682711000 | Merchant Number |
1008,************1114 | Masked Account Number (may need to appear on receipt) |
1010,COMPLETE | Gateway Response Message |
1012,0020 | Gateway Batch Number |
1200,0000AA | Issuer Network Information |
5002,80378002 | Device Serial Number |
5004,G2 | Encryption Provider ID This should be the value returned on the Stand-in Response |
5010,30650467 | EMV kernel version |
7007,1114281539351186 | 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 |
Note: Timeout on Void: If a Void Request times out at the POS before receiving a response from Simplify, or if the Simplify response indicates a host timeout, an Inquiry Request can be sent (as for any timeout). If a Void Request times out in either manner, it should be re-sent until a Host Response is received.