Supported cores
Fiserv
Production. Live on the Fiserv AppMarket, integrated by the Fiserv team.
Jack Henry
Production on SilverLake, including securities held on the general ledger.
Custom cores
Batch and API based cores without a prebuilt connector, integrated through
the deposit product model.
Cosmos Tokenization Suite on the Fiserv AppMarket
Banks with a Fiserv-based core can start from the AppMarket listing. The
Fiserv team has already integrated CTS there.
Tokenize and writeback
The integration runs in both directions. The model requires both directions. Tokenization is the process that reads a client’s deposit balance from the core ledger and creates a corresponding digital ledger entry. Writeback is the process that pushes digital ledger balance changes back to the core. This ensures that an on-ledger payment appears in the bank’s reporting system. Without writeback, the two ledgers drift apart, and the tokenized balance stops being trustworthy. Reconciliation is the connector’s normal operating mode, not a periodic batch process added afterward. See Reconciliation.What this preserves
Keeping the core authoritative is a deliberate constraint:- Accounting, regulatory reporting, and audit continue to use the same system they use today
- The deposit continues to be held and reported on the core
- Existing controls over the core remain unchanged
- A bank can stop issuing tokenized deposits without unwinding its books
Before you start
Core Requirements lists the read and write surface CTS needs from any core. Checking a core against these requirements is the fastest way to establish whether an integration is viable. The requirements apply with or without a prebuilt connector.Version requirements for each core, the certification process, and the setup
steps specific to each platform still need to be documented.
Integration reference
- Core Requirements describes the read and write surface that any core must expose
- Integration Architecture describes connection patterns and failure handling
- Custom Cores describes the deposit product model and cores without a connector
- ISO 20022 Messaging describes the message-based path
- Reconciliation describes tokenization, writeback, and divergence
Related
- Issuance, the solution this integration supports
- Getting Started for the setup flow
- Digital Ledger Support for the platforms that run the digital ledger