> 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/ecommerce-and-verifone-central-release-notes/readme.md).

# eCommerce & Verifone Central Release Notes

{% updates format="full" %}
{% update date="2026-03-01" %}

## Verifone Release Notes for Q1 2026

See what’s new and improved in our latest update.

### Improved Amount Entry in PBL and Virtual Terminal

* We’ve enhanced the amount entry experience in Pay By Link and Virtual Terminal to prevent unintended formatting and ensure more accurate transaction values. Merchants can now enter amounts without automatic placeholders interfering, reducing input errors and ensuring transaction values are captured correctly.

### Dynamic Guidance on Payments Dashboard

* We’ve enhanced the description text when selecting the organization and currency to dynamically reflect the user’s selections on Payments dashboard page, in Verifone Central. This ensures clearer guidance when required information - such as organization or currency - is missing, and provides more helpful feedback.

### Small updates across Verifone Central

* We’ve introduced a set of small enhancements to improve clarity and navigation throughout Verifone Central. The failure screen for declined or unsuccessful transactions displays the specific failure reason directly in the message, making it easier for users to understand what happened and take action. Additionally, updates in the Report Scheduler provide clearer scheduling details, making navigation more intuitive and efficient.

### "Virtual" Sales Channel Added to Orders/Transactions

* We’ve added the new “Virtual” sales channel to the channel list on the Orders/Transactions page in Verifone Central. This enables merchants with access to both terminals and the dashboard to easily distinguish the refund channel, improving tracking accuracy
  {% endupdate %}

{% update date="2025-11-01" %}

## Verifone Release Notes for Q4 2025

See what’s new and improved in our latest update.

### Verifone + PayPal: Powering Omni-Channel Payments in the US

* Verifone and PayPal have partnered to support omni-channel merchants. As part of the first phase of the integration, we now support processing cards and Alt Pay for merchants in the US via this partnership.

### Dynamic Currency Conversion Support in APAC with Westpac

