Token Request Message (Tran Type 37)

Simplify supports a Token Request message from the POS process.

The Token Request message is a non-financial message, used to obtain the Fusebox assigned token for an account number.

Token Request Message

An example of a Token Request message (from the POS process to the Simplify application) is:

API Field #, Value Description
0001,37 Transaction Type. A value of 37 indicates a Token Request
0002,0.00 Transaction Amount. The amount should be 0.00 for a Token Request
0007,1045 Transaction ID / Reference Number. (Must increment on every new request)
0109,TERM1 Terminal ID provided by Elavon
0110,205 Cashier ID
0115,010 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 Location Name provided by Elavon
8006,TSTLAR 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).

Token Request Response

An example of a Token Request Response message (from the Simplify application to the POS process) is:

API Field #, Value Description
0001,37 Transaction Type
0002,0.00 Transaction Amount
0003,ID:1111748353147271 Account Token returned by Fusebox
0004,1208 Expiration Date – MMYY
0007,1045 Transaction ID / Reference Number
0052,3 Transponder / Proximity Indicator (3 = contactless, 5 = swiped)
0109,TERM1 Terminal ID provided by Elavon
0110,205 Cashier ID
0115,010 Transaction Qualifier (010 = Credit Tender)
0126,2 Track Indicator
1000,VI Card Type
1001,VISA Card Name
1003,0000 Gateway Response Code
1004,ACKNOWLEDGED Host Response Message
1008,400555******4460 Masked Account Number
1010,COMPLETE Gateway Response
5002,169018710 Device Serial Number
7007,11111799604661403 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 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 includes two additional fields:

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