> 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/support-us/verifone-hq/vhq-parameter-management/configuring-parameter-templates/multi-merchant-and-card-range-parameter-management.md).
# Multi-merchant and card range parameter management
Configure multi-merchant and card range parameter management for VHQ managed devices, including importing instances via XML and editing merchants directly in VHQ.
{% hint style="info" %}
**Use this when** you need to configure or edit parameters for multiple merchants sharing a single terminal, or manage card range instances.
{% endhint %}
VHQ supports **Multi-Merchant** functionality and editing of **Card Range** parameters for all VHQ-managed devices. Multiple merchants can share a single terminal — the device owner creates merchant IDs, and each merchant logs in with their own credentials to perform transactions, which are recorded in the system. VHQ supports this by reusing the same set of parameters and creating multiple instances with different values.
With standard functionality, VHQ manages parameters at the container level, mapped to a single instance. Multi-merchant functionality extends this to multi-instance and multi-level parameter handling:
* **Multi-Level**: Multiple child levels under a parent — a hierarchical parent-child relationship.
* **Multi-Instance**: A set of parameters repeated at the same level with different values.
Application developers build a parameter definition file (.vpdx) defining all parameters and their attributes, plus multiple form files (.vpfx) for editing them.
{% hint style="info" %}
**Example**: A hair salon terminal serves up to 20 different merchants — each stylist/contractor logs into the same terminal with their own credentials to perform transactions.
{% endhint %}
Multi-merchant terminals typically download parameters once per business day (or more often); editing a parameter or adding an instance triggers a download.
{% hint style="info" %}
Parameter editing and viewing is allowed only if the application is configured with, or has had uploaded, a form file.
{% endhint %}
## Import instances via XML
{% stepper %}
{% step %}
### Open Add Devices
Go to **Device Management** > **Add Devices**.
{% endstep %}
{% step %}
### Choose file import
Select **Add Device via File Import**.
{% endstep %}
{% step %}
### Import the file
Browse for the XML file and click **Import**.
{% endstep %}
{% endstepper %}
XML files for adding or modifying instances or merchants are typically prepared by customer administrators, regional support representatives, or VHQ support personnel.
## Set up multi-instance support in VHQ
Before editing parameters, upload the .vpdx and .vpfx files.
{% stepper %}
{% step %}
### Check the MultiInstance attribute
Confirm the container-level **MultiInstance** attribute is set to *Yes* in the .vpdx file.
{% endstep %}
{% step %}
### Upload the vpfx file(s)
You can upload multiple levels of .vpfx file to the application assigned to the device. Check the parent ID attribute is present when uploading. Within the vpfx: *AllowAdd*, *AllowDelete*, and *AllowEdit* set to **True** allow the user to create, delete, and edit instances; *AllowSequence* set to **True** allows setting the ordering for merchants (on deletion, the preceding merchant takes the sequence order).
{% endstep %}
{% step %}
### Assign the application
Once the vpdx and vpfx files are uploaded, assign the application to the device.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
If *AllowSequence* is **True** in both VPDX and VPFX, the user can change the instance sequence; if **False**, they cannot.
{% endhint %}
## Edit merchant parameters
{% stepper %}
{% step %}
### Find the device
Select a device or search for one.
{% endstep %}
{% step %}
### Open the Parameter tab
On *Device Profile*, click **Device Details** > **Parameter**.
{% endstep %}
{% step %}
### Click the edit icon
{% endstep %}
{% step %}
### Manage merchants
On the *Edit Parameter for Application* window, click the merchant node to view configured merchants. You can add a new merchant, edit merchant-specific parameters, or delete an existing merchant from the *List* tab. Merchants are identified by ID and name; the *Details* tab shows full details and lets you edit them.
{% endstep %}
{% endstepper %}
## Add, edit, or delete a merchant
**Adding a merchant**
1. On the *Edit Parameter for Application* window, click the edit icon.
2. Enter the merchant ID, name, address, and other details (or restore defaults).
3. Click **Add**. The new instance is added.
**Editing a merchant**
1. Select the merchant and click the pencil icon.
2. On the *Details* tab, edit the value and click **Save**.
**Deleting a merchant**
1. Select the merchant and click the remove icon.
2. Use the up/down icons to reorder the merchant sequence. You can manage multiple levels on the *Edit Parameter for Application* screen.
On creating or modifying a merchant, parameters are downloaded to the terminal once the job is scheduled. The output parameter file format is generated as shown below:
Keywords
Also called: multi-merchant, card range parameters. Search terms: merchant ID, multi-instance, multi-level.
---
# 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/support-us/verifone-hq/vhq-parameter-management/configuring-parameter-templates/multi-merchant-and-card-range-parameter-management.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.