* Verifone Central now supports Dynamic Currency Conversion (DCC) for merchants in APAC using Westpac as their acquirer. Transactions processed via the Neo V660P-A terminals will automatically reflect DCC details on the *Orders/Transactions* page in Verifone Central, with dedicated DCC fields also available for selection in the *Custom report* template. Check our [Supported acquirers](https://verifone.cloud/docs/online-payments/acquirers), [Reporting details](https://verifone.cloud/docs/portal/reports/transaction-reports/report-columns) and [Exporting reports](https://verifone.cloud/docs/portal/reports/transaction-reports/exporting-reports) documentations for more information.

### 3RI Support for 3DS Transaction

* Verifone now supports 3DS Requestor Initiated authentication flow to enable 3DS transactions for marketplaces where the 3DS request is made at the marketplace but the transactions are completed on a merchant of the marketplace.

<details>

<summary>Improved</summary>

* To ensure Verifone Central UI consistency, we're standardizing dropdown components across the application, replacing multiple button variations with a unified design. This change improves usability, enhances the user experience, and simplifies component maintenance.
* In accordance with compliance and security guidelines, we are updating the minimum password requirements for both the Create, Set, and Expired Password journeys. The updated minimum required password length is now 14 characters. See more in the [Account security](https://verifone.cloud/docs/verifone-central/verifone-central/getting-started/account-security) documentation.&#x20;
* To strengthen platform security and protect user data on the production environment, we have blocked the creation of new accounts using fake domains, including Yopmail, Getnada, and Guerrillamail, in Verifone Central. The existing users on production with fake domains were disabled. Read more in [Users and merchants roles](https://verifone.cloud/docs/verifone-central/verifone-central/manage-your-account/administration/users-and-merchants-roles).
* To enhance consistency across all Verifone Central portal pages, the Entities API response now includes two new parameters supporting organization-level filtering. Additionally, a new **"Friendly Name"** field has been added to the *Organizations* page, allowing merchants to assign nicknames to organizations. This helps differentiate between entities that share the same legal name, improving clarity and usability in the organization drop-down filter. Find our more in our [Organizations](https://verifone.cloud/docs/verifone-central/verifone-central/manage-your-account/administration/organizations) article.
* We introduced mobile number verification through a One-Time Passcode (OTP) to improve data accuracy and strengthen user validation. Users who add a contact number in the **My Account** section are now required to verify it via OTP. \
  For **Petro site admins**, we enforce this verification. Admins without a verified mobile number will be automatically redirected to the **My Account** page in edit mode, where they must add and verify their contact number. This redirection will persist until the number is successfully validated.
* Verifone now supports externally provisioned 3rd party tokens to be used in a signup and charge flow of the checkout product.
* Intercard merchants can now use webhooks to get status updates on certain events/actions, and automate business processes like order management, accounting, or downloading reports. Using webhooks helps connect with systems and services more efficiently.
* The **Payment Account Reference** field is now available for Barclays acquirer in the Verifone Central reports. This enhancement provides more comprehensive reporting, improves data visibility, and supports easier tracking and analysis of key metrics.
* We enhanced the Merchant Admin role with broader permissions enabling merchants and partners to better manage their estate within Verifone Central, improving operational efficiency and reducing reliance on internal support. Find out more on the new permissions in the [User roles and permissions](https://verifone.cloud/docs/device-management/device-management-user-guide/user-roles-and-permissions) documentation.

</details>
{% endupdate %}

{% update date="2025-09-01" %}

## Verifone Release Notes for Q3 2025

See what’s new and improved in our latest update.

### Direct Organization Role Assignment

* To ensure more flexibility and security in managing organizational roles, users can now be assigned directly to specific organizations having targeted access while maintaining consistent permissions across all assigned entities. For more details, check our [Users and merchants roles](https://verifone.cloud/docs/verifone-central/verifone-central/manage-your-account/administration/users-and-merchants-roles) documentation.

### Automated Cardinal 3DS Onboarding for Westpac

* Merchants who use Westpac as an acquirer, can now be onboarded faster with the automated Cardinal 3DS setup process, via API. By simply creating a 3DS contract in the Verifone Central UI, the onboarding is completed - enabling sale readiness. See our [3DS Contracts](https://verifone.cloud/docs/verifone-central/verifone-central/manage-your-account/administration/3ds-contracts) article for additional details.

### Analytics Token for Nordic Loyalty

* Merchants in the Nordics can now request and receive only an "Analytics" token for loyalty purposes, so that they can analyze customer behavior without enabling token reuse.

<details>

<summary>Improved</summary>

* We have added new filter options to the *Organizations* page, in Verifone Central, improving usability and efficiency for administrators by enabling quicker data access and streamlined management of organization records. Read more in our [Organizations](https://verifone.cloud/docs/verifone-central/verifone-central/manage-your-account/administration/organization-company-and) documentation.
* Verifone enabled deferred authorization according to scheme mandates for Landsbankinn, Swedbank, Nets, EVRY, Elavon.
* Merchants can now view full text on the *Orders / Transactions* pages, in Verifone Central, by simply hovering over truncated content - making navigation smoother and refining the interface for better clarity.
* We have enhanced the *Audit log* page, in Verifone Central improving usability and clarity, enabling users to quickly access and interpret audit data. Check the updates in the [Audit Log](https://verifone.cloud/docs/portal/reports/audit-log) article.
* We have added a **Clear Filter** button on the *Payments Dashboard* page improving usability by allowing merchants to reset their search quickly, saving time and reducing friction during search sessions.
* Verifone enabled the use of "Online refunds" according to schemes mandates for Barclays, Globalpay, Lloyds, Worldpay and Elavon.
* We have added back for Merchant Admin users the possibility to send password reset emails directly from Verifone Central, enhancing overall user experience by providing a faster way to reset credentials.
* We have implemented small usability enhancements to Verifone Central, such as increased consistency in the dropdown filters, to ensure customers benefit from an improved, seamless experience.
* Verifone enabled the use of Merchant Payment Gateway ID according to Mastercard mandate on Barclays, Globalpay, Lloyds, Worldpay and Elavon.

</details>
{% endupdate %}

{% update date="2025-06-13" %}

## Verifone Release Notes for May-June 2025

See what’s new and improved in our latest update.

### Product information in Verifone Central

* To help merchants benefit from an improved user experience, the product information can now be stored in Verifone Central, in order to be further reused in Pay By Link and Virtual Terminal and searched in a page of it's own, *Product Catalog*. For more details, check our [Product catalog](https://verifone.cloud/docs/online-payments/pay-link/product-catalog) documentation.

### New API parameter

* We added the **User ID** field in *My Account* in Verifone Central, which can be used in the API calls. This way, the **User ID** detail can be fetched effortlessly, enhancing flexibility and ease for merchants. See our [Getting started](https://verifone.cloud/docs/verifone-central/verifone-central/manage-your-account/getting-started) article for additional details.

<details>

<summary>Improved</summary>

* Merchants with Landsbankinn acquiring option now have the possibility to refund, capture, void and cancel transactions from terminals in [Verifone Central](https://verifone.cloud/docs/portal/common-portal-guide/verifone-central-overview) and [eCommerce API](https://verifone.cloud/api-catalog/verifone-ecommerce-api), improving adaptability and convenience for merchants to manage transactions.
* We have enhanced our reporting capabilities by making the **surcharge\_amount** field available in the *Custom Report* templates, as well as adding additional fields, in order to expose more of the 3DS details, for merchants to easily filter out the 3DS transactions. Read [Exporting reports](https://verifone.cloud/docs/portal/reports/transaction-reports/exporting-reports) to review our available fields in the custom template.
* The new **Wallet** filter is now available in the report scheduler to allow filtering transactions by wallet type, allowing merchants to add additional filters to their search results, facilitating a more focused analysis. See more in [Report Scheduler](https://verifone.cloud/docs/portal/reports/report-scheduler).
* We improved the accessibility in different pages, such as the Verifone Central portal and Checkout pages, allowing visitors to access the information they need and to help ensure a positive experience.
* We’ve introduced a new **Danger Button** color option in the [Whitelabel](https://verifone.cloud/docs/portal/administration/white-label-feature) settings panel. This allows merchants to customize the danger button color from the **Custom Styles** panel based on their branding requirements. The selected color will be applied to all danger buttons across the whitelabeled website.

</details>

<details>

<summary>Fixed</summary>

* Fixed an issue that prevented a capture from being allowed when the `captureAmountModifier` field contained a value in the transaction record.
* Fixed an issue that prevented the TAVE tokens from displaying correctly in the Order / Transaction reports in Verifone Central.

</details>
{% endupdate %}

{% update date="2026-05-01" %}

## Verifone Release Notes for February-March 2025

See what’s new and improved in our latest update.

### Customer Catalog Information

* To help merchants benefit from an improved user experience, the customer information can now be stored in Verifone Central, in order to be further reused in Pay By Link and searched in a page of it's own. Find out more details in the [Customer Catalog](https://verifone.cloud/docs/online-payments/pay-link/customer-catalog) documentation.

### Payment Account Reference

* Verifone is adding support for Payment Account reference (PAR) to be returned in the authorization response for Landsbankinn-acquired eCommerce transactions. Read more in our [Supported Acquirers](https://verifone.cloud/docs/online-payments/acquirers) documentation.&#x20;

<details>

<summary>Improved</summary>

* Verifone is adding an end-of-day cut over time for Barclays. Merchants who were able to choose the 00:00, 03:00, 06:00 cut overs before can now also have the possibility to choose the 19:00 cut over.
* Fiserv US acquirer now supports Private Label Credit Cards (PLCC) through Synchrony, via eCommerce. See more in the [Supported Acquirers](https://verifone.cloud/docs/online-payments/acquirers) documentation.
* Using the new show\_confirmation\_page field, via [Checkout API](https://verifone.cloud/api-catalog/checkout-api), allows merchants to hide our default iFrame *Thank you* page displayed after payment and provide their own.
* By default, we provide a *Pay* button. The new [Checkout API](https://verifone.cloud/api-catalog/checkout-api) handle\_order\_confirmation field allows merchants to remove our *Pay* button and use event listeners/messages to initiate a payment from outside the iFrame.
* We now support payment actions from the *Transactions* view, in the *Orders/Transactions* page, in Verifone Central, similar with the *Orders* view function. Allowing payment actions under both the transaction and order view detail pages enhances flexibility and ease for merchants to manage transactions between both views. See our [Orders/Transactions Reports](https://verifone.cloud/docs/portal/reports/transaction-reports) documentation for more information.
* The order/transactional data now loads only after applying all desired filters, in the *Orders/Transactions* page, in Verifone Central. As a result, the displayed data is accurate and complete, ensuring a smooth and reliable experience for merchants with large datasets. Find out more in the [Reporting filters](https://verifone.cloud/docs/portal/reports/transaction-reports/transaction-filters) documentation.
* Added the *Cashback* and *Gratuity* amounts filters to the *Orders/Transactions* page, in Verifone Central, allowing merchants to add additional criteria to their search results and have a more targeted analysis. Check the [Reporting filters](https://verifone.cloud/docs/portal/reports/transaction-reports/transaction-filters) page for more details.
* Updated the title for the *Reason for refund* field in transaction details from *Description* to *Refund/Amount Description*, making the field more user-friendly and easier to pinpoint for merchants. Read more in our [Reporting details](https://verifone.cloud/docs/portal/reports/transaction-reports/report-columns) documentation.
* On the *Settlements* page, in Verifone Central, for merchants who have more than 10.000 entities associated with their account, the filters now display before loading any results, as with the *Order/Transaction* display screen, for a smoother user experience.
* A new warning message is displayed on the *Change password* screen guiding merchants on how to create stronger passwords to ensure their accounts are safe and secure.
* When using [Pay by Link](https://verifone.cloud/docs/online-payments/pay-link/create-payment-link), merchants will now have the box *Automatically send transaction for capture* selected by default, enabling a more seamlessly interaction when dealing with payment links.
* We enhanced the date filter in the *Orders/Transactions* and *Settlements* pages along with the payments Dashboard and included now the option to filter the results by time, assuring data accuracy and reliability.

</details>

<details>

<summary>Fixed</summary>

* We’ve implemented changes for the components in our *Whitelabeled* application to adopt the colors set in the custom styles for the whitelabeled entity, while other colors to align with Verifone Central. This way we can assure consistency across all pages, so that the type and color scheme for buttons, dropdowns, tables, filters, text, borders, etc. are the same.&#x20;
* Fixed multiple UI/UX issues in Verifone Central to accommodate an improved user experience and interaction for our merchants.

</details>
{% endupdate %}

{% update date="2025-01-13" %}

## Verifone Release Notes for December 2024-January 2025

See what’s new and improved in our latest update.

### Support for Worldpay

* Verifone added support for Worldpay non-fleet merchants to process Voyager transactions. See more in the [Supported Acquirers](https://verifone.cloud/docs/online-payments/acquirers) documentation.

### Partial capture in API

* Added the Partial Capture feature that enables merchants to perform multiple partial captures directly from Verifone Central, extending the current [eCommerce](https://verifone.cloud/api-catalog/verifone-ecommerce-api) API functionality to support split shipments for Fiserv US, Fiserv CA, Chase US, and Chase CA, with no limit on the number of captures as long as the total does not exceed the authorized amount. For more information, check our [Capturing an authorization](https://verifone.cloud/docs/online-payments/payment-actions/capturing-authorisation) documentation.

<details>

<summary>Improved</summary>

* Verifone unattended EVC merchants will now be able to process unattended sales transactions through the Swedbank acquiring connection. For more details, check our [Supported Acquirers](https://verifone.cloud/docs/online-payments/acquirers) page.
* Merchants can now set up templates via the Checkout API, defining the needed fields and choosing what shopper details to capture, directly on the Hosted Payments Page (HPP). Find out more about *Templating* in the [Checkout API](https://verifone.cloud/api-catalog/checkout-api) documentation.
* To help merchants have clearer information on their transactions, we have added the following new fields in Verifone Central, in the "Orders/Transactions" details: *Cashback*, *Gratuity Amount*, *Scheme ID*, *Origin,* and *Charitable Donation*. Find out more details in the [Reporting details](https://verifone.cloud/docs/portal/reports/transaction-reports/report-columns) documentation.
* As per the new legislation, the value-added tax (VAT) for Israel increased from 17% to 18%. This update is now available via [Pay by Link](https://verifone.cloud/docs/online-payments/payment-documents/invoice4u/use-invoice4u-pay-link) and [Virtual Terminal](https://verifone.cloud/docs/online-payments/virtual-terminal/invoice4u), so merchants who do not use the Invoice4U payment documents can perform transactions with updated tax rates and tax amounts.&#x20;
* We have enhanced our reporting capabilities by making *Gratuity*, *Cashback*, and *Donation amounts* available via the [eCommerce](https://verifone.cloud/api-catalog/verifone-ecommerce-api) API, in the GET/LIST Transaction API responses, providing merchants with financial details for improved transaction visibility and operational efficiency.
* We have updated the message on the "Forgot Password" page, in Verifone Central to make it more user-friendly. The updated message now reads: “*Please enter your email address in the field below. You will receive an email with further instructions on how to reset your password*”.
* To help merchants benefit from an improved user experience, we made the API key expiration warning emails easier to spot by personalizing the email Subject and Contact information.

</details>

<details>

<summary>Fixed</summary>

* Fixed multiple display issues in Verifone Central to accommodate an improved user interaction for our merchants.
* Fixed a defect preventing the stuck transactions from displaying the timeout failure.

</details>
{% endupdate %}
{% endupdates %}


---

# 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 dynamically by asking a question.

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

```
GET https://docs.verifone.com/ecommerce-and-verifone-central-release-notes/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
