4 - MTSCRA Library Data Type and Structures
Dynamag, DynaMAX, and eDynamo| Secure Card Reader Authenticator | Programmer’s Reference (WCF)
Page 25
*/
4.6
ARQC
getTransactionProgress will return the ARQC after device request a acquirer decision for a transaction.
type : 771 (0x303)
data : hex string contains byte array for following structure
Offset
Field
Name
Value
0
Message
Length
Two byte binary, most significant byte first. This gives the total length of the
ARQC message that follows.
2
ARQC
Message
See Appendix A. It is expected that the host will use this data to process a
request.
{"type":771,"data":"01ABFD8201A7DFDF250F423330364639363039323831354141
FA8201909A030000009F02060000000009999F10120110A00001220000000000000000
000000FF9F1607303030303030309F4E0730303030303030820258008E100000000000
00000042015E0342031F035F24031401315F25031201019F0607A00000000410109F07
02FF009F0D05F0500408009F0E0500008800009F0F05F0700498009F260816A2BD071A
D5DC1E9F2701809F360200C59C01009F33032028C89F34035E03009F37049FA41BDA9F
3901059F4005720000B001950542200080009B02E8009F1E0842333036463936209F1A
0208405F2A0208409F01060000000000019F2103183917DFDF4D263B35343133303030
3034303030313531333D303131343030303030303030303030303030303FDFDF520105
F8820078DFDF560A9010010B306F9600001BDFDF570100FA820061DF31182E6ECDA60D
8CB9D382EE13942C18B6DF82EE13942C18B6DFDF321040A47A243903C9DA71DBF06996
3D1D64DF3B30E5B2E54BF31D8DC0BA5C217F756F0CC3D24553AE6B25BD4FFA7C8D9824
3DC66D8C43FEA072300044F6278B858108B825"};
4.7
Transaction Result
getTransactionProgress will return the transaction data after device complete a transation
type : 772 (0x304)
data : hex string contains byte array for following structure
Offset
Field
Name
Value
0
Signature
Required
This field indicates whether a card holder signature is required to complete the
transaction:
0x00 – No signature required
0x01 – Signature required
If a signature is required, it is expected that the host will acquire the signature
from the card holder as part of the transaction data.
1
Batch Data
Length
Two byte binary, most significant byte first. This gives the total length of the
ARQC message that follows.
3
Batch Data
See Appendix C. It is expected that the host will save this data as a record of
the transaction.