The Portico API supports clients that interact with EMV capable terminals through the EMV data elements defined on Credit based services of the Portico API. If an EMV capable client/terminal is interfacing with a chip card, then the EMV tag data must be present in the transaction (e.g., CreditSale, CreditAuth, CreditReturn, DebitSale, DebitReturn, and DebitReversal. For a normal EMV transaction, the transaction should contain the EMV tag data obtained from the terminal/chip card. However, if the terminal has an issue reading the chip card, then the chip card can be processed as a normal swipe transaction with the EMV chip condition indicating whether the previous read of a chip card failed or succeeded.

For additional information, see the Heartland Integrator's Guide.

• Service Tag Validation
• EMV Conversation Flow
• Services That Support EMV Tags
• EMV Tags
• EMV Request Tags
• EMV Response Tags
• EMV Parameter Data Download
• ParameterDownload Service
• PDL Request Definition
• PDL Response Definition
• PDL Response Table 10—Table Versions and Flags
• PDL Response Tables 30-60
• PDL Response Table 30—Terminal Data
• PDL Response Table 40—Contact Card Data
• PDL Response Table 50—Contactless Card Data
• PDL Response Table 60—Public Key Data
• PDL Response—Confirmation