Introduction

Welcome to Bluefin® PIN Translation!

Overview

PIN translation is a critical security function in payment processing that enables a Personal Identification Number (PIN) to be securely transferred between different encryption domains without ever exposing the PIN in plaintext.

This process ensures that sensitive cardholder data remains protected throughout the transaction lifecycle while allowing multiple payment systems to communicate using their own encryption keys and security requirements.

PIN translation is primarily used in ATM transactions, point-of-sale, unattended payment terminals, and other PIN-based debit transactions.

Key Features of PIN Translation

In a nutshell, PIN Translation:

  • Securely transfers an encrypted PIN Block between different encryption domains without exposing the plaintext PIN

  • Translates a PIN Block from one key set to another within a secure cryptographic environment that is Hardware Security Module

  • Maintains end-to-end PIN confidentiality throughout the payment process

  • Commonly used in ATM, POS, unattended payment terminals, and other PIN-based payment transactions

  • Supports compliance with industry security standards while facilitating secure PIN verification


Problem It Solves

PIN debit transactions can originate under one source PIN-key domain while the selected processor or acquirer requires a different destination key domain. Managing those differences can complicate processor migrations, secondary-processor strategies, regional processing arrangements, and other multi-processor models.

Bluefin performs the HSM-backed translation and returns the translated PIN block.

Customers can use an existing device PIN key or a generic Bluefin-injected key as the configured source PIN-key domain. Destination PIN keys are maintained within Bluefin's secure environment. Because the source and destination key domains can differ, customers may retain the source device key when adding or changing processor destinations.



How it works

PIN Translation is the secure process of translating an encrypted PIN block from one encryption domain (card reader device) to another (processor) without ever exposing the clear PIN outside of the HSM.

It consists of the following key steps:

  • Device Encryption: The PIN block is encrypted at the card reader device - typically using a unique DUKPT-derived transaction key.
  • PIN Block Decryption: The encrypted PIN block is securely decrypted inside Bluefin's PCI-certified secure environment.
  • Re-encryption under Processor Key: Within the secure HSM boundary, the PIN block is re-encrypted under the payment processor's Zone PIN Key (ZPK).

In other words, PIN Translation refers to the re-encryption of the PIN block from the device encryption domain into the processor's encryption domain. The resulting output is referred to as the translated PIN block.


Supported Encryption Methods

Our platform supports multi-processor PIN translation, translating device-encrypted PIN blocks from a supported source key to the destination processor’s ZPK. Depending on the existing device key configuration, this may reduce or eliminate the need to rekey deployed devices when adding or changing processors.

Bluefin supports flexible PIN Translation options to meet various processor and acquirer requirements:

  • DUKPT-to-DUKPT — for processors using their own DUKPT key hierarchy
  • DUKPT-to-ZPK — for translation to the traditional Zone PIN Key used by most payment networks and issuers
    • DUKPT: This is when the PIN Block is encrypted at the terminal device using a unique key derived via DUKPT. This is considered to be the source encryption.
    • ZPK: This is when the PIN Block is re-encrypted within the secure HSM boundary under the payment processor's Zone PIN Key (ZPK). This is considered to be the destination encryption.
📘

Note on Acronyms

DUKPT stands for Derived Unique Key Per Transaction.

ZPK stands for Zone PIN Key.




Decryptx® PIN Translation API

Bluefin offers PIN Translation by providing a fully managed ready-to-use API service, allowing merchants to securely translate PIN Blocks without the burden of implementing and maintaining:

  • Processor-specific Integrations
  • Cryptographic Infrastructures
  • Complex PIN Translation Workflows
  • Different Devices in the field

Decryptx PIN Translation API is a managed cryptographic capability for card-present PIN debit transactions that must move between different source and destination PIN-key domains.


📘

Target Payment Facilitators

Decryptx PIN Translation API is intended primarily for processors, gateways, acquirers, PayFacs, and payment platforms that already operate their own routing and processor-integration layer. Customers retain full control over routing, processor-message integration, processor communication, and authorization handling.

This lets you support all kinds of payment relationships, reduce integration friction, and adapt quickly to new business needs—without adding extra operational complexity.



The PIN Translation API securely translates an encrypted PIN block from the device encryption domain into a processor encryption domain. This operation is performed entirely inside Bluefin-managed Hardware Security Modules (HSMs). The clear PIN is never exposed outside the HSM boundary.


📘

Transaction Processing

PIN Translation is typically performed during transaction processing, prior to routing the transaction to the processor.


Bluefin seamlessly integrates PIN Translation directly within its powerful TrustConex solution — a complete, end-to-end card-present payment solution. It combines our proprietary P2PE hardware with PCI-certified software for card-present POS systems.

