Knova helps financial institutions launch tokenized payment products while keeping their existing systems and providers. Its partnership with Tempo connects payments, stablecoins and tokenized deposits to those systems through one operating platform. Request a briefing on the Knova integration.
One platform for traditional and tokenized assets
Knova is a financial operations platform that connects institutions’ existing systems, asset data and transaction workflows. Banks and other financial institutions can use it to coordinate traditional and digital assets while continuing to work with their custody and payment providers.
The platform combines three components. Connectors link the systems an institution uses. Digital Twin Assets create standardized records of assets, including ownership and current state. A Transaction Workflow Engine uses those records and connections to automate operations across blockchain networks and existing financial systems.
That gives institutions a way to manage processes that span multiple assets and providers. Knova’s platform supports workflows such as netted settlement, moving balances between accounts and converting between traditional money and stablecoins. Knova coordinates these operations without holding customer assets.
Connecting Knova to Tempo
Knova’s partnership with Tempo focuses on bringing that simplified operating model to payments, stablecoins, and tokenized deposits on Tempo. For financial institutions, the aim is to connect a new settlement network to the systems and processes they’re already running.
Institutions can connect supported TIP-20 assets on Tempo or create new tokens through Knova. Knova supports TIP-20 transfers and, where the institution has the required issuer permissions, minting and burning. The integration also credits inbound on-chain deposits and debits outbound withdrawals.
Supported Tempo assets and events connect to Knova’s Transaction Engine and digital twins, so institutions can configure workflows and automations and apply AI-driven insights and actions. Knova uses Tempo’s webhooks to receive on-chain updates. Institutions sign transactions through a supported wallet provider of their choice, with custody remaining with the institution or its chosen custody provider.
An illustrative tokenized deposit workflow
Issuance and bank controls
Consider a bank that wants to issue tokenized deposits backed by customer funds. It could configure approval and screening steps in Knova’s Transaction Engine, using its existing compliance systems for KYC, AML and sanctions checks. Knova would orchestrate those checks rather than perform them. The bank could place these steps before issuance or elsewhere in the workflow, based on its risk and compliance requirements.
Once the configured checks pass, Knova could instruct the bank’s core system to move the corresponding funds into a settlement account, where the bank’s controls reserve them for redemption. Using an account with the required issuer permissions, the workflow could then mint the equivalent TIP-20 balance on Tempo. A digital twin record would link that on-chain balance to the reserved funds.
Private transfers between banks
Using Tempo Zones, currently available on testnet only, a bank could operate its own private execution environment. Knova could coordinate both banks’ configured checks before routing a transfer between their Zones. This would allow the banks to transact without exposing their broader internal balances and transaction histories to each other or public observers. Each Zone operator would retain visibility into its own Zone to support compliance processes. Some deposit and withdrawal information would remain visible on the public chain.
Liquidity and redemption
As balances accumulate, the bank could configure Knova to reconcile and rebalance funds across its traditional payment systems at specified thresholds or on a schedule. Those movements would follow the bank’s reserve and liquidity controls.
On redemption, the workflow could first return the customer’s tokens to an issuer-authorized account for burning. Only after the burn is confirmed via Tempo’s webhook would the bank’s core system release the corresponding reserved funds to the customer. Knova would reconcile the traditional ledger and on-chain balances as each step is confirmed.
This example shows how Knova can coordinate institutional systems and operational workflows around settlement on Tempo. The exact configuration depends on the bank’s systems, permissions and controls.
Why Tempo
Knova is chain-agnostic by design. Its platform connects institutions’ existing systems to supported networks for a given asset or workflow. Tempo adds a network built for payments, with fast, low-cost settlement. The integration brings token operations on Tempo into Knova’s configurable workflows and controls.
Tempo is a blockchain built for payments, incubated by Stripe and Paradigm. Standard token transfers typically cost less than a tenth of a cent, with fees payable in supported USD stablecoins. Payment memos carry references that help enterprise operations teams match transfers to their internal records.
“Our goal is to make it dramatically easier for financial institutions to launch tokenized payment products without rebuilding their existing infrastructure. Together with Tempo, Knova provides the operational layer to connect systems, automate workflows, and reconcile activity—helping institutions move from idea to production faster, all from one control plane.”
Natalya Thakur, CEO, Knova
“Knova is helping financial institutions bring stablecoins and tokenized deposits into the systems they already use. We’re glad to support that work as Knova brings more institutional payment flows onto a network designed for payments.”
Ninad Nirgudkar, GTM, Tempo
Discuss your integration
If your institution is evaluating payments, stablecoins or tokenized deposits on Tempo, request a briefing on the Knova integration so our teams can help you work out the best path forward.
