Six pillars. One deployable stack. The registered EU Digital Identity Wallet verifier, telephony and call-traceability platform for EU wholesale telecoms.

For wholesale · not for end users

Built for the buyers who sit between the platform and the retail subscriber.

CTIC is a wholesale-shaped, six-pillar XaaS deployment. It targets organisations that resell connectivity, identity and voice services to downstream partners — MVNOs, MVNEs, eSIM brands and national carriers included — and are directly exposed to the 2027 EU Digital Identity Wallet acceptance obligations at the moment a subscriber is onboarded, activated or ported. CTIC is a self-hosted, six-pillar XaaS platform for wholesale telecoms.

The four 2027 touchpoints where CTIC replaces manual KYC and paper-based flows: SIM registration, eSIM activation, number portability and B2B account onboarding. Each is a regulated moment. Each currently costs the wholesale operator hours of manual verification per subscriber, per port, per new corporate account. CTIC turns each into a wallet-presentation flow that completes in seconds, with a signed, tamper-evident verification receipt kept in the operator's own filesystem.

The first-mover position

Among the very first EU-shipped EU Digital Identity Wallet verifiers delivered as-a-Service.

CTIC is production-ready and among the first EU-shipped EUDI Wallet verifiers delivered as-a-Service. It ships six market-first pillars in one integrated binary: an EU Digital Identity Wallet verifier that speaks the OpenID for Verifiable Presentations profile and accepts SD-JWT Verifiable Credentials over the high-assurance interoperability profile (HAIP), browser-native SIP-over-WebSocket telephony, a database-free self-hostable runtime, eIDAS QES-sealed signatures, interoperable eForms and EN 16931-aligned XInvoice / XRechnung / ZUGFeRD e-invoicing — delivered as installable software the operator runs itself.

The 2027 acceptance mandate is not a suggestion. It is a hard obligation on any organisation whose customer-onboarding flow triggers the eIDAS 2.0 acceptance requirement. Wholesale telecoms operators sit at every one of those triggers. The organisations that deploy a wallet verifier before the deadline capture two things: procurement leverage against retail partners still scrambling for a verifier of their own, and a regulatory-alignment story that lands with national regulators, ministries and enterprise procurement.

Shipped in the last 90 days · production-live · last update 2026-08-10

The verifier is now a registered, EU-listed EU Digital Identity Wallet platform.

The six pillars anchor CTIC. Since the wholesale rollout began, the platform has extended the identity pillar into a full self-hosted EU Digital Identity Wallet stack — registered Wallet Relying Party on the EU Reference Registry, EJBCA-issued wrp.p12 JAR-signing certificate, JAdES-B intended-use attestation, verifier + issuer + hosted holder PWA, LOTL-anchored trust chain, OpenID Federation 1.0, W3C Bitstring Status List, W3C VCDM 2.0 (JOSE envelope), four DID methods, Wallet Instance Attestation, cross-tenant trust federation, EU-Ref-CA autofetch and per-check attestation reports — and hardened the telephony and communications pillars around it. Everything below is deployed and reachable on Aloaha Limited's production tenants today (phone.codeb.io, phone.aloaha.com).

Fifteen chips visualise ninety days of shipments — the newest row (mDoc / ISO 18013-5 primitives, OID4VP QR camera scanner, OID4VCI authorization_code + PAR + PKCE) landed on 2026-07-20; between then and 2026-08-10 the platform also gained an EU-Registry entry, a registry-issued wrp.p12, LOTL trust-chain enforcement, the CSC v2 remote signature service and the Cross-tenant Trust Federation shortcut listed below. Amber chips extend the EU Digital Identity Wallet pillar; blue chips harden the telephony and communications pillars. Diagram viewBox 800x264 scales to 380px mobile.

