Terminal Configuration — Adyen

Level 200 — Configuration Applies To: Gateway=Adyen | Integration=SPF, MS | Variants=ALL

Prerequisites: Merchant Configuration

What Is a Terminal?

A terminal represents a point-of-interaction — a physical POS device, a virtual terminal, or a software session. Every merchant needs at least one terminal before MPG entries or terminalConfig can be provisioned.

For Adyen, the terminal record also carries feature flags (tipping, surcharge, suppress alternate payment methods) and links to the terminalConfig where the Adyen Merchant Account and POIID are set.

Key Concept: POIID and Merchant Account

Unlike MPGS (which puts gateway credentials in the MPG entries), Adyen puts its per-terminal credentials in terminalConfig:

ADYEN_MERCHANT_ACCOUNT — the Adyen merchant account name (e.g. MyHotelAU). This is the Adyen-side merchant identifier, distinct from the MGMT merchant record.
ADYEN_POIID — the Point of Interaction ID. Format: <model>-<serial> for physical terminals, or a logical ID for virtual terminals.

These two fields are what Adyen uses to route and authenticate each transaction at the terminal level.

1. Terminal

Field	MGMT Field	Required	Notes
`TERMINAL_ID`	`terId`	Mandatory	Terminal identifier. Also written to `workstationId`. Supply via secrets manager.
`INTEGRATE_FLAG`	`integrateFlag`	Conditional	⚠️ Confirm correct value with integration owner.
`TIPWORKFLOW_ENABLED`	`tipWorkflowEnabled`	Conditional	Set `true` to enable tipping workflow.
`RENDERED`	`rendered`	Conditional	Controls receipt rendering mode.
`SURCHARGE_ENABLED`	`surchargeEnabled`	Conditional	Enables surcharge calculation.
`ALLOWPARTIAL`	`allowPartial`	Conditional	Allow partial payment amounts.
`SUPPRESS_ALT_PM`	`suppressAltPm`	Conditional	Suppress alternate payment method display.

2. Terminal Configuration (terminalConfig)

ADYEN_MERCHANT_ACCOUNT and ADYEN_POIID are secrets. Supply via secrets manager.

Field	MGMT Field	Required	Sample	Notes
`ADYEN_MERCHANT_ACCOUNT`	`channelMerchantId`	Mandatory	`<secret>`	Adyen merchant account name. Routes the transaction on Adyen's side.
`ADYEN_POIID`	`channelTerminalId`	Mandatory	`<secret>`	Point of Interaction ID. Physical: `<model>-<serial>`. Virtual: logical ID.
`HOST_TIMEOUT`	`extData1`	Conditional	`170000`	Host communication timeout in milliseconds. Default 170 s.
`UNSUPPORTED_CARDTYPE_MAPPER`	`extData2`	Conditional	—	Maps unsupported card types to a fallback flow.
`CARD_TOKEN_TYPE`	`extData3`	Conditional	—	Card tokenisation type (e.g. `NETWORK`, `CUSTOMER`).
`ADYEN_STORE`	`extData4`	Optional	—	Adyen store identifier for multi-store merchants.
`ADYEN_RECURRING_MODEL_OVERRIDE`	`extData5`	Optional	—	⚠️ Override for Adyen recurring model. Confirm before setting.

Adyen vs MPGS — Credential Location Comparison

Credential	MPGS location	Adyen location
Gateway host URL	MPG entry `extData1`	Merchant `extData3` (`ADYEN_HOST_MERCHANT_DNS`)
API key / password	MPG entry `extData2/3`	Merchant `extData1` (`ADYEN_API_KEY`)
Merchant account	Terminal config `channelMerchantId`	Terminal config `channelMerchantId` ✓ same field
Terminal ID	Terminal config `channelTerminalId`	Terminal config `channelTerminalId` (= POIID)

The MPG entries for Adyen carry mapper IDs (not credentials) — see MPG Configuration.

Open Items

#	Item
OI-INTEGRATE	`INTEGRATE_FLAG` correct value not documented — confirm with Adyen integration owner
OI-RECURRING	`ADYEN_RECURRING_MODEL_OVERRIDE` usage not confirmed