Tumi Institutional Token Studio for Banks
Bank-issued tokens with institutional controls: configure, deploy, and operate tumi.token with msig or HSM authority, not a clerk’s personal wallet.
The problem
- Retail create-token puts issuer keys in the wrong trust model for a regulated mint.
- Fiat reserve, screening, and chain issue must stay in one audited lifecycle.
- Pause, freeze, clawback, and mint caps have to be first-class, not afterthought scripts.
What Sika gives you
Policy wizard
Legal form, closed-loop defaults, flags, and roles before deploy.
tumi.token template
Whitelist, freeze, blacklist, clawback, pause, caps, mandatory memos.
Org authority
Issue, retire, compliance, and pause roles via msig or HSM.
Mint / redeem orchestration
Screening, oracle peg, liquidity, and FLEXCUBE-style reserve holds.
Day-2 ops
Queues, freeze controls, attestation export, audit hash chain.
Four-way recon
Chain PoR, core CASA, gateway journal, and bank statements.
Hard boundary
Issuer keys never in Sika App or retail wallet plugins.
Launch your institution on Sika
From application to a live, compliant bank in weeks, not years.
How it works
Four steps, all on a single audited core banking ledger.
- 1
Configure
Ops complete the Tumi wizard and deploy a versioned tumi.token template.
- 2
Gate
Mint requires clean screening, peg, liquidity, and a fiat reserve hold.
- 3
Issue
The gateway posts core entries and the chain issues only after gates pass.
- 4
Operate
Day-2 console handles freeze, clawback, recon breaks, and attestations.
Tumi Institutional Tokens: FAQ
Is Tumi included in Enterprise?
No. Tumi is a premium add-on on every plan, including Enterprise. It is priced for the cost of building regulated issuance, not as a thin feature toggle.
Can clerks mint from the mobile banking app?
No. Issuer keys stay in org msig or HSM paths. The retail app is holder UX only; Tumi Studio and the gateway run mint and redeem.
Launch your institution on Sika
From application to a live, compliant bank in weeks, not years.