• Wallet Attestation endpoint (HAIP interoperability profile). Wallet-instance attestations issued and validated on the operator's own tenant, so downstream relying parties see a full chain of trust from wallet instance through verifier to their own trust store.
• OpenID4VCI issuer. The same platform that verifies presentations now issues Verifiable Credentials over the pre-authorized_code flow, with a per-tenant admin UI for defining credential types, key rotation and revocation.
• Hosted holder wallet PWA. A self-hostable, installable Progressive Web App that lets operators offer their own subscribers a wallet without waiting for national scheme apps. Zero-knowledge backup between devices via the operator's own OIDC store.
• OpenID Federation 1.0 discovery. Wallets and other relying parties can discover the operator's trust anchor at /.well-known/openid-federation, ready for the incoming federation-based EU trust model.
• List-of-Trusted-Lists poller. Continuously refreshes the EU trust list and validates x5c chains presented at the verifier, so no manual trust-store rotation is required.
• Per-tenant EU Wallet audit log. Every wallet presentation is written to a per-tenant, greppable audit trail; the tenant's CISO and DPO have full auditability over identity flows without leaving the operator's own filesystem.
• Public verifier conformance test. A third party can point their wallet at the operator's verifier and inspect the presentation exchange end-to-end — useful for RFP responses, procurement diligence and downstream retail-partner reassurance.
• Per-trunk SDES SRTP. RFC 4568 SDES SRTP is available per-trunk across every bridge in the SBC, so signalling and media stay encrypted regardless of the interconnect partner's posture.
• ACL v3 with hot-reload and auto-blacklist. Signalling scanners at well-known OVH and other hosting ranges are auto-blocked on startup; per-tenant allow-lists reload without a service restart.
• Multi-tenant chat platform with drop-in widget. Direct messages, groups and file transfers between tenant users, plus a per-tenant visitor widget that lets a wholesale operator embed one line of script on their own retail-portal.
• Stereo per-trunk call recording and transcription. Per-trunk and per-virtual-number toggle. Recordings are stereo PCM16 WAV; transcripts flow into the per-tenant audit trail with sharable links the operator controls.
• Growing mDoc / ISO 18013-5 pipeline. CBOR, COSE_Sign1 and mDoc primitives are in the codebase today — end-to-end mDoc issuance and presentation is progressing through the same production tenants that already run the verifier.

Next up · wallet-driven remote signing · scoped, dated, on-schedule

Two tracks to complete wallet-driven remote signing on top of the CSC v2 RSSP.

The Cloud Signature Consortium v2 REST surface shipped in the last sprint (see the milestone list above). Two additional tracks complete the wallet-driven remote signing story so a subscriber can scan a QR in a browser and sign a PDF with their EU Digital Identity Wallet against this platform. Both tracks are scoped, reference-repo-aligned and behind honesty-gated feature flags (see the EU RQES reference library).

Both tracks are scoped and filed against the platform’s live TODO list. See the canonical wallet-driven rQES specification for wire-level detail. Honesty note: the spec is explicitly flagged pre-release, still work in progress at both the EUDI Kotlin library and the German BSI Blueprint — we ship each track behind a per-tenant feature flag so wire churn during the 2026 ARF Refinement Round doesn’t destabilise production.

ARF 3.0.0 · released ~late July 2026 · three-layer RP + two-cert + Intermediary role

ARF 3.0.0 fit — and the Intermediary opportunity CTIC is already shaped for.

The European Commission published Architecture and Reference Framework (ARF) 3.0.0 at the end of July 2026. It is the biggest ecosystem change since the 2024 launch: every Relying Party is now decomposed into three formal layers, every service ships with two complementary certificates, and a new Intermediary role lets one party carry the registration and certificate lifecycle for many downstream Relying Parties. CTIC is already the right shape for all three shifts. What follows is an honest split of what we ship today, what maps to the new model, and what we are formally adding.

The ARF 3.0.0 three-layer Relying Party structure. One legal entity may run multiple RP Instances (datacentres, DR sites, tenants). Each Instance exposes one or more Services, each with its own Registration Certificate declaring the exact Intended Use the wallet will let the user share. The wallet now shows the SERVICE name, not just the org name, on its consent screen.

The Intermediary opportunity — CTIC as managed compliance for SMEs.

ARF 3.0.0 formalises the Intermediary role: a special Relying Party that acts on behalf of one or more other Relying Parties, handling Wallet communication without ever storing the content of the transactions it forwards. Not every organisation wants to run its own EU Reference Registry registration, its own EJBCA-issued wrp.p12 lifecycle, its own per-service RC minting and renewals, its own JAdES-B intended-use signer, its own LOTL trust chain check. Most European SMEs — medical practices, MVNOs, hospitality operators, notaries, insurance brokers, retail chains — will not build any of that in-house. This is exactly the compliance-overhead-into-recurring-revenue shape CTIC has been architected for.

CodeB positioned as an ARF 3.0.0 Intermediary. One registration surface to the EU Reference Registry; per-downstream-RP AC + RC issuance and renewal handled by CodeB; the end user still sees only the downstream RP’s name on the wallet consent screen, with Intermediary involvement recorded in the wallet audit log per ARF 3.0.0 traceability rules. This is the missing managed-service layer the SME market has been waiting for.

