Platform/INT
Everything else you run, connected.
Banks, tax portals, carriers and your own tools, with every failure kept as a record.
Categories named below·Two-way where it makes sense·Failures are records
One ledger, connectedWebhook-first
BankingE-invoicingCarriersPaymentsIdentityMore
Dry run any timeFailures are records
ILLUSTRATIVE · SIX FAMILIES OF CONNECTION
The catalogue/01
Six families of connection.
Banking and cash
Open Banking feedsStatement formatsPayment initiationCard and expense providers
E-invoicing and tax
PeppolNational mandatesMaking Tax DigitalValidation first
Carriers and logistics
Parcel carriersFreight and pallet networksTracking and proof of deliveryCustoms documentation
Payments and collections
Card and wallet gatewaysDirect debitPayoutsSettlement reconciliation
Identity and workplace
SSOSCIM provisioningDirectory groups to rolesMail and calendar
Everything else
REST and webhooksTyped SDKsiPaaSFlat file and SFTP
What is inside · 17 features/02
4 areas. Pick one.
How a connection is held, and how narrowly.
Scoped per connectorOAuth where offeredLeast privilege by defaultRotation without downtime
How it runs/03
Four steps, in order.
01Authorise
02Map
03Dry run
04Monitor
The facts/04
What an architect checks.
Transport
Webhook-first; polling only where a provider offers no push
Credentials
Encrypted per connector, never readable back, rotatable live
Mappings
Versioned records, reviewable, per company
Idempotency
Replayed events never double-post
Failure
A record with payload, error, and retry — never silent
Backoff
Exponential retry with circuit breaking on persistent errors
Verification
Dry run available at any time, not only at setup
Drift
Per-connector reconciliation report
Where it stops/05
What it will not do.
Next step