Transfer
€240,000.00
Completion · 14 Rue des Écoles
Approvesigned
One capability
A message can be the document itself.
An approval, form or appointment can arrive as structured fields inside the encrypted conversation. People and agents work with supported message types at their endpoints; the relay carries ciphertext.
Three things are true of every one
- Typed
- It arrives as something your device understands. Fields with names, values with units, an amount that is a number rather than a picture of one.
- Opaque
- People and invited agents decrypt messages at their own endpoints. The relay cannot read protected content, but it knows Space membership and who posts. Timing and delivery information still exist.
- Signed
- For consequential actions, require an authorised person’s approval and check the exact terms before acting. Permissions and enforcement depend on the agent and deployment.
What a type looks like
InTouch defines 47 message schemas. These examples show their fields and possible uses. App support, composing a message and connecting external actions are separate integration steps.
Health
- Prescription
- Medicine · dose · schedule · dispensing pharmacy
- Referral
- Specialty · urgency · notes · patient reference
- Result
- Test · value · reference range · reporting clinician
Money
- Transfer
- Amount · account · reference · approver
- Invoice
- Line items · total · due date · terms
- Mandate
- Payer · limit · expiry
Legal
- Contract
- Parties · terms · execution date
- Signature
- Signatory · method · timestamp
- Disclosure
- Matter · recipient · scope
Operations
- Handover
- Shift · outstanding items · keys held
- Inspection
- Location · checks · defects · sign-off
- Incident
- Severity · systems affected · actions taken
Logistics
- Delivery
- Consignment · quantity · receiver
- Collection
- Slot · address · contact
- Damage report
- Item · condition · claim reference
Scheduling
- Appointment
- Time · place · attendees
- Booking
- Resource · duration · cost
- Cancellation
- Reference · reason · notice given
The same message, twice
One payload, one journey, two views of it. On your device it is a payment request with an amount on it and a button that says approve. On the wire it is a run of bytes with a length and a delivery token. There is no third version, held somewhere in the middle, that we can read.
On your device
On the wire
ciphertext · no type · no fields · no amount
Define your own
A custom type needs a schema and a client renderer. Your integration supplies them; the relay can carry the encrypted payload without reading its fields.
Schema plus renderer. The relay is unchanged.
To us it is all just ciphertext.
Whatever shape you give a message, the part we handle is the part we cannot read. That is the same for a sentence, a prescription and a payment.