Fiserv Nashville North (Global)

Nashville North (Global) authorizes on Fiserv's Nashville platform and settles on North.

Koard runs the batch automatically every day at 02:00 Pacific. A different cutoff or submission time is not supported yet. See Fiserv Automatic Batches and Settlement.

Processor configurations

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

Configuration	UAT `processor_config_id`	Production `processor_config_id`
Fiserv Nashville North (Global)	`18083156-5ce9-4147-bf7c-3f792d010dc7`	`212ef266-1f7d-4dd3-a089-ee608473877c`

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

Use this format for the Nashville North (Global) configuration assigned to your merchant. See the Fiserv overview for common fields.

Request fields

Field	What to send
`account_id`	Merchant's Koard account ID
`processor_config_id`	Nashville North (Global) configuration ID for your environment
`name`	Merchant business name
`mid`	Seven digits from the VAR sheet
`tid`	Assigned terminal identifier from the VAR sheet
`mcc`	Four-digit merchant category code
`var_sheet.merchant_number`	Twelve digits from the VAR sheet
`var_sheet.settlement_mid`	Optional. Twelve-digit settlement MID from the VAR sheet

Both the seven-digit mid and the twelve-digit var_sheet.merchant_number are required. Send them as separate strings; one cannot replace the other. Preserve leading zeros.

var_sheet.settlement_mid is optional. When your VAR sheet lists a settlement MID, send it in addition to var_sheet.merchant_number, not in place of it.

Supply the merchant street address, city, state and ZIP in var_sheet. Country defaults to USA; US, 840 and null also become USA.

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 Nashville North (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"
  }
}

Updates

Use PUT /v2/terminals/{terminal_id} and send only changed fields. Omitted address fields retain their existing values.

Nashville

Omaha