Fiserv terminal boarding

Processor configurations

Boarding requires a processor_config_id available to your account in the same environment. List available configurations before choosing an ID.

For production access to Fiserv RapidConnect, contact support@koard.com.

If an ID is not listed, contact support@koard.com for the appropriate configuration.

Examples with listed IDs use UAT. For production, use the production API URL, API key and configuration ID.

Examples without a listed UAT ID are request templates. Replace YOUR_PROCESSOR_CONFIG_ID with an available configuration ID before submitting a request.

Select the Fiserv configuration assigned to your merchant from GET /v1/processor-configs. Create the terminal with POST /v2/terminals using account_id, processor_config_id, mid, tid, and mcc.

Fiserv configurations can require different VAR-sheet fields. Use the request format assigned to your configuration and the identifiers from your merchant's VAR sheet.

Use the examples below for RapidConnect and address-based Nashville configurations. The Nashville Classic, Nashville North, Cardnet North, and Omaha pages include their own request examples. If your assigned configuration's request format is unclear, confirm it with Koard before submitting the request.

Merchant address

Supply merchant_street_address, merchant_city, merchant_state, and merchant_postal_code in var_sheet. merchant_street_address2 is optional.

Country defaults to USA. US, 840, and null also become USA. See shared address rules.

Assigned identifiers

Use the MID, TID, Group ID and Datawire ID assigned together for the merchant. Where your configuration uses Datawire, supplying did enables it. Setting datawire_enabled to true without a did requests a new Datawire ID.

For Nashville North's equipment-based request, supply the twelve-digit settlement_mid separately from the seven-digit mid.

For Nashville Global and Nashville North with merchant address, both the seven-digit mid and twelve-digit var_sheet.merchant_number are required. Send them as separate strings; one cannot replace the other. Keep the assigned tid unchanged, including leading zeros. Missing or malformed identifiers are rejected before boarding.

Request examples

Send these request bodies to POST /v2/terminals with your Koard API key in the X-Koard-apikey header.

Processor configuration IDs are listed by environment above. Merchant account IDs, credentials and merchant details below are fictional placeholders; replace them with your merchant's values. Preserve leading zeros.

Fiserv RapidConnect

UAT example. Use the merchant, terminal, group and Datawire identifiers assigned together for this configuration.

{
  "account_id": "00000000-0000-4000-8000-000000000001",
  "processor_config_id": "6fb2f3e1-cd5c-4206-8edc-ff878cff572c",
  "name": "Example Coffee",
  "mid": "YOUR_ASSIGNED_MID",
  "tid": "00000001",
  "mcc": "5812",
  "var_sheet": {
    "merchant_street_address": "123 Main Street",
    "merchant_street_address2": "Suite 200",
    "merchant_city": "New York",
    "merchant_state": "NY",
    "merchant_postal_code": "10016",
    "country_code": "USA",
    "industry": "retail_qsr_grocery",
    "group_id": "40001",
    "did": "YOUR_ASSIGNED_DID",
    "datawire_enabled": true
  }
}

Nashville Global

UAT example. Use this when your assigned configuration requires a business name and merchant address. Send both the seven-digit mid and twelve-digit var_sheet.merchant_number, plus name, tid, mcc and the address fields shown.

{
  "account_id": "00000000-0000-4000-8000-000000000001",
  "processor_config_id": "18083156-5ce9-4147-bf7c-3f792d010dc7",
  "name": "Example Coffee",
  "mid": "1234567",
  "tid": "7654321",
  "mcc": "5812",
  "var_sheet": {
    "merchant_street_address": "123 Main Street",
    "merchant_street_address2": "Suite 200",
    "merchant_city": "New York",
    "merchant_state": "NY",
    "merchant_postal_code": "10016",
    "country_code": "USA",
    "merchant_number": "000123456789"
  }
}

Nashville North with merchant address

Request template: replace YOUR_PROCESSOR_CONFIG_ID with an available configuration ID before submitting. Use this when your assigned configuration requires a business name and merchant address. Send both the seven-digit mid and twelve-digit var_sheet.merchant_number, plus name, tid, mcc and the address fields shown.

{
  "account_id": "00000000-0000-4000-8000-000000000001",
  "processor_config_id": "YOUR_PROCESSOR_CONFIG_ID",
  "name": "Example Coffee",
  "mid": "1234567",
  "tid": "7654321",
  "mcc": "5812",
  "var_sheet": {
    "merchant_street_address": "123 Main Street",
    "merchant_street_address2": "Suite 200",
    "merchant_city": "New York",
    "merchant_state": "NY",
    "merchant_postal_code": "10016",
    "country_code": "USA",
    "merchant_number": "000123456789"
  }
}

Updates

Use PUT /v2/terminals/{terminal_id} with only the fields you want to change. Omitted address fields retain their existing values.