Mobile Devices

Here are details on our available Mobile devices.

top top top

MagTek iDynamo

The MagTek iDynamo is equipped with lighting ports to suit all Apple devices.

To view full details on the MagTek iDynamo, click here.

 

Development Requirements

MagTek is specific in their SDK with regards to the data that they send.

 

The MagTek SDK can collect the following fields from each swipe:

[self.mtSCRALib getTrackDecodeStatus]
[self.mtSCRALib getMaskedTracks]
[self.mtSCRALib getTrack1Masked]
[self.mtSCRALib getTrack2Masked]
[self.mtSCRALib getTrack1]
[self.mtSCRALib getTrack2]
[self.mtSCRALib getTrack3]
[self.mtSCRALib getCardIIN]
[self.mtSCRALib getCardName]
[self.mtSCRALib getCardLast4]
[self.mtSCRALib getCardExpDate]
[self.mtSCRALib getCardServiceCode]
[self.mtSCRALib getCardPANLength]
[self.mtSCRALib getKSN]
[self.mtSCRALib getDeviceSerial]
[self.mtSCRALib getMagnePrint]
[self.mtSCRALib getMagnePrintStatus]
[self.mtSCRALib getSessionID]
[self.mtSCRALib getDeviceName]

 

However, iATS only needs the following fields to be send via the API:

[self.mtSCRALib getTrack1]
[self.mtSCRALib getTrack2]
[self.mtSCRALib getKSN]

iATS also requires some additional details including some parsing delimiters.

 

For MagTek iDynamos, please collate the data in the following order and delimitation:

SwiperType|@|getTrack1Masked|@|getTrack2Masked|@|KSN

 

Example of Data to be Sent to iATS:

03|@|C4DDC3DE59B1DB65F03D04CFF145469CBB2CB59E22BA56ED8691D27813D963F51408F5BDDEB03E0B1860EFAAD85F9FA78ED32911443282D4ACE1F585C194DEE2D7F473456972ABB9|@|FADF1842439903BB07D444459D4DBEDC0EE099322D1AA7FBC64CDBFE834511632A592E52BFC8EE95|@|9012910B1D54BC000069

MagTek uDynamo

The MagTek uDynamo uses the 3.5mm audio jack (headphone connector) to send the encrypted details to the app.

To view full details on the MagTek UDynamo, click here.

 

Development Requirements

MagTek is specific in their SDK with regards to the data that they send.

 

The MagTek SDK can collect the following fields from each swipe:

[self.mtSCRALib getTrackDecodeStatus]
[self.mtSCRALib getMaskedTracks]
[self.mtSCRALib getTrack1Masked]
[self.mtSCRALib getTrack2Masked]
[self.mtSCRALib getTrack1]
[self.mtSCRALib getTrack2]
[self.mtSCRALib getTrack3]
[self.mtSCRALib getCardIIN]
[self.mtSCRALib getCardName]
[self.mtSCRALib getCardLast4]
[self.mtSCRALib getCardExpDate]
[self.mtSCRALib getCardServiceCode]
[self.mtSCRALib getCardPANLength]
[self.mtSCRALib getKSN]
[self.mtSCRALib getDeviceSerial]
[self.mtSCRALib getMagnePrint]
[self.mtSCRALib getMagnePrintStatus]
[self.mtSCRALib getSessionID]
[self.mtSCRALib getDeviceName]

 

However, iATS only needs the following fields to be send via the API:

[self.mtSCRALib getTrack1]
[self.mtSCRALib getTrack2]
[self.mtSCRALib getKSN]

iATS also requires some additional details including some parsing delimiters.

 

For MagTek uDynamos, please collate the data in the following order and delimitation:

SwiperType|@|getTrack1Masked|@|getTrack2Masked|@|KSN

 

Example of Data to be Sent to iATS:

03|@|C4DDC3DE59B1DB65F03D04CFF145469CBB2CB59E22BA56ED8691D27813D963F51408F5BDDEB03E0B1860EFAAD85F9FA78ED32911443282D4ACE1F585C194DEE2D7F473456972ABB9|@|FADF1842439903BB07D444459D4DBEDC0EE099322D1AA7FBC64CDBFE834511632A592E52BFC8EE95|@|9012910B1D54BC000069

ID Teach UniMag II

ID Tech UniMag II uses the 3.5mm audio jack (headphone connector) to communicate with the app.

To view full details on the ID Tech UniMag II, click here.

 

Development Requirements

When you swipe your credit card, ID Tech will read, mask some information and encrypt all track information. See screenshot below from a demo application showing the masked information above and encrypted data below (in red box):

 

Make sure to parse out and only pass in the encrypted credit card track information (enclosed with red rectangle in the diagram above) to the creditCardNum or ccNum parameter of web service method.

You can use the unencrypted (masked) data to fill fields for the customer to verify, such as the last 4 digits of the credit card, the first name and last name.

 

Example of encrypted data from ID Tech UniMag II:

<02f00080 1f422300 8383252a 34313131 2a2a2a2a 2a2a2a2a 31313131 5e504159 4d454e54 53544553 54434152 442f4941 54535e32 3130382a 2a2a2a2a 2a2a2a2a 2a2a2a2a 2a2a2a2a 2a2a3f2a 3b343131 312a2a2a 2a2a2a2a 2a313131 313d3231 30382a2a 2a2a2a2a 2a2a2a2a 2a3f2a87 a8e39cfa b3ef0630 ee27e912 34ce82d8 5b689e5f 10365a78 4c7573d2 1398ac9d 9cc2cd87 5e05ba1f 4e845ee0 306cf707 ae02a247 b2cab73a 46a2b203 df559488 433d3c14 a769b2c4 244829c4 97dbffc2 3890bd8e 1373fb2c 56706162 e6a4fd03 23be5966 9ff8bd73 71634a4c 2c3d4254 31343032 36333335 33ffff73 81390314 800007c8 2403>

iATS requires this encrypted data and the swiper type and this encrypted data to complete the transaction.

 

Please parse the information as follows:

SwiperType|@|EncryptedCode

 

Where:

• SwiperType : 01 for ID Tech UniMag II>br>• Entire Encrypted string (no masked data)
• |@| : Delimiter

 

Example of Data to be Sent to iATS:

01|@|02f00080 1f422300 8383252a 34313131 2a2a2a2a 2a2a2a2a 31313131 5e504159 4d454e54 53544553 54434152 442f4941 54535e32 3130382a 2a2a2a2a 2a2a2a2a 2a2a2a2a 2a2a2a2a 2a2a3f2a 3b343131 312a2a2a 2a2a2a2a 2a313131 313d3231 30382a2a 2a2a2a2a 2a2a2a2a 2a3f2a87 a8e39cfa b3ef0630 ee27e912 34ce82d8 5b689e5f 10365a78 4c7573d2 1398ac9d 9cc2cd87 5e05ba1f 4e845ee0 306cf707 ae02a247 b2cab73a 46a2b203 df559488 433d3c14 a769b2c4 244829c4 97dbffc2 3890bd8e 1373fb2c 56706162 e6a4fd03 23be5966 9ff8bd73 71634a4c 2c3d4254 31343032 36333335 33ffff73 81390314 800007c8 2403