Supported Transaction Types — Adyen
Generated page — source of truth is
capabilities/adyen.yaml. Do not edit this file directly.
Overview
Adyen supports card-present, token, and ecommerce transactions. Unlike MPGS, Adyen authenticates through a central API Key (set at merchant level) and routes payment methods through a POIID/merchant account pair (set at terminalConfig). This means the MPG array does not carry gateway credentials — it carries mapper IDs and STS channel references instead.
3DS is natively supported for ecommerce via Adyen's Drop-in SDK — no separate MPI integration is required.
Payment Methods
| PM Slot | Name | Description |
|---|---|---|
| PM0 | Bank Card | Card-present via physical terminal |
| PM1 | Token | Tokenised / card-on-file transactions |
| PM4 | Ecommerce | Browser-based via Adyen Drop-in hosted components |
Transaction Type Support Matrix
Source:
capabilities/adyen.yaml
| Code | Transaction Type | PM0 Card Present | PM1 Token | PM4 Ecommerce |
|---|---|---|---|---|
| 01 | Authorization | ✅ | ✅ | ✅ |
| 04 | Sale | ✅ | ✅ | ✅ |
| 07 | Void Auth | ✅ | ✅ | — |
| 10 | Refund | ✅ | ✅ | — |
| 05 | Tip Adjust | ❌ | ❌ | ❌ |
Notes: - Void Auth and Refund are not applicable to ecommerce (PM4) — ecom uses Adyen's webhook-driven capture/refund flow. - Tip Adjust is not supported on Adyen.
Capabilities
| Capability | Supported | Notes |
|---|---|---|
| Partial Auth | ✅ | Credit card only. Not available for debit. |
| Ecom 3DS | ✅ | Native in Adyen Drop-in. No separate MPI required. |
| DCC | ❌ | Not configured in current deployments. |
| Webhooks | ✅ | Ecom processing uses WEBHOOK_HMAC for event verification. |
| Tipping | ⚠️ UNCONFIRMED | TIPWORKFLOW_ENABLED flag exists on terminal. Confirm with Adyen integration owner. |
Which Transaction Types Apply to My SKU?
The active SKU bitmap determines which PM slots are provisioned. See the SKU page for the exact transaction profile: