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. A Void Transaction is also used to financially recover from a timed-out financial request.

The following table shows a sample of fields in the Void Transaction message that may need to match fields in the original transaction.

API Field # Description
0002 Transaction Amount
0003 Account Data (token)
0004
Expiration Date
0007 Transaction ID / Reference Number
0109 Terminal ID
8002 Location Name
8006 Chain Code

See the Fusebox Integration Guide under "Transaction Types" > "Void Sale (11)" for more information.

Sample Message

Request

An example of a Void Request message (from the POS to Simplify) is:

API Field #, Value Description
0001,11 Transaction Type.
0002,125.98 Transaction Amount. Must match Sale response.
0003,ID:1102571965098318 Account Data. Must match Sale response.
0004,1215 Expiration Date – MMYY. Must match Sale response (if present).
0007,1025 Transaction ID / Reference Number. Must match Sale response.
0011,xxx.. User Data. See Field 11 (User Data) .
0013,022519 Transaction Date (current date) – MMDDYY
0014,143515 Transaction Time (current time) – HHMMSS
0109,TERM1 Terminal ID. Must match Sale response.
0110,205 Cashier ID
0115,010 Transaction Qualifier (010 = credit; 030 = debit). Must match Sale response.
8002,RETL01 Location Name. Must match Sale response.
8006,TSTLAR Chain Code. Must match Sale response.

Response

An example of a Void Response message (from Simplify to the POS) is:

API Field #, Value Description
0001,11 Transaction Type.
0002,125.98 Transaction Amount
0003,ID:1102571965098318 Account Token (returned by Fusebox)
0006,CMC663 Authorization Code (returned by Fusebox)
0007,1025 Transaction ID / Reference Number
0009,0020 Fusebox – Host Batch number
0011,xxx.. User Data. See Field 11 (User Data) .
0013,022519 Transaction Date (current date) – MMDDYY
0014,143515 Transaction Time (current time) – HHMMSS
0030,1 Fusebox – Online Indicator
0032,022519 Fusebox – Authorization Transaction Date
0033,105319 Fusebox – Authorization Transaction Time
0035,1008 Validation Code
0036,MCC0DFA9A Host Transaction Identifier
0037,0 Fusebox – Authorizer
0043,022284 System Trace Audit Number
0047,2;1;0;1;0;0;6;5;4;1;2;4;0;4 POS Data Code
0052,5 Transponder / Proximity Indicator (0 = contact; 2 = contactless, 5 = swiped)
0054,90 POS Entry Mode
0109,TERM1 Terminal ID. Must match Sale response.
0110,205 Cashier ID
0112,400 Fusebox – Processor ID
0115,010 Transaction Qualifier (010 = credit; 030 = debit)
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
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)
1009,AA Host Response Code
1010,COMPLETE Gateway Response Message
1012,0020 Gateway Batch Number
1200,0000AA Issuer Network Information
1359,4 EMV CVM Indicator
5002,80378002 Device Serial Number
5004,G2 Encryption Provider ID
5010,EMVDC0838 EMV kernel version
5070,xxx… Simplify Information. See Field 5070 (Simplify Load Information) .
5071,xxx… Defines whether card and cardholder are present. See Field 5071 (Card/Cardholder Present?) .
7007,1114281539351186 Transaction Link Identifier (unique identifier to link transactions)
8002,RETL01 Location Name. Must match Sale response.
8006,TSTLAR Chain Code. Must match Sale response.