Bluefin PIN Translation provides exceptional flexibility — it plugs effortlessly into any Bluefin P2PE device integration straight out of the box, with zero disruption to your existing systems, workflows, or business logic.

This includes support for more than 120 certified device models across 17 leading manufacturers.

For more information on the TrustConex solution, refer to ShieldConex ORCA | TrustConex Solution and Bluefin TrustConex.


PIN Translation | Direct API Integration

Here is the step-by-step diagram for a clear breakdown of how it all works - from the terminal (device) encryption to the delivery of the translated PIN block.


  • (1) When a cardholder enters their PIN for the payment terminal at POS, the PIN is formatted into a PIN block (combined with the PAN) and encrypted using DUKPT from the Bluefin-injected key.
    • This terminal-encrypted PIN Block is sent to Bluefin HSM for PIN Translation
  • (2) Within the the Bluefin HSM, Decryptx® extracts the encrypted data and decrypts the terminal PIN Block (with the initial terminal key)
  • (3) Within the secure HSM boundary, the PIN block is translated from the supported source key domain to the configured destination processor’s key domain. The keys and clear PIN block are never exposed outside the HSM.
    • Bluefin supports ZPK and DUKPT as processor encryption domain

    • For all translation options Bluefin offers, check out the Supported Encryption Methods above

    • Bluefin HSM Processor Keys

      • Bluefin Secure Processor Keys refers to the destination keys provided by the payment processor. Bluefin stores these encrypted keys (e.g. DUKPT / ZPK / issuer interchange keys) in its secure HSM Key Store for retrieval at will.
      • Current alpha support accepts a Format 0 PIN block encrypted under the configured source PIN-key domain and returns a Format 0 PIN block encrypted under the configured destination PIN-key domain. The encryption key domain changes; the PIN-block format does not. Initial alpha support targets DUKPT and Zone PIN Key (ZPK) models.
      • For operational efficiency, processor keys are pre-loaded and managed by Bluefin on behalf of the merchant while being encrypted at all times. This removes the need for merchants to manage processor key distribution or ongoing maintenance, while helping reduce operational complexity, security exposure, and PCI-related burden.
    • As mentioned above, this re-encryption step is referred to as PIN Translation

  • (4) In the downstream authorization request, the translated PIN block is then routed through the merchant systems
    • While staying encrypted, the translated PIN Block is routed and verified through the merchant payment processor over an encrypted connection
    • To fully automate, extend, and integrate this authorization step with Bluefin ORCA while maintaining flexibility across multiple payment processors and devices, refer to the Bluefin TrustConex ORCA solution
  • (5) The authorization response, whether the PIN is verified, is echoed back to the POI device.

📘

Device Configuration

On behalf of the merchant, Bluefin handles the complete configuration of the card reader device. This includes securely injecting a Bluefin PIN Encryption Key (IPEK) into the terminal, enabling encrypted PIN Block creation and seamless translation based on the payment processor.


📘

PIN Block and PAN

  • PAN is mandatory for verification in both major methods — you cannot verify the PIN without it
  • PIN block formats often embed PAN digits to prevent certain attacks
  • Security: PAN + PIN are never stored together in cleartext. Everything stays in the HSM
  • For multiple processors: The PAN is what allows consistent verification regardless of the incoming encryption method

TrustConex ORCA Integrations

With TrustConex built-in PIN translation, merchants can enable PIN Translation across multiple payment processors without disrupting their current payment flows.

This enhancement combines PIN Translation, PIN Verification, and Transaction Processing into a unified orchestration capability, allowing Card-Present debit transactions to be securely processed end-to-end with massive PCI scope reduction. The result is a flexible and portable payment architecture that eliminates processor lock-in.

TrustConex® fully supports PIN Translation by enabling Bluefin PIN keys to be injected directly into POS devices. This allows encrypted PIN Blocks to be securely translated and routed to different processor endpoints through the ORCA layer.

Key benefits include

  • TrustConex® Orchestration supports PIN Translation with Bluefin PIN key injection for secure PIN Block translation
  • Merchants can deploy devices configured with Bluefin PIN and data keys with ORCA proxying transactions across multiple processor endpoints
  • Allows Merchants to support multiple processors from a single payment device at the same time. So the enterprise merchants can spread their business dynamically between processors as needed.
  • Merchants can switch between processors without rekeying all devices in the field
  • Maintains full PCI/P2PE and tokenization security guarantees without processor lock-in
  • Enables efficient, secure P2PE transaction processing combined with real-time PIN Translation and Verification
  • Customers retain their processor relationships, processor-message integrations, and routing logic

This integration delivers a unified, multi-processor payment orchestration that enhances security, operational flexibility, and long-term scalability for enterprise merchants and ISVs.