• Formal mandate flow. Each downstream Relying Party signs a mandate authorising CodeB to act on its behalf; mandate captured via the existing European Business Wallet director-signed workflow. The Registrar verifies the mandate before issuing the RC.
• Per-tenant Intermediary mode. A single intermediary=true flag on the tenant switches eudiw-register.ashx from RP mode to Intermediary mode. Same pipeline, same certificates, different registration frame.
• Downstream RP visibility, not Intermediary visibility. The wallet consent screen shows the downstream RP’s tradeName + verified badge, not CodeB’s. Intermediary involvement is captured in wallet audit logs per the ARF 3.0.0 traceability requirement — useful for compliance, invisible to the user.
• Metered like everything else. Per-downstream-RP and per-Service meters on the same clientRef plumbing already used for wallet verifications, CSC v2 signHash calls, call minutes and AI tokens (see the wholesale distribution section below).
• Legal template. An ARF 3.0.0 Intermediary Mandate Template ships alongside the existing DPIA + RoPA templates — per-tenant configurable via compliance-admin.html.

Positioning note. The three-layer RP structure, the two-certificate model, and the Intermediary role are new formal concepts — the underlying capabilities they organise (AC-style tenant cert, service-scoped attribute lists, third-party managed compliance) have been shipped in CTIC for months. What ARF 3.0.0 gives us is a common vocabulary to describe an offer the SME market has been asking for and no other EU-sovereign vendor is yet positioned to deliver at price. Sales language: “Compliance is a moat when you don’t have to build it yourself.”

Architecture

One deployable stack. Six load-bearing pillars.

CTIC is not a suite of separately-licensed products bolted together. It is one integrated binary that presents six pillars to the operator, each labelled with the exact standard it implements. Every pillar is switchable on or off per tenant, per trunk, per user — so a wholesale operator can start with just the EU Digital Identity Wallet verifier and extend into telephony, signatures, eForms and e-invoicing as their retail programme grows. CTIC is a self-hosted, six-pillar XaaS platform for wholesale telecoms.

CTIC platform architecture — six pillars, one deployable stack. On mobile the two-by-three grid reflows vertically at the same aspect ratio; the SVG viewBox scales fluidly with the container down to 380px widths.

Wholesale distribution

Multi-tier tenancy that keeps every customer relationship end-to-end.

CTIC is wholesale-shaped at the tenancy layer. Aloaha bills the platform tenant. The platform tenant bills its distributor tenants. Each distributor bills its reseller tenants. Each reseller bills the end-customer. Every event carries a clientRef slot so revenue is attributable at any tier — and every tenant owns its own subscriber list, call detail records, recordings and transcripts inside its own domain, end-to-end.

Each tenant is an independent per-domain partition on disk. Every subscriber list, CDR, transcript and recording stays inside its own tenant boundary, owned end-to-end by whichever party in the wholesale-to-retail chain the data belongs to. Diagram remains legible at 380px mobile widths thanks to the responsive viewBox.

Voluntary call-traceability plug-in · sovereign, eIDAS-native

A voluntary plug-in that aligns wholesale and retail telecoms against unidentifiable-call fraud.

CTIC offers global mobile operators, MVNOs, eSIM brands, telecom retailers and their wholesale peers a voluntary plug-in solution to the long-standing traceability problem for unidentifiable calls. Because the same platform runs the EU Digital Identity Wallet verifier, per-trunk SIP-over-TLS, per-trunk SDES SRTP, per-tenant OIDC identity and RFC 4028 Session-Timer, it can attach a chain-of-trust from originating carrier through interconnect to terminating retailer — voluntarily, without waiting for a regulator to mandate it. The six-pillar delivery makes it operationally cheap to adopt: no separate KYC vendor, no separate signalling-protection vendor, no separate identity IdP. This is the missing piece the wholesale-to-retail chain has been waiting for.

The plug-in is designed as the sovereign, eIDAS-native alternative to the US regulatory-driven approach. It attaches a signed attestation at each hop — originating carrier, interconnect, terminating retailer — so the terminating operator and, ultimately, the retail subscriber can see the verified origin of the call. Because CTIC already terminates SIPS, mints per-tenant certificates and issues QES-sealed signatures across the same tenant boundary, no new vendor is needed. Any operator can opt in on their own timeline, and the chain-of-trust flows through only the CTIC-enabled hops.

CTIC-attested chain-of-trust across originating carrier, wholesale interconnect and terminating retailer. Each CTIC-enabled hop attaches a signed attestation the terminating retailer and the verified end-user can inspect. Diagram viewBox 800x260 scales fluidly to 380px mobile.

