VIPA Getting Started

VIPA is Verifone's interface for POS integration with Verifone payment devices. It lets integrators accept EMV debit and credit cards on Verifone terminal

Please login or register to gain access to the detailed material on this page.

LoginRegister for an Account

Before you Begin

Confirm these three things first:

• your target device family

• your deployed VIPA version

• your integration model

VIPA supports two integration models:

• terminal-managed EMV processing on the Verifone device

• external-kernel processing with the device used for secure card and PIN handling

Choose the Right Specification

Start with the specification that matches your estate.

What the specification gives you

• protocol structure for POS-to-device messaging

• transaction flows for contact, contactless, and mixed-card scenarios

• command reference for device and payment features

• configuration, authentication, and security requirements

Pick one specification version as your source of truth.

Do not mix command rules across versions.

7.x Interface Specification

1

Understand the Product Model

Discover how VIPA fits your POS architecture and transaction model.

Login

2

Prepare the Terminal Environment

Set up communication, configuration files, and deployment expectations first.

Runtime setup

Use the configuration section for runtime setup.

Login

Package rollout

3

Build the Transaction Flow

Map your POS state machine to VIPA behaviour.

Start with contact and contactless flows.

Login

4

Implement the Command Layer

Use the command reference after you understand the flow.

Start with templates, core EMV transaction commands, and device interaction.

Login

5

Add Security and Validate Behaviour

Add security, authentication, and compliance checks before pilot rollout.

Keep PCI requirements and appendices close during testing.

Login

6.9x Interface Specification

6.8x Interface Specification

POS Integration Checklist

Use this checklist before certification or pilot rollout.

• Confirm the target device family and VIPA version.

• Choose one specification version as the primary reference.

• Configure communication and required runtime settings.

• Implement message framing and template handling.

• Build the transaction flows your POS supports.

• Add only the command groups you need.

• Validate error handling and unsolicited message behavior.

• Apply security, authentication, and PCI requirements.

• Test contact, contactless, fallback, and cancellation flows.

• Keep the appendices available during debugging.