Portico Developer Guide
Services That Support EMV Tags
Services that support passing of EMV tags are below:
EMV tags should be passed in the TagData field.
For EMV, CreditAuth/CreditSale transactions, either the EMV chip condition or tag data is required. This data is required when the Portico client is interfacing with an EMV chip card/terminal. The tag data will be included in the request to the issuer and any issuer response tags will be returned to the client.
CreditTxnEdit allows for updating EMV tag data already persisted on the database from the original CreditAuth or CreditSale. The EMV tag data on the request consists of the TLV field list associated with security data and/or script results obtained from the chip card/terminal upon applying the issuer response from the CreditAuth or CreditSale.
Like the CreditTxnEdit, CreditAddToBatch allows for updating EMV tag data already persisted on the database from the original CreditAuth. CreditAddToBatch allows for an alternate flow for editing EMV tag data on a CreditAuth which is not automatically added to the open batch like CreditSale. Thus for CreditAuth, two flows are allowed when editing EMV tag data:
There may be many reasons for reversing an EMV transaction (communication errors, etc.). For normal reversals no additional requirements or passing of EMV tag data are required when reversing EMV transactions. However, if the reversal is due to a chip card declining a transaction upon applying issuer response tags obtained online, then the resulting EMV tag data obtained from the terminal/chip card when applying the issuer response tags should be sent on the CreditReversal request.
The CreditOfflineAuth and CreditOfflineSale services allow for "offline" chip card approvals. If the chip card approves the transaction offline (e.g., does not require the authorization to go online for approval), then the offline authorization services must be called with the resulting EMV tag data obtained from the terminal. The tags recorded by these services are utilized in the settlement process.
The ChipCardDecline service allows for the recording of an "offline" chip card decline. This occurs when the chip card declines the transaction without requesting that the transaction go online.
The ChipCardDecline is an inactive transaction and is for recording purposes which may be required by some issuers.
The CreditReturn service allows for EMV Credit Return transactions to be initiated using an EMV chip card. EMV CreditReturn transactions are stand-alone transactions, meaning they do not depend on the card data or tags obtained from a previous transaction via a Gateway Transaction Id. For an EMV CreditReturn to take place, both card data and EMV tag data must be present in the request.
If the CreditReturn is based solely on a reference transaction via a Gateway Transaction Id and the referenced transaction is an EMV transaction, then the CreditReturn will be based solely on the card information of the referenced transaction.
For EMV, DebitSale transactions, either the EMV chip condition or tag data is required. This data is required when the Portico client is interfacing with an EMV chip card/terminal. The tag data will be included in the request to the issuer and any issuer response tags will be returned to the client.
The DebitReturn service allows for EMV Debit Return transactions to be initiated using an EMV chip card. EMV DebitReturn transactions are stand-alone transactions, meaning they do not depend on the card data or tags obtained from a previous transaction via a Gateway Transaction Id. For an EMV DebitReturn to take place, both card data and EMV tag data must be present in the request.
If the DebitReturn is based solely on a reference transaction via a Gateway Transaction Id and the referenced transaction is an EMV transaction, then the DebitReturn will be based solely on the card information of the referenced transaction.
There may be many reasons for reversing an EMV transaction (communication errors, etc.). For normal reversals no additional requirements or passing of EMV tag data are required when reversing EMV transactions. However, if the reversal is due to a chip card declining a transaction upon applying issuer response tags obtained online, then the resulting EMV tag data obtained from the terminal/chip card when applying the issuer response tags should be sent on the DebitReversal request. In addition, for Canadian Debit transactions, when the reversal is due to Customer Cancellation, the card must be present and card data and tags must be included in the reversal request.
The Portico reporting services indicate whether the transaction has EMV tag data associated with the transaction. In addition, EMV tag data will be returned when requesting detailed information about a transaction through the ReportTxnDetail service. The following is a list of those reporting services that include EMV Tag information: