EMV Credit Card Payments

Better known as chip credit card payments are cards that have a small computer chip on them which authenticate and secure transactions.

Use Cases

In person transactions where the Merchant has EMV capable equipment and the customer is using a chip card.

EMV transactions are typically integrated in environments where the swiped transactions are used where the

Commonly used anywhere swipe is available, however, restaurants and gas stations have not fully adopted EMV yet.

Equipment

Check out the Supported Hardware tab for a full list of equipment and card readers available for EMV transactions.

Things to Keep in Mind

You may have noticed EMV transactions take slightly longer than a swipe transaction, this is due to the EMV chip on the credit card talking to the EMV reader to ensure the customer is who they say they are. Although integrating with EMV transactions is a bit more work they are much more secure transactions and have proven to reduce fraud when compared to keyed and swiped. The security that the EMV technology provides and the merchant having the card in their presence will typically result in lower processing fees for these transactions. Please note, it does require integrating with at least one of the supported card readers and for the merchant to purchase this equipment.

Making an EMV Transaction

Step 1

Set HTTP request method to POST and use /payment route

Step 2

Supply the request with your username and password. Make sure it's in base-64 encryption in the Authorization header field.
Set Content-Type to Application/JSON

Step 3

In the cardAccount object, we only provide EMV as seen in this payload:

{
   "merchantId" :"4xxx0",
   "tenderType" :"Card",
   "amount" :"0.01",
   "cardAccount" :{
      "emvData": "Xym9TXlYqOusxG1JrdlDqThnzBVZHnTziDjptEdBsv0MasvWV8IOF75Ld0OlntfIxxxxxxxxxxxxxxxx\/...", 
      "emvDataKsn": "8033xxxxxxx000011" 
       }
  }

If you would like to get the response object, you should supply echo=true as a URL parameter. This is useful as it keeps the user from having to use a GET call to see the response object information.

Step 4

You may use any chip-card for testing, but you will need to get an emv-enabled reader injected with our PPS private key to make payments. The response from the reader will be encrypted in TLV, which you will need to pull out the C0 tag for the emvDataKsn field and the C2 tag for the emvData field.

Step 5

You should expect to receive an HTTP 201 code for the response if the payment posted correctly, and the status field should set to Approved. Note that the Sandbox environment will approve all cards as long as they are in the correct credit card format. To get a Declined status, you would use our Testing Cards as specified.