The open ISO 20022 protocols that connect terminals, sales systems and acquirers, how they differ from EMV certification, and what to check before a project depends on them.
nexo standards define open ISO 20022 protocols for card payment acceptance: terminal to acquirer, terminal to terminal management system, and sales system to terminal. They sit beside EMV, not in place of it. If your acquirer or market requires nexo, treat it as its own workstream, with its own specifications, test tools and owner, and plan it early.
nexo standards is a not-for-profit association that develops open payment acceptance specifications based on ISO 20022. It formed in 2014 from the merger of EPASOrg, the OSCar consortium and the CIR SEPA-FAST technical working group. Members include acceptors, processors, schemes, PSPs and vendors, and the specifications are free to download after creating a free account.
The goal is interoperability: one terminal application that works with multiple acquirers, and one POS system that works with multiple terminals.
| Protocol | Connects | What it covers |
|---|---|---|
| nexo Acquirer protocol | Acceptor and acquirer | ISO 20022 card messages for authorization, completion, cancellation, reconciliation, batch transfer and diagnostics. Real-time or batch, direct or through a PSP. |
| nexo TMS protocol | Terminal and terminal management system | Terminal management, such as parameter download. |
| nexo Retailer protocol (Sale to POI) | Retail sales system and the terminal's card application | Version 3.1 is widely deployed over XML on HTTP or TCP. Later versions use the ISO 20022 data dictionary. |
| nexo security specification | Across the Acquirer, TMS and Retailer protocols | Mechanisms that protect the messages. |
nexo FAST is a common payment application specification for the point of interaction (POI). The nexo implementation specification (NIS) packages the protocols together. NIS v4.0 pairs Acquirer protocol v6.0 and TMS protocol v6.0, with Retailer protocol v3.1 as optional.
A compliant FAST terminal must support:
nexo does not replace EMV. Chip, contactless and card brand terminal behavior still follows EMV and brand rules, and acquirers that require EMV Level 3 still require it. Treat these as two parallel workstreams, each with its own evidence, test tools and often its own owner.
| Question | EMV and brand certification | nexo |
|---|---|---|
| What it governs | Chip, contactless and card brand terminal behavior | Terminal to acquirer, terminal management and sales system communication |
| What you prove | The application passes acquirer and brand card-flow certification | The application correctly speaks the required nexo protocols, validated by an accredited tool or body where required |
| Where it comes up | Every acquirer EMV Level 3 project | Acquirer specs, RFPs and European market plans |
For the EMV side, see our guide to the EMV Level 3 certification process and our EMV Level 3 certification in Europe page.
If the acquirer and the market never mention nexo, you may never need it. If they do, plan early.
nexo has announced an accredited test tool for validating acquirer hosts against Acquirer protocol v6.0, followed by a POI test tool, and test labs have been authorized to evaluate implementations against Acquirer protocol v6.0. Tools and accrediting bodies change, so confirm the current process with the acquirer and the lab before scheduling.
Recent work includes instant payments at the POI and payment encryption updates, with post-quantum cryptography on the roadmap. nexo also signed an agreement with the European Central Bank related to digital euro payments, so European builders may see these changes sooner than expected.
Paying.co is a payment engineering firm specializing in EMV Level 3 certification, payment applications and acquirer integration. Tell us the acquirer, the terminal and the market, and we will help you confirm the specification versions and plan the evidence before testing.
Talk to us Book a meeting with a founder