Fiserv Nashville North
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 (equipment-based) | Not listed | Not listed |
If an ID is not listed, contact support@koard.com for the appropriate configuration.
Examples without a listed UAT ID are request templates. Replace YOUR_PROCESSOR_CONFIG_ID with an available configuration ID before submitting a request.
Use this format for a Nashville North configuration assigned to your merchant. See the Fiserv overview for common fields.
This page covers the equipment-based request format. For a configuration that requires the business name and merchant address without equipment fields, use the address-based Nashville North example.
Request fields
| Field | What to send |
|---|---|
account_id |
Merchant's Koard account ID |
processor_config_id |
Assigned Nashville North configuration ID |
mid |
Seven digits from the VAR sheet |
tid |
Seven digits from the VAR sheet |
mcc |
Four-digit merchant category code |
var_sheet.group_id |
Assigned Group ID |
var_sheet.industry |
Assigned industry value |
var_sheet.equipment |
CreditCallLTDGTWRC or CRDCallResellerRCSS, as assigned |
Supply the assigned twelve-digit var_sheet.settlement_mid. It is required and is separate from the seven-digit mid.
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
Request template: replace YOUR_PROCESSOR_CONFIG_ID with an available configuration ID before submitting. Use the VAR-sheet format assigned to your processor configuration. Replace all sample identifiers with your assigned values.
{
"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",
"industry": "retail_qsr_grocery",
"group_id": "10001",
"equipment": "CreditCallLTDGTWRC",
"settlement_mid": "123456789012"
}
}
Updates
Use PUT /v2/terminals/{terminal_id} and send only changed fields. Omitted address fields retain their existing values.

