---
title: "EPI Update"
method: POST
path: "/api/valor/update-epi"
---

# EPI Update

`POST /api/valor/update-epi`

## Headers

- `Authorization` string, required
- `isv-secret-key` string

## Request body

- object
  - `newUserId` string, required — Merchant User ID (Max length of 11 chars)
  - `mp_id` string, required
  - `epiData` object[]
    - `id` string, required
    - `epi` string, required — EPI is an end point identifier, Identify the device on valor infrastructure, it's a 10 digit number starts with 2
    - `device` string — <p>The model description of the device to be boarded for that merchant. Have to pass the 'Device ID'</p> <table class="valor_module_table"> <tr> <th>Device Name</th> <th>Device ID</th> </tr> <tr> <td>VL100</td> <td>130</td> </tr> <tr> <td>VL110</td> <td>145</td> </tr> <tr> <td>VL500</td> <td>136</td> </tr> <tr> <td>VP100</td> <td>207</td> </tr> <tr> <td>RCKT</td> <td>274</td> </tr> <tr> <td>Virtual Terminal</td> <td>139</td> </tr> <tr> <td>VP500</td> <td>235</td> </tr> <tr> <td>VL100 Pro</td> <td>540</td> </tr> <tr> <td>VL550</td> <td>533</td> </tr> <tr> <td>VP550</td> <td>412</td> </tr> <tr> <td>VP550E</td> <td>524</td> </tr> <tr> <td>VP800</td> <td>527</td> </tr> </table>
    - `deviceType` string — <p>The type description of the device / terminal Possible Options.</p> <table class="valor_module_table"> <tr> <th>Device Name</th> <th>Device Type</th> </tr> <tr> <td>VL100, VP100, VL100 Pro</td> <td>Desktop POS</td> </tr> <tr> <td>VL500, VP500, VP550, VP550E, VP800</td> <td>Smart POS</td> </tr> <tr> <td>VL110</td> <td>Handheld POS</td> </tr> <tr> <td>RCKT</td> <td>DONGLE</td> </tr> <tr> <td>Virtual Terminal</td> <td>Soft POS</td> </tr> <tr> <td>VL550</td> <td>Portable</td> </tr></table>
    - `processor` string, required — Update the processor params 1 or 2 (TSYS : 1 and FD : 2)
    - `epiLabel` string
    - `features` object
      - `tip` object
        - `enabled` boolean, required
        - `value` integer[], required
      - `surcharge` object
        - `enabled` boolean, required
        - `value` string, required
      - `tax` object
        - `enabled` boolean, required
        - `value` string, required
    - `processorData` object[]
      - `mid` string, required — Merchant id related to the surcharge profile. If the epi is to be boarded on Traditional profile set it as "null"
      - `mid1` string, json, required — Merchant id related to the traditional profile. If the epi is to be boarded on surcharge Profile sets it as "null"
      - `vNumber` string, required — vNumber mapped to the particular device / terminal in surcharge profile. If the epi is to be boarded on Traditional profile set it as "null"
      - `vNumber1` string, json, required — vNumber mapped to the particular device / terminal in traditional profile. If the epi is to be boarded on a Surcharge profile, set it as "null"
      - `storeNo` string, required — Store number of the particular device / terminal in surcharge profile. If the epi is to be boarded on traditional Profile set it as "null"
      - `storeNo1` string, json, required — Store number of the particular device / terminal in traditional profile. If the epi is to be boarded on a Surcharge profile, set it as "null"
      - `termNo` string, required — Terminal number of the particular device / terminal in surcharge profile. If the epi is to be boarded on traditional Profile set it as "null"
      - `termNo1` string, json, required — Terminal number of the particular device / terminal in traditional profile. If the epi is to be boarded on a Surcharge profile, set it as "null"
      - `association` string, required — Association number for the particular device / terminal in surcharge profile. If the epi is to be boarded on a traditional Profile set it as "null"
      - `association1` string, json, required — Association number for the particular device / terminal in traditional profile. If the epi is to be boarded on a Surcharge profile, set it as "null"
      - `chain` string, required — Chain number for the particular device / terminal in surcharge profile. If the epi is to be boarded on a traditional Profile set it as "null"
      - `chain1` string, json, required — Chain number for the particular device / terminal in traditional profile. If the epi is to be boarded on a Surcharge profile, set it as "null"
      - `agent` string, required — Agent code number for the particular device / terminal in surcharge profile. If the epi is to be boarded on a traditional Profile set it as "null"
      - `agent1` string, json, required — Agent code number for the particular device / terminal in traditional profile. If the epi is to be boarded on a Surcharge profile, set it as "null"
      - `EbtNo` string, json, required — Ebt number for the particular device / terminal in surcharge profile. If the epi is to be boarded on a traditional Profile set it as "null"
      - `EbtNo1` string, json, required — Ebt number for the particular device / terminal in traditional profile. If the epi is to be boarded on a Surcharge profile, set it as "null"
      - `binnumber` string, required — Bin number for the particular device / terminal in surcharge profile. If the epi is to be boarded on a traditional Profile set it as "null"
      - `binnumber1` string, json, required — Bin number for the particular device / terminal in traditional profile. If the epi is to be boarded on a Surcharge profile, set it as "null"
      - `agentBank` string, required — Agent bank number for the particular device / terminal in surcharge profile. If the epi is to be boarded on a traditional Profile set it as "null"
      - `agentBank1` string, json, required — Agent bank number for the particular device / terminal in traditional profile. If the epi is to be boarded on a Surcharge profile, set it as "null"
      - `industry` string, required — The industry type on which the terminal / terminal in surcharge profile. If the epi is to be boarded on a traditional Profile set it as "null"
      - `industry1` string, json, required — The industry type on which the terminal / device to be boarded in traditional profile. If the epi is to be boarded on a surcharge Profile set it as "null"
      - `EBTcash` string, required — The EBT cash on which the terminal / device to be boarded in traditional profile. If the epi is to be boarded on a surcharge Profile set it as 0 or 1
      - `EBTcash1` integer, required — The EBT cash on which the terminal / device to be boarded in traditional profile. If the epi is to be boarded on a surcharge Profile set it as 0 or 1
      - `EBTfood` integer, required — The EBT food on which the terminal / device to be boarded in traditional profile. If the epi is to be boarded on a surcharge Profile set it as 0 or 1
      - `EBTfood1` integer, required — The EBT food on which the terminal / device to be boarded in traditional profile. If the epi is to be boarded on a surcharge Profile set it as 0 or 1
      - `surchargeIndicator` integer, required — The value '0' means % and 1 means dollar
      - `surchargePercentage` string, required — If the epi is to be boarded on a traditional Profile set it as "null". Surcharge indicator % means the value should be (3.000) and dollar (3.00)
      - `label` string, required — The storename on which the device/terminal created is mapped on this field
      - `programType` string, required — If program type set as "surcharge" or "cashdiscount".
    - `programType` integer, required
  - `associate_user_name` string — ISO user name (Alphanumeric length of 35 chars)

## Response `200`

200

- object

## Other responses

- `400` — 400

---

[API](https://skmtc.net/valorpaytech/apis/ecommerce-api.md) · [All operations](https://skmtc.net/valorpaytech/apis/ecommerce-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/valorpaytech/ecommerce-api/revisions/c6468b606325/schema)