Across 2025 and into early 2026, four payment-and-commerce protocols shipped — Mastercard Agent Pay, Google AP2, OpenAI/Stripe ACP, Visa Trusted Agent Protocol — and the open agent-identity protocol underneath them, KYA-OS (formerly MCP-I, donated to DIF), graduated to a stewarded standard. Nexi sits in front of all of them as a payment processor whose merchant base meets agentic commerce demand before most banks do. The question is what Nexi ships when the first regulated forcing function lands. That forcing function is CCD2 — application date 20 November 2026 — and what it demands at the moment of consent is the one layer the four protocols and KYA-OS deliberately do not ship. PoPEye — the Point-Of-Purchase Evidence-Yielding Engine — is the answer for that piece. Anchored to Namirial as qualified trust-service provider; native to the Italian regulated identity stack (SPID, CIE) Nexi customers already integrate against; designed and operated by CINDR.LA with IDCanopy's bureau + identity moat underneath. Nexi brings the merchant channel. CINDR.LA / IDCanopy build and operate the regulated evidence layer.
CCD2 is the first deadline. PoPEye is the product that answers it. KYARA is the receipt authority it grows into. KYA-OS is the protocol layer that keeps it interoperable.
Individually, each of these is available. Bundled into one flow, delivered via a PSP channel with wallet-ready consent + MCP exposure — nobody has this today. It's the full compliance stack plus the agentic future in one product.
Directive (EU) 2023/2225 was adopted 18 October 2023, entered into force 19 November 2023. Application is 20 November 2026 (Art. 48). On that date Directive 2008/48/EC (CCD1) is repealed and the new regime is directly enforceable in national courts.
CCD1 carved out short-term, low-value, fee-free credit (CCD1 Art. 2(2)(f)) — the exact shape BNPL took. CCD2 closes the carve-out. Operative scope changes beyond the §02b summary: the lower-threshold carve-out is cumulative (below €200 is in scope unless also non-deferred, interest-free, and fee-free — a test almost no BNPL product passes); the "large online supplier" exemption (Art. 2(2)(h)) is materially narrowed (most merchants who relied on the CCD1 version no longer qualify); leasing with purchase option or acquisition obligation is in (Art. 2(2)(d)); P2P and crowdfunded consumer credit — not in CCD1 at all — are captured.
Article 18 is the centre of gravity. Three rules compound:
Three consequences flow from the text. A negative assessment means no credit — Art. 18(6) is a prohibition on granting credit the consumer cannot plausibly repay, with creditor liability attached ("we charged a higher APR instead" is not a defence). Automated decisions carry a human-review right layered on top of GDPR Art. 22 and the CJEU Schufa ruling (C-634/21, December 2023) — consumers must be told the decision logic and can demand human intervention. And proportionality cuts both ways: shallow checks are defensible at the shallow end and indefensible at the deeper end, with the burden of explaining why a given depth was adequate on the creditor.
Product implication: Article 18 does not specify a rail. It specifies an outcome. A documented policy mapping product, ticket, duration, and risk signal to required evidence depth is the defensible form — and the artifact a class-action plaintiff will demand in disclosure.
Creditworthiness consent under CCD2 is tighter than the GDPR baseline on four points (Art. 18, read with Arts. 10–12 and the Schufa ruling):
The artifact that proves compliance is the consent receipt: a signed, timestamped record binding specific consumer, specific creditor, specific transaction, evidence sources, and decision. CCD2 does not mandate a receipt format. It mandates an outcome that a receipt is the only clean way to deliver.
The 14-day consumer withdrawal right carries over from CCD1. Two CCD2 additions matter for merchants: material modification triggers a new SECCI, new consent, and — where it materially changes the consumer's financial obligation — a new creditworthiness assessment (top-ups, limit increases, and restructurings are procedurally new agreements, not amendments); and forbearance is not optional — before enforcement, the creditor must offer reasonable forbearance measures.
CCD2 requires "effective, proportionate, and dissuasive" penalties (Art. 44). National legislatures set the specific amounts. What ships uniformly across the EU:
Germany passed transposition on 17 April 2026 (amending BGB and KWG, introducing the Sales Finance Supervision Act; Bundesrat consent expected May 2026). France transposed by Ordonnance of 3 September 2025. Austria's draft is in consultation, Q2 2026 targeted. Italy, Spain, Netherlands, Belgium have drafts in flight.
The directive text sets the floor for pan-European operations. What varies is the implementation layer — registration, supervisory templates, penalty calibrations, exact Art. 18 verification wording — landing on a rolling calendar through Q3 2026, often weeks before application. Waiting for perfect clarity is not a strategy. Directive-level obligations are stable enough to build against today; national additions layer on as configuration.
CCD2 does not hit everybody the same way. Four distinct merchant shapes sit underneath one acquiring-channel checkout, each with a different compliance surface and a different pain profile. The Orchestration Layer handles them with one platform; the commercial pitch splits by buyer. What follows is what breaks, for whom, and why waiting is not an option.
The consumer-PM buyer. Pay-in-3, Pay-in-4, short-duration deferred payment — the product that built the €191B EU BNPL volume and is on track for €293B by 2030. The CCD1 short-term exemption that made this product lightweight is gone. Every transaction now needs a standardised SECCI before commitment (Directive (EU) 2023/2225, Arts. 10–12), a per-transaction creditworthiness assessment based on verified financial data (Art. 18), specific and unbundled consent, and a signed receipt proving all of it.
What breaks. Contract voiding and claw-back of interest, fees, and default charges on any non-compliant agreement — applied across the book, not per case. Collective actions under Directive (EU) 2020/1828 (German Verbandsklage, French action de groupe) against systematic consent-bundling or shallow Art. 18 checks. Supervisory exposure to BaFin, FMA, ACPR, Banca d'Italia. And — specific to BNPL — a liability-apportionment fight between merchant and BNPL provider that is ambiguous today and adversarial tomorrow: whichever side cannot produce an audit-trailed consent receipt carries the loss.
Why BNPL cannot wait. Volume spikes with seasonal checkout load (peaks above 1,000 TPS for tier-1 merchants). A compliance layer retrofitted mid-peak is a re-platforming project, not a patch. The 20 November 2026 date is fixed. The only question is whether the merchant enters peak with defensible infrastructure or with exposure.
The consumer-finance-PM buyer. Often a different internal owner at the same merchant as BNPL — different budget line, different compliance appetite, different SLA expectations. Same Orchestration Layer backend; different commercial face. The rule is load-bearing: one platform, two tracks — do not collapse into a single "consumer credit" offering.
What changes at this ticket band is the evidence floor. Bureau data alone is rarely enough to defend an Art. 18 assessment on a €3,000 24-month obligation — the directive's proportionality standard ("verified where necessary through independently verifiable documentation") pushes toward independently verifiable income and expense evidence. Policy-triggered AIS for higher-assurance flows is how that surface closes at checkout latency.
What breaks. The exposure profile shifts from volume-class (many small void-and-claw-back events) to ticket-class (fewer, larger, material voiding actions). "We used bureau data" is a weaker Art. 18 defence at €3,000 than at €150. Under Directive 2020/1828, a qualified consumer association can build a representative action on one or two systematically mis-assessed instalment products and apply the precedent across every similar agreement on the book.
Why instalment credit cannot wait. Higher-assurance evidence requires contracted AIS capacity, configured policy thresholds, and SECCI templates calibrated per national transposition — procurement-cycle decisions, not deployment tasks. Starting in Q3 2026 for 20 November 2026 is late.
The lessor buyer. CCD2 Art. 2(2)(d) is the key line: leases without acquisition obligation are out; consumer leases with a purchase option or acquisition obligation are in. Pure operational leasing is not routed through this platform unless local legal review puts it in scope.
The v1 posture is explicit and narrow: its own product mode, SECCI template, and pricing band; AIS-heavy evidence default (bureau-only not permitted at this scale under the v1 policy matrix). Available for design partners and first lessors — deliberately small to prove the product mode works before offering it broadly. Lessors have longer sales cycles and richer affordability-signal expectations than BNPL merchants; leasing carries its own commercial band because the evidence mix and unit economics differ.
What breaks. Same enforcement vectors as instalment credit, compounded by contract length — a voided lease is a multi-year revenue claw-back, not a ticket-level one. Mid-term payment changes and end-of-term purchase-option exercises each trigger the Art. 18 re-assessment rule. A lessor without re-assessment infrastructure at modification events carries cumulative exposure across the book.
Why leasing cannot wait. For design-partner lessors, scoping and evidence-calibration work starts now — leasing ships only if that validation runs parallel to the PSP PoC.
In scope under CCD2, but a different operational shape: continuous obligation rather than per-transaction credit, with re-assessment triggered by material change across the life of the facility. Compliance logic carries over — SECCI, Art. 18, specific consent, receipt — but the surface is a portfolio-review flow, not a checkout flow. Not a v1 commitment. The envelope and receipt schema are designed to absorb revolving as a future product mode without re-architecture.
The 20 November 2026 date does not discriminate by product shape. What discriminates is the exposure vector each shape creates: BNPL runs out of peak-season time fastest, instalment credit carries the largest per-case class-action risk, leasing compounds exposure over years, revolving is a later problem but not a different one. One platform, priced in four bands, handling the obligations each track actually faces — that is what it takes to walk into 20 November 2026 with defensible infrastructure across a merchant's full credit offering, not a checkout patch on one product while the rest of the book is exposed.
CCD2 creates compliance demand inside merchant portfolios. Every BNPL and consumer-credit merchant that runs through the Nexi channel will need a productized answer by 20 November 2026. They will not build it themselves. They will ask their acquirer.
The acquirer has one structural choice: wait for third-party vendors — Signicat, Sumsub, Trulioo — to productize the layer and own the merchant relationship, or fund the regulated evidence layer now and distribute it as a proprietary product. The first path cedes the relationship. The second path creates a durable channel position.
PoPEye is distributed through existing acquirer rails and relationships. CINDR.LA does not need to find merchants. Nexi selects which segment to activate first and controls the rollout pace. The build is funded once; the distribution is Nexi's channel. For the Italian market specifically, Namirial's Agentic Trust Services infrastructure and SPID/CIE integration make PoPEye uniquely positioned — the identity trust stack Nexi merchants already use becomes the evidence foundation.
Your merchant base will need this. Fund the layer now and own the distribution position before someone else productizes it for your customers.
A time-boxed engagement to establish mutual product fit, compliance fit, and architecture readiness before committing to a full build. CINDR.LA / IDCanopy deliver a structured scoping memo and a go / no-go recommendation for Tier 2. Italian market specifics — SPID/CIE identity chain, CRIF bureau routing, Namirial QTSP anchor, Banca d'Italia supervisory expectations — are part of the assessment scope.
Nexi funds the PoPEye implementation for one product mode and one launch market. CINDR.LA / IDCanopy deliver a working PoPEye instance integrated into the Nexi channel, anchored to Namirial QTSP and native to the Italian identity stack, ready for CCD2 enforcement on 20 November 2026.
White-label, co-branded, or embedded distribution through the Nexi acquirer channel. Commercial structure depends on exclusivity, markets, transaction volume, support burden, and IP arrangement. This is the durable channel position across Italy, DACH, Nordics, and Iberia.
Every capability CINDR.LA ships for CCD2 — signed consent, verified identity, bureau-fresh affordability — is exactly what agentic commerce needs when machine-initiated purchases go regulated. KYARA (Know Your Agent Receipt Authority) captures compliance at the moment of consent. KYA-OS (the DIF-stewarded open agent-identity protocol, formerly MCP-I) makes it interoperable across all four payment protocols. This is how CINDR.LA owns the next decade of compliance primitives, not just the 2026 deadline.
Legal entity. Registered in our operator registry. KYB-grade.
Operators pass IDCanopy KYB onboarding before issuing any agent. Operator DID + Agent Issuer Certificate minted. Registry resolution on every transaction. No registered operator → transaction rejected before SECCI renders.
Reproducible. Audit-traceable. Pinned per transaction.
Agent declaration at registration captures model family, version, capabilities, hosting, key custodian. Version written into every KYA receipt. Regulator traces a disputed CCD2 transaction back to the exact agent build that initiated it.
Verifiable Credential. Signed by consumer's wallet.
Consumer signs a mandate VC once per scope: merchant allowlist, MCC categories, per-transaction ceiling, rolling-period ceiling, allowed regimes, expiry. CCD2 forces requiresHumanConfirmation=true regardless of what the mandate says — policy engine overrides.
Enforced at the action point. Seven checks before any engine fires.
Signature valid · not revoked · not expired · scope match · period ceiling fresh · action assertion fresh · operator in good standing. Any fail → reject before SECCI even renders. Reason returned to merchant.
ccd2_credit.requiresHumanConfirmation=false for CCD2.Mapping Nexi's current exposure to the four protocols (AP2, Agent Pay, TAP, ACP) and KYA-OS. Where Nexi sits in the landscape today — and what is missing for a regulated-receipt-layer-aware acquirer position across Italy, DACH, Nordics, and Iberia.
Structural gap at the consent-receipt-and-affordability layer for Nexi's Italian and EU merchant base. Article 18 exposure profile. SPID/CIE/Namirial chain as the structural advantage for Italian-first deployment — Banca d'Italia transposition expected Q2–Q3 2026; directive applies 20 November regardless.
PoPEye as the CCD2-compliance piece Nexi distributes to its merchant base. Engagement options: white-label, OEM, or co-branded channel distribution. Operator anchors to the Namirial QTSP trust chain; Nexi brings the acquiring channel and merchant relationships.
CCD2 is the first wedge; PSD3/PSR, FIDA, and verticalized regulated transaction surfaces (insurance distribution, investment suitability) extend the same architecture.