# What’s New In Release: 54.02.01

<h2 align="center">Enhancement</h2>

### EPS System <a href="#bookmark35" id="bookmark35"></a>

Chip-based approvals are no longer supported for EMV cards.

<h2 id="bookmark36" align="center">Resolutions</h2>

### Loyalty <a href="#bookmark37" id="bookmark37"></a>

Mobile Transaction details were not displaying in the POS Loyalty PPU Transaction Detail Report and Terminal Batch Loyalty Detail Report. This was corrected.

### C18 Self Checkout <a href="#c18_self_checkout" id="c18_self_checkout"></a>

User was unable to access the Glory cash recycler browser through the POS. The error message “Your Internet access is blocked” displayed. This was corrected.

### Dispenser Card Readers <a href="#bookmark39" id="bookmark39"></a>

1. “Enter Data” was prompted instead of “Enter PIN” for contactless PIN transactions when PIN bypass was enabled for the card on Wayne DCRs. This was corrected.
2. When the DCR parameter “Approve All Sales” was enabled, the pump authorization for the second and any additional fuel products selected were not correctly using the original fuel product detail created. It was creating a new fuel product detail and not retaining the expected individual fuel grade limits provided from the host. This was corrected.

<h2 id="bookmark40" align="center"> FEP Specific Changes</h2>

### Rapid Connect FEP <a href="#bookmark41" id="bookmark41"></a>

#### Resolution <a href="#bookmark42" id="bookmark42"></a>

When a new BIN file that excluded 8-digit BINs was received and loaded for a TAVED Gilbarco M5, Debit Network Alliance cards were failing with a Try Again PIN error message. This was corrected.

### Verifone EPS

#### Resolution <a href="#bookmark43" id="bookmark43"></a>

Transaction numbers were exceeding 6-digits and were not settling after Store and Forward. This was corrected.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-and-integrated-pos/commander-release-notes/verifone-commander-release-54.02.03/whats-new-in-release-54.02.01.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.