📘

PIN Verification and Transaction Routing

TrustConex PIN Translation itself does not verify the cardholder's PIN, authorize the transaction, or choose the processor.

Your routing rules decide where the transaction goes — the processor, payment network, and issuer handle the rest.


TrustConex PIN Translation

TrustConex PIN Translation is a managed feature within Bluefin's card-present orchestration infrastructure.

It uses Decryptx to translate an encrypted PIN block from the configured source PIN-key domain into the key domain required by the customer-selected destination, while ShieldConex ORCA manages the configured message extraction and transformation. All cryptographic processing occurs inside Bluefin-managed Hardware Security Modules and the PCI DSS environment, and the clear PIN is never exposed outside the secure HSM boundary.

The customer retains its routing rules and processor relationships.

  • (1) When a cardholder enters their PIN at a POS payment terminal, the PIN is formatted into a PIN block (combined with the PAN) and encrypted using a unique per-transaction key derived via DUKPT from the Base Derivation Key (BDK).

    • This encrypted PIN Block is sent to ShieldConex® ORCA for processing
  • (2) The ORCA Engine identifies the encrypted PIN Block and interacts with Bluefin Decryptx® to decrypt the terminal PIN Block (with the initial terminal key).

  • (3) Decryptx® translates the PIN block by re-encrypting it using the processor keys - all inside the secure Bluefin HSM environment.

    • Inside the HSM, Bluefin translates the encrypted PIN block from the source key domain into the configured destination key domain. Current alpha support accepts a Format 0 PIN block encrypted under the configured source PIN-key domain and returns a Format 0 PIN block encrypted under the configured destination PIN-key domain. The encryption key domain changes; the PIN-block format does not. Initial alpha support targets DUKPT and Zone PIN Key (ZPK) models.
  • (4) In the format required by the processor's specification, the translated PIN Block is then re-inserted into the message and sent securely over the TLS protocol to the payment processor for authorization.

    • The downstream processor and payment network route the request to the issuer, which performs PIN verification.
  • (5) The response from the processor is proxied back to the client, specifying whether the PIN has been verified or declined.

    • Orchestrations can apply encryption to payment processor responses before returning them to the merchant/POS systems. This enables response-side protection and normalization workflows, preventing any sensitive data to ever enter the merchant environment. ShieldConex Orchestration fully supports this feature.


TrustConex End-to-End Integration | PIN Translation and Transaction Processing

With ShieldConex ORCA's multi-action capabilities, merchants can perform PIN Translation and P2PE payload processing within a single transaction workflow.

The translated PIN data and P2PE payload are both re-inserted into the message and securely forwarded to the payment processor over TLS for authorization — all in a single outbound request.

This streamlined approach reduces integration complexity, minimizes network bandwidth, and enables secure, efficient transaction processing without requiring separate requests for PIN handling and payment authorization.

  • (1) The cardholder presents their card to the terminal device at POS systems
    • Bluefin applies the P2PE service to encrypt the cardholder data on hardware-level in the POI device using SRED.
  • (2) The device prompts the customer to enter their PIN. The cardholder enters their PIN at the payment terminal
    • When a cardholder enters their PIN at a POS payment terminal, the PIN is formatted into a PIN block (combined with the PAN) and encrypted using a unique per-transaction key derived via DUKPT from the Base Derivation Key (BDK).
  • (3) The encrypted P2PE payload and PIN Block are sent to ShieldConex® Orchestration for processing
    • ORCA finds the data elements in the message to properly decrypt the payload and prepare the PIN Block for translation.
  • (4) The ORCA engine extracts the P2PE payload through the Decryptx® Parser and decrypts it on the fly in combination with Bluefin's Decryptx® solution.
  • (5) ORCA interacts with Bluefin Decryptx® to decrypt the terminal PIN Block (with the initial terminal key).
    • Decryptx® then translates the PIN block by re-encrypting it using the processor keys - all inside the secure Bluefin HSM environment.
  • (6) In the format required by the processor's specification, the decrypted data with the translated PIN Block is then re-inserted into the message and sent securely over the TLS protocol to the payment processor for authorization.
    • As a single processor message, all data is sent together to the payment processor in one go.
    • Both P2PE and PIN Translation are complete at this point.
    • The downstream processor and payment network route the request to the issuer, which performs PIN verification.
  • (7) The response from the processor is proxied back to the client, specifying whether the transaction has failed or succeeded.
    • Orchestrations can apply encryption to payment processor responses before returning them to the merchant/POS systems. This enables response-side protection and normalization workflows, preventing any sensitive data to ever enter the merchant environment. ShieldConex Orchestration fully supports this feature.

Did this page help you?