Peppol is the backbone of the EU's e-invoicing ecosystem, acting as the standard to ensure compliance with the European Norm EN-16931 and EU Directive 2014/55 for public authorities and businesses. With member states like Belgium making Peppol the default method for mandatory B2B electronic invoicing starting in 2026, its regional importance is massive. But what if we could modernize its traditional 4-corner model? 🇪🇺
Discover a novel Application-to-Application (A2A) alternative using the ICP blockchain! By leveraging **Apache Camel routes** alongside the `dscope-camel-ubl` component, you can seamlessly integrate and exchange structured UBL 2.1 XML documents directly between buyers and suppliers while maintaining strict European semantic norms. 🚀💡
github.com/dscope-io/UBL
#Peppol #EInvoicing #ICP #Blockchain #ApacheCamel #EU #A2A #B2BIntegration
CP-compatible Peppol messaging for European business documents: UBL 2.1 and Peppol standardize invoices, orders, and trade flows across systems and borders, while ICP canisters make document exchange tamper-proof and auditable. Apache Camel + IC4J Camel let you compose richer business processes and connect to 300+ integrations.
GitHub: github.com/dscope-io/dscope-… | github.com/ic4j/ic4j-camel
Peppol: peppol.org
ICP: internetcomputer.org
Apache Camel: camel.apache.org
"Critical."
That's the legal category EU regulators created in November 2025 for AWS, Microsoft Azure, and Google Cloud.
Under DORA - the EU's Digital Operational Resilience Act - the European Banking Authority, ESMA, and EIOPA officially designated all three as Critical third-party providers. Meaning, their failure would constitute systemic risk to the EU financial system.
Banks. Insurers. Investment firms. Payment institutions. Across the EU. Running critical functions on infrastructure regulators now class as a systemic dependency.
So regulators built a new oversight framework. Joint inspection teams. Annual risk analyses. On-site visits.
Not to reduce the dependency. To manage it.
That's not a supervision story. It's an architecture story.
When concentration becomes severe enough that regulators must invent a new legal category to contain the risk - the problem was never regulatory. It was structural.
🚀 Exciting news! We have just released version 0.8.0 of the IC4J Agent and the IC4J Apache Camel Component! 🌐🐪
github.com/ic4j/ic4j-agent
github.com/ic4j/ic4j-camel
What's new? You can now seamlessly integrate the Internet Computer (ICP) with the Model Context Protocol (MCP) using the new Apache Camel MCP Component! 🤖✨
github.com/dscope-io/dscope-…
You can natively execute Motoko smart contracts and expose them as MCP tools and endpoints using pure Camel YAML routes—no custom Java code required!
Check out the new `mcp-icp-motoko` sample to get started! 🛠️
github.com/ic4j/ic4j-camel/b…
#InternetComputer #ICP #ApacheCamel #Java #MCP #AIIntegration
Working on a Visual Studio Code extension for the IC4J Code Generator, which generates Java artifacts from Candid IDL files. This extension supports Java, Spring, and React Native applications that connect to the Internet Computer Protocol (#ICP). An early functional version is already available. #vscode #java @springframework @reactnative
We can now generate #Java Spring @springframework service directly from #ICP Candid file in our Codegen tool github.com/ic4j/ic4j-codegen. Also tested prototype of IntelliJ @intellijidea plugin.
The initial version of the IC4J Java Spring library has been released. Java Spring, a comprehensive framework for building modern, enterprise-level applications, offers robust support for dependency injection, aspect-oriented programming, and web applications. This library enables Java Spring developers to seamlessly integrate ICP canisters into their Spring applications, enhancing functionality and interoperability. Additionally, the library comes with predefined Internet Identity and Management Spring services, further simplifying the development process.
github.com/ic4j/ic4j-spring
The HelloWorld sample demonstrates the use of this library.
github.com/ic4j/samples/tree…
#ICP #Java @springframework
We have recently released an early developer preview of our dScope Apache Camel #ISO20022 Component. This component allows for the processing of #ISO20022 documents and their integration into Apache Camel workflows. @ApacheCamel
github.com/dscope-io/dscope-…
Our component leverages the open-source Prowide Software libraries to achieve this functionality. github.com/prowide/prowide-i…
Our goal is to integrate any system, regardless of format, by utilizing decentralized integration nodes. This latest release represents an important step towards achieving this objective.
In addition, we have updated our Camel ISO20022 sample to utilize the new component in conjunction with an #ICP smart contract.
github.com/dscope-io/ISO2002…
We have published a sample demonstrating how to use Apache Camel and IC4J Camel component (github.com/ic4j/ic4j-camel) to invoke an IC smart contract with an ISO20022 payload (CustomerCreditTransferInitiation). The sample reads the ISO20022 XML payload from an XML file and converts it to JAXB using the Prowide library (dev.prowidesoftware.com/SRU2…). It then calls the IC smart contract with a Motoko payload. The smart contract simply returns the same data back.
We developed the Camel route using the Apache Karavan Visual Studio plug-in, without needing to write any code.
github.com/dscope-io/ISO2002…
#ICP #ApacheCamel #ISO20022 #NoCode













