Skip to main content

Why

NFC integrations fail easily because of subtle differences between card types, terminal hardware, and operating systems. Clear guidance reduces integration errors and support load.

What

Developers build four request types: identify, read, write, and session. Each has card-specific data structures. Adyen terminals run two operating systems that do not always have feature parity.

How

I structured the documentation around user intent instead of API shape. Using existing CMS components, I organized the page so developers could quickly find the right combination of card type, terminal type, and request type.

Result

The documentation reduced cognitive load in a complex integration flow with a high potential for implementation errors.
© 2026 Strahinja Milošević | Author of all-maker.com, a part of the tech writing blog webring