Fiserv terminal boarding
Board a Fiserv terminal with POST /v2/terminals. Use the processor_config_id assigned to your merchant, listed by GET /v1/processor-configs, and the identifiers from the merchant's VAR sheet.
Configurations
Koard supports four Fiserv configurations. The merchant's VAR sheet names the one it is on.
| Configuration | Boarding guide |
|---|---|
| Nashville | Nashville |
| Nashville North (Global) | Nashville North (Global) |
| Buypass | Contact support@koard.com for the request format. |
| Omaha | Omaha |
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 (Global), 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.
Updates
Use PUT /v2/terminals/{terminal_id} with only the fields you want to change. Omitted address fields retain their existing values.
Batches and settlement
Koard runs settlement for every Fiserv configuration. You do not open or close a batch with Fiserv yourself.
On Nashville North (Global), the batch runs automatically every day at 02:00 Pacific. A different cutoff or submission time is not supported yet. See Fiserv Automatic Batches and Settlement.
