> 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/vipa/vipa-getting-started.md).
# 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
{% if visitor.isSet === false %}
{% columns %}
{% column %}
Please login or register to gain access to the detailed material on this page.
Need access to this content? Contact your Verifone representative.
{% endcolumn %}
{% endcolumns %}
{% endif %}
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.
{% if visitor.isSet === true %}
* [8.x Interface Specification](broken://spaces/lgQH7gn83JbwDliEhFdR/pages/07eQYUN8tNInmEjLYRth)
* [7.x Interface Specification](broken://spaces/lgQH7gn83JbwDliEhFdR/pages/uGJTbZiG7LcbP0Bqm0Ie)
* [6.9.x Interface Specification](broken://spaces/lgQH7gn83JbwDliEhFdR/pages/Cxg7pixu4HyM0PThhOIN)
* [6.8.x Interface Specification](broken://spaces/lgQH7gn83JbwDliEhFdR/pages/bsNZemDPkx5gq9S3ATrT)
{% endif %}
**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
{% hint style="warning" %}
Pick one specification version as your source of truth.
Do not mix command rules across versions.
{% endhint %}
{% tabs %}
{% tab title="7.x Interface Specification" %}
{% stepper %}
{% step %}
### Understand the Product Model
Discover how VIPA fits your POS architecture and transaction model.
{% endcolumn %}
{% endcolumns %}
{% endif %}
{% if visitor.isSet === true %} Security FunctionalityAuthenticationPCI Requirements
{% endif %}
{% endstep %}
{% endstepper %}
{% endtab %}
{% endtabs %}
POS Integration Checklist
Use this checklist before certification or pilot rollout.
* [x] Confirm the target device family and VIPA version.
* [x] Choose one specification version as the primary reference.
* [x] Configure communication and required runtime settings.
* [x] Implement message framing and template handling.
* [x] Build the transaction flows your POS supports.
* [x] Add only the command groups you need.
* [x] Validate error handling and unsolicited message behavior.
* [x] Apply security, authentication, and PCI requirements.
* [x] Test contact, contactless, fallback, and cancellation flows.
* [x] Keep the appendices available during debugging.
---
# 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/vipa/vipa-getting-started.md?ask=&goal=
```
`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.