Getnet DocsGetnet Docs

Card and EMV Handling

View as MarkdownView this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this pageOpen in PerplexityAsk questions about this page
Connect to CursorUse these docs in CursorConnect to VS CodeUse these docs in VS Code

The Pinpad Getnet solution manages diverse card reading technologies and orchestrates complex EMV protocol flows to ensure secure transactions. This module handles physical card interactions and the underlying logic for processing card data.

CardReader module and reading technologies

The CardReader module serves as the hardware abstraction layer responsible for initializing, preparing, and managing interactions with the physical card readers. It monitors the status of the readers, including detecting when a card is inserted or removed.

Early card removal during an EMV Contact (CHIP) transaction will trigger a failure and an immediate report to the Host System.

The Newland N750P terminal supports three primary interfaces:

  • Contact Chip (CHIP): Reads the card’s integrated circuit when inserted into the smart card slot.
  • Contactless (CTLSS): Facilitates transactions via NFC (Near Field Communication) technology when a card or digital wallet is tapped or held near the terminal antenna.
  • Magnetic Stripe (BANDA): Processes data from the card’s magnetic stripe when it is swiped through the reader.

EmvL3Flow module

The EmvL3Flow component facilitates the complete EMV Level 3 flow required to process a transaction. Its core responsibilities include:

  • EMV Configuration: Loading Application Identifiers (AIDs) and Certification Authority Public Keys (CAPKs) from the emvCfg.xml resource file, located in: <directorio>\pinpadgetnet\app\src\main\assets
  • Card Technology Management: Identifying CHIP or CTLSS cards and initiating the appropriate EMV process.
  • Protocol Execution: Coordinating all EMV stages, including card authentication, cardholder verification (CVM), and authorization.
  • Automatic PIN Request: Automatically launching a PIN request if the card’s protocol requires it.

Initial Parameter Loading: CHIP (EMV) parameters, public keys, and BIN information are provided by Getnet via an initial load file through the defined communication channel.

Technology fallback

Fallback occurs when the terminal requests a change in the card entry method because the initially attempted technology cannot be used.

Certified brands (VISA, MASTERCARD, AMEX)

For these certified brands, the terminal follows a specific protocol sequence:

  • CHIP to BANDA: If errors occur while reading the chip in EMV contact mode, the terminal prompts the user to swipe.
  • CTLSS to CHIP: If an error occurs during contactless application selection, the terminal prompts the user to insert the card.

Non-certified brands

For brands not certified for this terminal, both the NFC and CHIP readers will force an operation of fallback to BANDA (swiping the magnetic stripe) upon a reading failure.

Restricted band reading

To maintain high security standards, the Pinpad does not permit transactions via magnetic stripe (BANDA) if the card possesses an EMV chip.

If a chip-enabled card is swiped, the terminal displays the error message “Lectura de Banda no Permitida” (Band Reading Not Permitted) for one second. After this interval:

  1. The system automatically returns to the waiting screen showing the message: “Ingresá o apoyá la tarjeta”.
  2. The user can attempt the transaction via chip or contactless.
  3. If this occurs three consecutive times, the operation is automatically canceled, and the terminal displays the screen corresponding to a cancellation.

Card data protection

The card data read here is never returned in clear. Track I and Track II are encrypted with RSA, and the PAN inside those tracks is masked with zeros; the real PAN is returned separately as a 3DES DUKPT cryptogram (ENC-PAN) with its own KSN-PAN. EMV data is also encrypted with RSA. For the full encryption model, see Pinpad Encryption.

  1. Pinpad Encryption: the two encryption schemes, key slots, and how the PAN is masked inside the tracks.
  2. Security and PIN Model: how sensitive data is protected via RSA encryption and DUKPT key management.
  3. Process Card Payments: start implementing specific transaction flows.