MDE Flow
Real-time communication of your entire Sales and Invoicing.
Real-time communication of your entire Sales and Invoicing pipeline. MDE Flow is an enterprise B2B integration platform built on .NET 10. It speaks every major EDI format — EDIFACT, ANSI X.12, VDA, TRADACOMS, XML, and JSON — over every standard transport protocol: AS2, OFTP2, SFTP, FTPS, SOAP, X.400 and REST. Every message is validated, deduplicated, and delivered exactly once through a pluggable outbox architecture. Out of the box it integrates with Microsoft Dynamics 365 Business Central — and its delivery layer is fully extensible, making it straightforward to connect any ERP, WMS, or backend system. Adding a new trading partner requires no code — only configuration.
Security Architecture
Security built into every layer
Every message MDE Flow processes is encrypted, authenticated, and verifiable end-to-end. Security is not an add-on — it is enforced at the transport, payload, and application layer simultaneously.
- Multi-layer transport security.
- Every channel enforces TLS 1.3 (RFC 8446). OFTP2 and AS2 add mutual TLS (mTLS) with X.509 certificate chain validation and online CRL checking — no unverified connection is ever accepted.
- Payload encryption & signature verification.
- Inbound AS2 and OFTP2 payloads are decrypted and signature-verified using CMS/PKCS#7 (RFC 5652) with AES-256 before any business logic runs. Encryption and signing certificates are managed independently per trading partner.
- Per-partner authentication — 4 modes.
- Each trading partner is authenticated independently: API Key (O(1) lookup), JWT Bearer with OIDC issuer and clientId whitelist (RFC 7519), mutual TLS with thumbprint pinning, or None for trusted internal networks.
Everything you need
All-in-one platform
The platform manages the complete inbound-to-outbound lifecycle. Each with a single responsibility. No circular dependencies. No shared mutable state. Every component can be tested, replaced, or extended independently. 12+ dedicated test projects with 475+ total test files.
- EDI
- ORDERS/INVOIC parsing for D96A, D97A, D99B, D01B, EANCOM/GS1.
- ASC X12
- 850 (Orders) / 810 (Invoice), versions 004010 + 005010.
- VDA
- Parsing VDA 4905/4913 (Orders) / 4908/4938 (Invoices).
- TRADACOMS
- Parsing ORDERS 9 / INVFIL 9.
- XML
- XSD-validated XML (per-partner schema registry).
- JSON
- JSON parsing.
- Secure
- TLS (RFC 5246), mTLS, Cert Validation, Decryption, Signature Verify.
- MS Dynamics 365 Business Central
- Multi company routing, Order and Invoice delivery.
We are..
We set out with the mission of accelerating and empowering software development teams.
Our priorities in software development are architecture, appropriate design, security, and performance.
Our mission
Our mission is to eliminate the complexity of B2B integration. Trading partners speak different languages — different formats, different protocols, different standards.
MDE Flow speaks all of them. We believe that connecting a new partner should be a matter of configuration, not code. That every message should arrive exactly once, securely and traceable end-to-end. And that the system beneath it all should be clean enough to last, solid enough to scale and open enough to grow with your business.
The numbers
- Transport Layer
- 7
- Security Layer
- 6
- Format Parser
- 6
- Canonical Model
- 6
- Transactional Outbox
- 6
Ready to dive in?
Our Transport Stacks
AS2 (Applicability Statement 2)
MDE Flow implements AS2 (RFC 4130) with full CMS/PKCS#7 payload encryption and RSA signature verification (RFC 5652). Both synchronous and asynchronous MDN (RFC 3798) are supported — async delivery runs through the Transactional Outbox for guaranteed acknowledgement. SSRF prevention, header whitelist validation, and per-partner certificate pinning are built in.
OFTP/OFTP 2
MDE Flow implements OFTP2 (RFC 5024) as a full-stack protocol engine. STB framing is byte-precise, DEB reassembly is allocation-free. All sessions enforce mutual TLS. EERP/NERP receipts are CMS/PKCS#7 signed (RFC 5652) with configurable hash algorithms and enforced minimum RSA key sizes. A notable detail: the SignedEerpRequest flag is read from the RFC-mandated byte offset 161 — a compliance detail many competing products get wrong.
SFTP/FTPS
SFTP is implemented over the full SSH protocol stack (RFC 4253/4254) with SHA-256 host key fingerprint pinning and PEM private key authentication. FTPS implements FTP over TLS (RFC 4217) in both Implicit and Explicit modes, with server certificate thumbprint pinning and sidecar SHA-256 transfer integrity verification.
REST/HTTP
MDE Flow exposes a standards-based REST API for inbound EDI delivery over TLS 1.3 (RFC 8446). Authentication supports JWT Bearer (RFC 7519) and API key modes per trading partner. JSON payloads are processed with AOT-ready source generators (RFC 8259). Outbound delivery to Business Central uses OAuth 2.0 Client Credentials (RFC 6749) via MSAL with proactive token refresh.
SOAP
MDE Flow supports SOAP 1.1 and 1.2 (W3C) with WS-Security (OASIS), a structured envelope builder, and automatic fault detection. Delivery runs through the Transactional Outbox for reliable exactly-once processing.
X400
MDE Flow supports X.400 messaging for legacy automotive and financial EDI over both HTTP and SMTP transport modes. VAN envelope handling, OR address parsing, CMS payload encryption (RFC 5652), and delivery reports are fully supported out of the box.