Support Services

Setting Up the MagTek eDynamo

Overview

The eDynamo is a secure card and chip reader that works with iOS, Android, and Windows devices. It supports Bluetooth Low Energy on iOS, Android and Windows systems. USB connections are available for Windows systems.

The eDynamo requires key injection; therefore, it will not work if bought from a third party. Please order the eDynamo from Forte.

Although users can hold the eDynamo when processing card payments, you may want to purchase a third-party mount to attach it to the computing device you will be using it with (computer, tablet, or phone).

Setting Up the Reader

Web-Based Applications (including BillPay* and Forte Checkout*)

Windows (7+)

  1. Download the edynamo install file.
  2. Run the edynamo.exe file with administrator rights.
  3. Attach the eDynamo to the computer via a USB cable.

Android (6.0+)

Download the Wedget application from Google’s Play Store

iOS (11.0+)

Download the Wedget application from Apple’s App Store.

*Chrome, Edge and Internet Explorer are currently supported.

BillPay Configuration*

The new BillPay product automatically detects whether an eDynamo is connected to the computer using BillPay. EMV support available Q1 2020.

*All EMV transactions require printing an EMV-compliant receipt. Please see the EMV-Compliant Receipt format requirements described below.

Forte Checkout Configuration*

The following fields are required for processing transactions with the eDynamo using Forte Checkout:

  • swipe=edynamo
  • connection_type=USB [in the future BLE will be supported for Bluetooth connections

*All EMV transactions require printing an EMV-compliant receipt. Please see the EMV-Compliant Receipt format requirements described below.

AGI Configuration*

The following fields are required for processing transactions with the eDynamo using the Advanced Gateway Interface (AGI):

  • pg_merchant_id
  • pg_password
  • pg_transaction_type
  • pg_total_amount
  • pg_cc_enc_decryptor=21079802
  • pg_cc_enc_emv_data = KSN|DFDF59

KSN is the device serial number. DFDF59 is the value found in the ARQC field at tag DFDF59 after dipping the card when using MagTek’s Web API. The information that should be sent is after tag DFDF59 in the ARQC data: skip the first two hexadecimal characters after DFDF59, then x = the next 4-digit hexadecimal number. Starting after x, DFDF59 is the next x bytes or 2*x hexadecimal characters.

Example: DFDF598200025555

In this case the data to be sent is 5555.

NOTES:

  1. The eDynamo must be used in Quickchip mode. To set Quickchip mode on the eDynamo you must initiate the EMV transaction using options: 128 and amount: 9.99.
  2. Whenever a fallback swipe needs to be performed on an EMV card, pg_fallback_swipe = 1 must also be sent in the AGI message.

*All EMV transactions require printing an EMV-compliant receipt. Please see the EMV-Compliant Receipt format requirements described below.

Configuring an EMV-Compliant Receipt

Merchants are required to create EMV-compliant receipts for all EMV transaction sales and authorizations. Data required to print the receipt can be found in the transaction response data from the Forte Checkout callback or AGI response. Fields displayed in angle brackets (< >) contain the callback field name from Forte Checkout and field displayed in square brackets ([ ]) contain the response field name from the AGI response message. Note that these are the minimum requirements, but custom formatting is allowed.

Receipts must contain all the below elements:

Callback Response 
FIeld or Description
Receipt Format
Transaction TypeSale
Your Business NameCSG Forte
Your Business Address500 West Bethany, Suite 200
Allen, TX 75013
Your Business Phone866-290-5400
The Local Date and Time of the Transaction9/9/2019 8:10am
Your Forte Merchant ID/LocationMerchant ID: 173185
<terminal_number>Terminal: B43A775
<method_used>Card Type: Visa
<authorization_code>, [pg_authorization_code]Auth Code: 123456
<last_4>Acct No: *************8569
<total_amount>Amount: $10.81
<trace_number>, [pg_trace_number]Transaction ID: 8b0a7b87-09a2-4cb8-a9ea-545881ce80c4
<response_description>, [pg_response_description]Approved
<emvReceiptData.application_label>, [pg_emv_receipt_data.application_label]Application: Capital One
<emvReceiptData.entry_mode>, [pg_emv_receipt_data.entry_mode]Entry Mode: Chip
<emvReceiptData.CVM>, [pg_emv_receipt_data.CVM]CVM: Sign
<emvReceiptData.AID>, [pg_emv_receipt_data.AID]AID: A0000000041010
<emvReceiptData.TVR>, [pg_emv_receipt_data.TVR]TVR: 0000008000
<emvRceiptData.IAD>, [pg_emv_receipt_data.IAD]IAD: 0110606001220000AAC1000
<emvReceiptData.TSI>, [pg_emv_receipt_data.TSI]TSI: E800
<emvReceiptData.ARC>, [pg_emv_receipt_data.ARC]ARC: 01
A Signature Line for the Customerx___________________________________________________                                                              Signature

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.