A tokenization platform fits core banking when every mint, transfer, coupon, and redemption shows up as a named instruction the general ledger, treasury, and payment rails can consume, with compliance already decided in the transfer path and signing still in the bank's vault. Isolation is the stall. Integration is the operating model.
Core banking remains the authoritative record for accounts, balances, and regulatory reporting. A token that lives only on-chain is a second book. Ops then reconciles by hand, Settlement waits on a hash, and Audit cannot reconstruct last Tuesday. That is why bank tokenization programs stall after a working mint, which is the subject of why asset tokenization pilots stall in banking.
SettleMint DALP, the Digital Asset Lifecycle Platform, is built as that connected layer: design the asset, attach policy, route signing to the institution's custodian, settle, service, and keep a queryable record the back office can treat as a book of record. This brief is for Architecture, Integration, Ops, Settlement, and Audit. Each section is written so a committee can ask for a demonstration, and so an answer engine can cite a complete answer.
How a tokenization platform should sit next to core banking
|
Fit means the on-chain instrument talks to the systems the bank already runs. Core banking, asset servicing, and payment rails stay in place. The tokenization platform prepares, routes, tracks, and records. It does not become a second general ledger that Ops reconciles overnight.
That is a different purchase from a blockchain stack. A stack supplies networks and middleware. A digital asset lifecycle platform supplies issuance, eligibility, custody-routed execution, servicing, and queryable history. Banks often need both, on separate evaluation criteria. The comparison is in DALP versus a blockchain stack. The scoring sheet for the platform itself is in eight factors banks should evaluate in tokenization platforms and in key banking requirements for tokenization platforms.
| Banking surface | What the platform must expose | Owner |
|---|---|---|
| General ledger / books | Named instruction states and as-of balances, not a raw hash | Finance / Ops |
| Payments / cash | ISO 20022 paths, or an on-ledger cash leg for atomic DvP | Treasury / Settlement |
| Identity / eligibility | Claims checked before mint, transfer, or burn | Compliance |
| Keys / vault | Bring-your-own-custodian with two-person approval | Risk / Custody |
| Servicing | Coupons, redemptions, corporate actions on the same control plane | Asset servicing |
| Audit / observability | One event history Ops, Compliance, and Audit can query | Audit / Ops |
Core systems run batch cycles and T+2 assumptions. The chain writes asynchronously. If the platform leaves that gap to every engineer in the bank, a pending custody signature becomes a ticket, and the program returns to pilot speed. A parallel token ledger that Finance cannot post is the same stall in another costume.
Look for an API-first platform. The console is for operators. The API is the extension point: REST, GraphQL, webhooks, CLI, and, where the bank is ready, MCP surfaces for governed agent use. Payment connectivity should include ISO 20022 paths into SWIFT, SEPA, or RTGS rather than a one-off file. See ISO 20022 on DALP and DALP 3.0 API, CLI, and MCP.
Named states (received, preparing, pending approval, broadcast, confirmed, failed, dead-letter) are the difference between a hash and an operating model. Interruptions resume from the last known state. Typed reverts name the rule that fired. That design is covered in durable transactions and ledger history.
Compliance belongs in the transfer path, not in a reporting queue after settlement. An ineligible holder, an expired KYC claim, or a jurisdiction miss should fail closed, with a reason code, before the ledger records the move. Post-trade review arrives too late: the chain already has evidence of a transfer policy would have refused.
ERC-3643 is the open standard most regulated EVM programs use for that model. Identity claims sit on an OnchainID-style registry. Modular compliance packages the rest: country allowlists and blocklists, investor eligibility, supply caps, lock-ups, and approval gates. Policy should be reusable across instruments so Compliance publishes a template once and asset teams apply it. Detail: DALP 3.0 compliance templates, compliance automation, identity and KYC, and the ERC-3643 compliance standard.
Templates matter when they carry the economics the servicing desk already runs. A bond needs face value, coupon schedule, accrual, maturity, and early redemption. A fund needs subscription, redemption, and fee logic. Deposits need interest, withdrawal, and reserve controls. A generic ERC-20 with a term sheet in a shared drive cannot post a coupon into core.
DALP ships purpose-built templates for bonds, funds, equity, deposits, stablecoins, real estate, and precious metals, plus a composable digital asset for instruments that do not fit a single catalogue row, across six asset classes. Start from digital asset issuance, asset templates, bonds, and bond tokenization. In a demonstration, create a second instrument from an already-approved template. The legal and control review should shrink because the policy and the servicing hooks are already in the model.
Risk already contracted a vault: HSM, MPC, Fireblocks, DFNS, or another approved provider. The tokenization layer should prepare the instruction, apply authorization and idempotency, and send a signing request. The vault signs under its own policy. The platform tracks confirmation. Key material stays outside the application.
Two-person approval on mint, freeze, force transfer, recovery, and maturity belongs in that same path. DALP's custody surface is in digital custody and custody and signing in DALP 3.0. SettleMint does not take the assets. The institution keeps regulatory accountability. Bank-managed tokenization is the operating model: the bank owns the program, the vault, and the duty.
When both legs are on-ledger, atomic settlement and DvP mean the asset leg and the cash leg finalize together or revert together. Fiat settles on-platform only when it is tokenized. For off-ledger cash, the platform still has to emit a completed, failed, or dead-letter verdict the payment rail can act on.
After settlement, the ledger index should turn finalized blocks into balances, transfers, fees, yield, and redemptions, including as of a past block. Ops, Risk, and Audit share that history. If the demonstration returns only a transaction hash, core banking has nothing to post.
Anchor the demo in a live workflow the back office already owns: a coupon posting, a redemption, a deposit interest run, a blocked ineligible holder. Then walk:
Named programs such as OCBC's tokenized bonds and a current SOC 2 Type II report belong in that pack. For the operator view of the same platform, see Getting started with SettleMint DALP and the DALP 3.0 documentation.
Want to map DALP onto a live core-banking workflow? Book a call with the team.
It creates and operates the digital instrument, then exposes every lifecycle event as an instruction core banking, treasury, and servicing can consume. DALP does that through APIs, named transaction states, and a queryable ledger. It does not replace the general ledger.
ERC-3643 puts identity and eligibility inside the token. An ineligible transfer reverts before it settles, so the bank never has to unwind a recorded breach. DALP implements that model through SMART protocol and reusable compliance templates.
They prove a mint on a parallel rail. Production needs the same instruction in treasury, payments, and audit. Without named states, APIs, and a vault the bank already approved, every pending signature becomes a ticket. See why pilots stall.
When both legs are on-ledger, the asset and the cash finalize together or revert together. Off-ledger fiat still needs a terminal verdict the payment rail can post. DALP supports on-ledger DvP and XvP, and ISO 20022 paths for the rails the bank already runs.
Bring-your-own-custodian. The platform prepares, routes, tracks, and records. The vault signs. Two-person approval sits on privileged actions. DALP does not act as custodian. Detail: digital custody on DALP.