Skip to main content
REM Sync delivers canonical financial events and state into existing systems. REM integrates these systems; it does not replace them.
REM does not publish a public, self-serve API. Interfaces are configured per deployment against the destination systems in scope, and their schemas are versioned with the canonical model.

​
Delivery interfaces

​
Enterprise connectors

REM connects to the systems around the ledger, as each engagement requires:
  • ERP and accounting systems;
  • custody and wallet providers;
  • treasury and bank systems;
  • compliance providers (KYC, KYT, sanctions, Travel Rule), as inputs to a workflow; and
  • internal ledgers and books of record.
ISO 20022 and FIX are supported only for a validated workflow that needs them.

​
Delivery guarantees

  • At-least-once ingestion, exactly-once business effects. Every delivery carries stable event identifiers so consumers can apply idempotently. Replays and retries do not double-credit.
  • Finality-aware. Events carry their finality and correction state. Consumers can choose to act only on finalised events, and corrections are delivered as first-class events.
  • Traceable. Every delivered event links back to its raw source record and forward to every action taken on it.
  • Versioned. Schemas, mappings, and policies are versioned, and a change never silently rewrites history.