Integration That Enforces Instead of Connecting
Every integration platform on the market was built for a world where the thing on the far side of the connector could not act on its own. Move a payload from A to B, transform it in flight, retry on failure. Governance, where it exists, is a wrapper around the outside.
Autonomous software breaks that assumption. The thing on the far side now decides what to call, when, and why. Anything that can discover an endpoint can invoke it; anything that can invoke it can chain it. The moment two individually permitted calls are chained, an institution has a capability nobody authorised and nobody can prove was bounded.
inConcert is an integration fabric in which discovery itself is governed. Nothing can be found that has not been certified, nothing can be invoked without single-use authority bounded by its human principal's own, and nothing executes against a component whose supply-chain record has gone stale. Integration stops being plumbing and becomes the place the rules are enforced.
Meaning is not allowed to drift at the boundary. Incoming data is mapped to the platform's governed definitions rather than to an internal house format, and a term with no exact match is refused rather than rounded to the nearest one. Most integration failures are not dropped messages; they are two systems agreeing on a word and disagreeing on what it means. That failure mode is closed here by construction.
When the Network Drops Mid-Transaction
Connectivity fails. The question is what the customer standing at the terminal experiences when it does, and the answer is designed rather than hoped for.
Edge appliances hold enough hardware-backed authority to keep authenticating people locally while the connection is down. Work does not stop and it does not silently proceed unchecked – transactions completed in that window are stamped and marked provisional, and when the connection returns the platform reconciles them against the rules that were actually in force at the time, unwinding or compensating anything that ran against authority since revoked.
For the customer, the behaviour is the same offline as online. For the operator, the exposure during the outage is bounded and measured rather than discovered afterwards in the logs.
For Customers Without a Smartphone
A platform that only works for people with a current smartphone and a good signal is not infrastructure. Three routes exist for everyone else, and none of them is a degraded fallback.
A physical card, issued on the spot
Banks and qualified trust providers can issue branded physical credentials at a community kiosk or a locker shop, cryptographically linked to the holder's identity in the same way a phone would be. If it is lost, it is revoked.
The kiosk itself as the device
A community terminal carries the same interaction pattern as a phone. The customer brings nothing; the appliance does the work locally, including while the network is down.
A qualified officer, remotely
Where a case needs a human, a bank or council officer can join the session from anywhere – so the complex application does not require the branch to still be open, or to still exist.
The design goal here is explicit in the architecture: reach the people conventional digital services leave behind, rather than assuming them away.
Engineered for Institutional Margins.
Adopted for Human Sovereignty.
Every capability across the Salient Innovation Set delivers an immediate, symmetrical return: radical margin recovery for the enterprise tenant, paired with frictionless dignity and absolute cryptographic safety for the citizen.
How the Tenant Expands Margins
Transforming operating models from defensive cost centres into agile, shared revenue engines through multi-tenant pooling and mathematical compliance.
-
CapEx Pooling & No Single-Tenant Hardware
POI Appliances run white-label on co-funded premises. Reach 50 commercial catchments without funding 50 proprietary branch builds.
-
Zero Interchange & Flat-Fee Clearing
Instant Account-to-Account rails (SEPA Instant / PayShap) bypass 1.5–3.5% card scheme tolls with predictable, flat sub-cent clearing fees.
-
Compliance by Construction
Agreement DAGs enforce statutory mandates at wire speed; non-compliant states cannot execute, eliminating retrospective audit penalties.
-
Accelerated Partner Onboarding
Pre-verified BIAN and ArchiMate capability components compress multi-firm integration cycles from quarters to days.
Why the Customer Loves Using It
Delivering sovereign dignity and verifiable security where users never surrender control over their identity, consent, or funds.
-
Nothing Stored to Steal
Credentials remain in the user's oneWallet. A breach of a merchant's server reveals zero identity records, protecting citizens completely.
-
One Pattern, Everywhere
The same intuitive tap-and-confirm interaction works seamlessly at a high-street kiosk, transit hub, EV charger, or smartphone.
-
Delegated Authority, Never Escalated
Autonomous AI agents carry single-use, bounded warrants; an agent checking information cannot escalate its authority to transfer money.
-
Payments That Do Not Fail
When a payment network degrades, the transaction reroutes with authentication preserved – zero declines, zero repeated entries.
inConcert Runtime Manifest
Governed Integration Fabric
Customer Journey Convergence & Friction Reduction
Today an institution's regulatory perimeter has a hole exactly where its partners connect. Every connector is a place where evidence is lost, purpose is unstated and liability is ambiguous. Making integration the enforcement surface closes that hole – and removes a standing audit finding along with it.
Because a credential is not bound to a processor until the moment of dispatch, a failing rail becomes a routing decision rather than a failed transaction. Authentication travels with the credential, so the backup rail accepts it natively. The customer does not re-authenticate; the payment simply completes elsewhere.
PSD3 / SCA Compliance
Payment initiation and data access are modelled as explicit permissions with purpose stated, and consent is bound into the data record and enforced at execution rather than checked at the door.
Rail Outages Stop Being Customer-Visible
A degraded rail reroutes with the authentication already carried across. No decline, no re-entry, no second attempt – and no abandoned basket.
Orchestration & Symphony Integration
As a synchronisation mechanism within the System of Engagement (SoE), inConcert coordinates interactive states across distributed endpoints. It communicates directly with the Symphony layers to enforce consistency:
State Normalisation
Maps external payloads onto the platform's governed definitions, so a term that has no exact match is refused rather than quietly approximated.
Adjudication Gate
Ensures session state transitions receive dynamic validation warrants from the DRAGON engine.
Evidence as a By-Product
Every translation and routing decision is recorded with the reason it was made, so the path can be replayed rather than reconstructed. Evidence is produced by operating, not assembled afterwards for an audit.
Enforcement Path and State Reconciliation
The formal treatment – how credentials and keys move across secure hardware boundaries, how state is reconciled deterministically, and the two-clock time model behind replayable evidence – is compiled in the Deep Tech Series.
Roadmap position: inConcert is part of the onePOI.online reference architecture, validated for viability by end of 2028. Tenant cohorts derive a target state from this architecture and transition toward it on their own roadmap; capabilities described here are design targets, not shipped product.