Get merchant varsheet by terminal ID

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Get Merchant Varsheet by Terminal ID

Retrieves the complete Value-Added Reseller (VAR) sheet for a specific terminal belonging to a merchant. The VAR sheet contains all parameters required to program a payment terminal, including acquirer BIN, merchant and store numbers, authorization and settlement phone numbers, debit/EBT configuration, and SSL/host-capture fields.

Endpoint

GET /api/export/Varsheet

Authentication

Basic HTTP Authentication required.
Encode username:password in Base64 and pass in the Authorization header:

Authorization: Basic {base64(username:password)}

When to use

Use this endpoint when provisioning or reprogramming a payment terminal. Call GET /api/export/Terminals first to obtain the internalId for the specific terminal, then pass both the merchant id and the terminal internalId to this endpoint. The returned parameters are passed directly to terminal configuration software or a VAR to program the device.

Query Parameters

ParameterTypeRequiredDescription
idintegerYesThe internal merchant profile ID
internalIdintegerYesThe internal terminal ID (from GET /api/export/Terminals response)

Response

200 OK

Envelope fields:

FieldTypeDescription
requestIdintegerUnique identifier for this API request
successbooleanWhether the request was successful
errorstringError message if success is false
validationErrorsarrayField-level validation errors
dataobjectVarsheetInformation object

data.merchantInformation

FieldTypeDescription
namestringMerchant DBA name
addressstringStreet address
citystringCity
statestringState code
zipstringZIP code
phonestringMerchant phone number

data.vitalParameters

FieldTypeDescription
acquirerBinstringAcquirer BIN used for network routing
merchantNumberstringMerchant account number
vNumberstringV-number assigned to the terminal
storeNumberstringStore number within the merchant hierarchy
terminalNumberstringTerminal number within the store
merchantLocationNumberstringLocation identifier for multi-site merchants
merchantCategoryCodestringMCC (Merchant Category Code)
agentNumberstringISO/agent number
chainNumberstringChain number for multi-location groups
merchantZipCodestringMerchant ZIP code (used in AVS)
dbaNamestringDoing Business As name programmed into the terminal
merchantCitystringMerchant city
merchantStatestringMerchant state
timeZoneCodestringTime zone code for transaction timestamping
timeZoneDifferentialstringOffset from UTC

data.vitalPhoneNumbers (read-only)

FieldTypeDescription
authorizationstringAuthorization phone number
settlementstringSettlement phone number
voiceAuthorizationstringVoice authorization fallback number

data.debitEbt

FieldTypeDescription
sharingGroupstringDebit network sharing group code
merchantAbaNumberstringABA number for debit/EBT routing
settleAgentNumberstringSettlement agent number (read-only)
reimbursementAttributestringReimbursement attribute code (read-only)
industrystringIndustry code for EBT (read-only)
fcsIdstringFCS identifier for EBT transactions

data.authentication

FieldTypeDescription
authenticationCodestringAuthentication code for terminal validation

data.sslFields (read-only)

FieldTypeDescription
portNumberstringSSL port for host communication
urlstringSSL host URL

data.hostCaptureFields

FieldTypeDescription
hcPosIDstringHost-capture POS ID
{
  "requestId": 304812,
  "success": true,
  "error": null,
  "validationErrors": [],
  "data": {
    "merchantInformation": {
      "name": "Acme Retail Store",
      "address": "100 Commerce Blvd",
      "city": "Miami",
      "state": "FL",
      "zip": "33101",
      "phone": "3055557890"
    },
    "vitalParameters": {
      "acquirerBin": "999001",
      "merchantNumber": "918000000001234",
      "vNumber": "79416045",
      "storeNumber": "0001",
      "terminalNumber": "0001",
      "merchantLocationNumber": "00000001",
      "merchantCategoryCode": "5999",
      "agentNumber": "000100",
      "chainNumber": "000000",
      "merchantZipCode": "33101",
      "dbaName": "ACME RETAIL",
      "merchantCity": "MIAMI",
      "merchantState": "FL",
      "timeZoneCode": "705",
      "timeZoneDifferential": "-5"
    },
    "vitalPhoneNumbers": {
      "authorization": "8004STRIPE",
      "settlement": "8004SETTLE",
      "voiceAuthorization": "8004VAUTH0"
    },
    "debitEbt": {
      "sharingGroup": "NYCE",
      "merchantAbaNumber": "021000021",
      "settleAgentNumber": "000001",
      "reimbursementAttribute": "0",
      "industry": "R",
      "fcsId": "1234567"
    },
    "authentication": {
      "authenticationCode": "A1B2C3D4"
    },
    "sslFields": {
      "portNumber": "443",
      "url": "txn.netevia.com"
    },
    "hostCaptureFields": {
      "hcPosID": "00000001"
    }
  }
}

Error Codes

CodeWhen it happens
400Missing or malformed id or internalId parameter
401Invalid or missing Basic Auth credentials
403User does not have permission for this operation
404No merchant or terminal found for the provided IDs
500Internal server error

Common Mistakes

  • Omitting the internalId parameter — both id and internalId are required.
  • Using the public merchant ID string or terminal name instead of the internal integer IDs.
  • Requesting the VAR sheet for a terminal with status: Closed — closed terminals may return empty or stale programming data.
  • Attempting to write or modify VAR sheet data via this endpoint — it is read-only.
  • Not calling GET /api/export/Terminals first to obtain valid internalId values.

Related Endpoints

  • GET /api/export/Terminals — list all terminals for a merchant to obtain internalId
  • GET /api/export/MerchantProfile — retrieve full merchant data including equipment section
  • GET /api/export/GetAvailableStatusesList — decode merchant status codes

Example

curl -X GET "https://hq.staging.netevia.dev/api/export/Varsheet?id=71103&internalId=10045" \
  -H "Authorization: Basic $(echo -n 'username:password' | base64)"
Query Params
int32
required
int32
required
Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Response

Language
Credentials
Basic
base64
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
text/json