dsiEMVUS Supported Payment Transactions

Document created by matthew.milner on May 10, 2016Last modified by Chris Jennings on Jun 1, 2016
Version 4Show Document
  • View in full screen mode

Once you have successfully run an EMVParamDownload and initiated the ProcessTransaction method, you can build your XML payload to send a transaction request. This tutorial shows XML examples for both the dsiEMVUS and dsiPDCX.

Below are the test server end point and a generic test MerchantID. Unique MerchantIDs are available upon request from the Developer Integrations team.

 

TestServer

x1.mercurycert.net

MerchantID

755847002 (E2E/Token)

 

 

Supported dsiEMVUS payment transactions are:

 

TRANCODES

REQUIRED/OPTIONAL

NOTES

EMVSale

R

CVMSupport:chip and signature, chip and signature with chip and PIN andNo CVM

EMVVoidSale

R

EMVReturn

R

EMVVoidReturn

R

EMVVoiceAuth

O

 

*EMVZeroAuth

O

Card verification without posting an authorization to cardholder

*Available for MasterCard, Visa and Discover

 

VoidReturnbyRecordNo

O

These require the token returned from the original authorization response

AdjustbyRecordNo

O

VoidSalebyRecordNo

O

SaleByRecordNo

O

 

 

Supported dsiPDCX payment transactions are:

 

Tran type

CArd type

TRANCODES

REQUIRED/OPTIONAL

EBT

Foodstamp

Sale

O

Foodstamp

Return

O

Foodstamp

Balance

O

Foodstamp

Voucher

O

Foodstamp

VoucherReturn

O

Cash

Sale (Allows cash back)

O

Cash

Return

O

Cash

Balance

O

 

Tran type

Tran Code

Required/optional

 

Credit

FSASale

O

ReverseFSASale

O

Attachments

    Outcomes