• Voluntary industry-wide plug-in. Not a regulatory mandate. Any operator, MVNO, eSIM brand, wholesale distributor or retail carrier can opt in on their own timeline — the chain flows through only the CTIC-enabled hops.
• Sovereign, eIDAS-native. Built on eIDAS 2.0 primitives — EU Digital Identity Wallet presentations, QES signatures, per-tenant certificates. No dependency on non-EU regulatory frameworks or non-EU trust anchors.
• Attach the attestation without adding vendors. The six pillars are already in the box: no separate KYC vendor, no separate signalling-protection vendor, no separate IdP. The plug-in reuses what CTIC already ships.
• Wholesale-to-retail chain-of-trust. The attestation attaches at originating carrier, wholesale interconnect and terminating retailer, so the retail subscriber ultimately sees a verified origin for their inbound call.
• Aligns wholesale and retail incentives. Wholesale interconnects that opt in get a differentiator; retail carriers that opt in reduce fraud losses on unidentifiable calls; end subscribers get an inspectable proof.

The 2027 acceptance mandate · four wholesale touchpoints

Where CTIC turns each regulated moment into a wallet flow.

Each of the four touchpoints below is a moment where an EU Member State regulator will, from 2027, expect the wholesale operator to accept an EU Digital Identity Wallet presentation as a valid identity assertion. The flow is the same shape in each case: the subscriber presents from their wallet, CTIC's verifier validates cryptographically, and the operator activates or ports.

Capability breadth

Everything the wholesale operator needs in one stack.

CTIC's XaaS breadth is deliberately unusual for the category. A typical wholesale procurement bundles a verifier from one vendor, an SBC from another, a CPaaS from a third, an e-invoicing SDK from a fourth and a metering system from a fifth. CTIC ships all of the following out of one install.

Sovereignty · no middleman

Self-hosted. No national-identity-cloud in the loop. DR is a folder copy.

A wholesale telecoms buyer's regulatory exposure is directly proportional to the number of vendors sitting between their subscriber and the identity-assertion outcome. CTIC removes middlemen from that chain.

• Self-hosted on operator infrastructure. Deploy inside the operator's own datacentre, a sovereign-cloud region or a colocation cabinet. No Aloaha-side data plane. No mandatory outbound telemetry.
• No national-identity-cloud middleman. The wallet verifier speaks directly to the presenter and the operator's own trust store. The operator does not route identity presentations through an intermediary hosted-verifier service.
• Filesystem-only state. Every setting, every credential store, every recording, every transcript, every CDR is a file on disk in a per-tenant directory. No SQL server dependency. No database patch window.
• Disaster recovery is a folder copy. Snapshot the tenant directory, ship it to a warm-standby node, start the process. No schema migration. No point-in-time restore ceremony.
• No hyperscaler tie-in. The stack runs on .NET Framework 4.8 on any Windows Server. Cert issuance uses public ACME. Storage is native NTFS. Nothing forces the operator into a specific cloud provider.
• Explicit DPO/CISO-friendly logging. Every trust decision leaves a greppable INF-level log line at entry, branch, pre-call and post-call. Auditable by human inspection alone.

Head-to-head

CTIC vs the largest CPaaS incumbents.

The largest hyperscaler-tied CPaaS incumbents were built for retail-app-developer distribution, not European wholesale telecoms procurement. The wholesale buyer's requirement set diverges from that model across the six pillars CTIC ships in one binary — and across the voluntary call-traceability plug-in that rides on top of them.

"Largest CPaaS incumbents" reflects the current public-market positioning of the top-tier CPaaS vendors in 2026. CTIC does not name any competitor by brand.

Deploy in weeks, not quarters

Two timelines. One EU 2027 deadline.

The 2027 EU Digital Identity Wallet acceptance mandate is a hard, dated obligation. The operators who deploy against it early clear procurement conversations with retail partners; the ones who wait for their hyperscaler-tied CPaaS vendor to catch up will be scrambling in the last quarter of 2026.

Two timelines against the 2027 deadline. On mobile the SVG scales down while preserving both timeline tracks — the deadline anchor stays visible at 380px widths.

Next step

Book a wholesale briefing.

Ninety minutes with the CodeB team, walking through the architecture at the depth your procurement, network-architecture and general-counsel functions need. Bring your 2027 readiness questions. Leave with a scoped deployment plan and pricing calibrated to your subscriber volume.

Sovereign SBC SIPS E-Invoicing SDK All features REST + webhook APIs Get your own tenant Compare