> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/feature-references/features-and-products-references/bluefin-encryption.md).

# Bluefin Encryption

PCI-DSS 4.0 has introduced many new requirements which can be reduced if payment devices have implemented Point-to-Point Encryption (P2PE).

## Overview

### Feature Description

PCI-DSS 4.0 has introduced many new requirements which can be reduced if payment devices have implemented Point-to-Point Encryption (P2PE). Bluefin has teamed up with Heartland to provide P2PE on Heartland Value Added Payment System (VAPS) and Network Services (NWS) platforms.

For Verifone Release 56.03, Verifone has implemented the P2PE solution using Bluefin for Phillips 66. For this release the encryption is only implemented for indoor PIN pads.

This solution requires the installation of Feature Enablement Token (FET) package, Bluefin key (DATA DUKPT / P2PE) and associated configuration files on the PIN pad. This installation is in addition to the usual 3DES DUKPT debit keys that are used for debit PIN encryption. Sites should get in touch with P66 to install the required packages on the PIN pad.

If any indoor PIN pad is enabled for ADE encryption (the encryption Bluefin uses), then all the active PIN pads at that site must also be using the ADE encryption. Mixed implementation are not allowed where some PIN Pads are encrypted and some are not.

### Requirements

**Supported Hardware Configurations**

* Verifone Commander with C18

**PIN pad**

* P400
* M400

**Software Requirements**

* Verifone Commander Release 56.03 and above
* EVPAY 2.08.00 R09 kernel 703


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verifone.com/feature-references/features-and-products-references/bluefin-encryption.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
