MercuryPay and eConduit Overview

Document created by matthew.milner on May 10, 2016Last modified by Chris Jennings on Dec 19, 2016
Version 13Show Document
  • View in full screen mode

MercuryPay Cloud Processing with Blackline’s eConduit

 

Vantiv Integrated Payments partnership with Blackline leverages eConduit’s patent-pending communication method to enable transaction processing, including EMV chip card acceptance, on the MercuryPay® processing platform. This semi-integrated solution uses eConduit to connect POS applications to a variety of payment terminals that manage the transaction authorization to MercuryPay processing platform.

 

This approach means the POS application is out of scope of PA-DSS and EMV card brand certifications. Developers do not have to compromise the UX or limit value added services because our RESTful API enables tokenization and MercuryGift to be managed completely by the POS.

 

Transaction Data Flow

 

Supported Transactions

eConduit supports Credit mag-stripe data(MSD), Credit EMV and MercuryGift.

 

Credit MSD Transaction Types

Card Present (eConduit)

Tokenization (MercuryPay)

Sale

SaleByRecordNo

Authorize

PreAuthByRecordNo

Refund

AdjustByRecordNo

Void

Reversal

Tip Adjust

ReturnByRecordNo

Adjust

PreAuthCaptureByRecordNo

 

Credit EMV Transaction Types

Card Present (eConduit)

Tokenization (MercuryPay)

Sale

SaleByRecordNo

Refund

PreAuthByRecordNo

 

AdjustByRecordNo

 

Reversal

 

ReturnByRecordNo

 

PreAuthCaptureByRecordNo

 

Gift Transaction Types

Card Present (eConduit)

Card not Present (MercuryPay)

GiftActivate

Sale

GiftSale

Balance

GiftBalane

Return

GiftAddValue

Reload

GiftRefund

Void

 

 

Integration Process

 

As mutual partners, developers will work closely with both Blackline and Vantiv Integrated Payments to integrate their solution. First, developers integrate to eConduit, which will manage all non-sensitive commands from the business management solution and then MercuryPay to process follow on transactions with tokens and Vantiv StoreCard (optional).

 

Note: ISVs interested integrating to Vantiv Integrated Payments and Blackline will need to contact integrationteam@vantiv.com to order test hardware and test cards first.

 

Below we will provide the basic steps to integrate using Blackline’s JSON web API and MercuryPay JSON interface. For detailed explanation on how to integrate to eConduit, click here to view the eConduit API.

 

Step One – pairTerminal

eConduit offers two implementation options, a payment window and Web API, both methods support the same transaction functionality. It is recommended to speak with a Vantiv IP solution consultant and Blackline to identify the best integration path that fit your needs.

 

Each pairing request requires the Dejavoo device serial number located on the back of the hardware.

 

Sample GET pairTerminal

https://econduitapp.com/services/api.asmx/pairTerminal?BusinessName=Blackline&ContactName=Joe&Address=1234%20anystreet&City=Anytown&State=Illinois&ZipCode=12345&Email=email@email.com&Phone=555-555-5555&ResellerName=ResellerID&ReferenceID=1234-4322-23423&TerminalSerialNumber=123420anystreet&City=Anytown&State=Illinois&ZipCode=12345&Email=email@email.com&Phone=555-555-5555&ResellerName=ResellerID&ReferenceID=1234-4322-23423&TerminalSerialNumber=1234

 

Step Two – runTransaction

To process a transaction request on the Dejavoo terminal you will use the runTransaction method. The parameters are exactly the same as in the Command Strings section in the eConduit API and responses follow the same logic as the Transaction Results section.

 

Sample GET runTransaction

https://econduitapp.com/services/api.asmx/runTransaction?command=sale&key={Key}&password={Pwd}&amount=2.50&refID=1234&terminalId={Id}" title="https://econduitapp.com/services/api.asmx/runTransaction?command=sale&key={Key}&password={Pwd}&amount=2.50&refID=1234&terminalId={Id}

 

Step Three – Parse Response

Below is an example response message returned to the POS from eConduit. This section highlights the required fields that need to be stored by the POS for follow on transactions through MercuryPay’s JSON/RESTFul API.

 

AuthCode – this is the assigned approval code from the Issuer. It is required for Reversal, PreAuthCapture, and Adjust on MercuryPay.

 

Amount – this is the amount of the authorization approved by the issuer. If partial authorization is supported confirm the amount matches the request amount. If they are different, another form of payment should be used to zero the remaining balance.

 

CardToken – This is the RecordNo (MToken) replacing card data for follow on transactions.

ProcessorExtraData1 - AcqRefData

ProcessorExtraData2 - ProcessData

ProcessorExtraData3  - RefNo

 

{   
"TerminalID": "1234",   
"ResultCode": "Approved",   
"AuthCode": "abc1234",   
"TransType": "Sale",   
"Amount": 25.00,   
"AmountString":"25.00",   
"CardType": "Visa",   
"Last4": "1234",   
"Name": "John Doe",   
"CashBack": 0.00,   
"CashBackString": "0.00",   
"Message": "This is a sample message",   
"RefID": "ee0252f6-38bf-4c3f-97d4-a3ecf87cf69b",   
"CardToken":"ASDF2134-AHRCW+FSD123123-NKODS",
"GiftCardBalance":23.75,   
"GiftCardBalanceString":"23.75",
"ProcessorExtraData1":"KaNb015170105002706cAAFEd5e00fJlA m000005",   
"ProcessorExtraData2":"|17|210100700000",   
"ProcessorExtraData3":"0058",   
"SignatureData":"iVBORw0KGgoAAAANSUhEUgAAAI4AAA<snipped>QmCC=",   
"Track1": null,   
"Track2": null,   
"EMV_TC": "B9AB420B0937438F",   
"EMV_TVR": "0800008000",   
"EMV_AID": "A0000000031010",   
"EMV_TSI": "F800",   
"EMV_ATC": "0016",   
"EMV_App_Label": "Visa Credit",   
"EMV_App_Name": "Visa Credit",   
"CardBin": "476173",   
"EntryMethod": "Chip",   
"receiptTerminal":"Blackline Partners
  
Client ID:  13318900010001 
Cashier ID:  
Lane:                            Store:    


05/01/2015                      16:56:25                     
  SALE
      Invoice: 78   


Account:  VISA 401200******0026 
Cardholder:  TEST CARD   /VISA 
Result:  CAPTURED Authorization Code:  000271 

"  
}

 

 

Supported Hardware

Today, Vantiv Integrated Payments supports Dejavoo Systems, Inc. hardware when processing through Blackline’s eConduit. Each device supports EMV, NFC, MSD swipe and manual entry. The images below link to each device landing page for more details about their capabilities. To request a test device, please contact integrationteam@vantiv.com Or, visit the Blackline Terminal List.

 

z8.jpg

Z8 IP Terminal

 

z9.jpg

Z9 WiFi Terminal

 

z11.jpg

Z11 IP Terminal

z6-side.jpg

Z6 IP PIN pad

9 people found this helpful

Attachments

    Outcomes