Onchain Features · 05 / 8
Rules, splits and references ride with money.
On Tempo, a payment can carry an invoice reference, follow a compliance policy, split across recipients, and run under a delegated key with a spending limit. These rules are enforced by the protocol, not in a spreadsheet afterwards.
0 bytes
Memo on every transfer
Source · TIP-20
0 tx
Atomic batch of many calls
Source · Tempo Transactions
0 min
Expiring nonce window
Source · T11
Toggle the rules. Each one is a protocol feature that executes with the transfer.
Rules
Tempo transaction
{ to: pathUSD, amount: 1,000.00 memo: "INV-2041" policy: TIP-403 allowlist }
2 rules enforced by the protocol, in one transaction.
Attach a memo
transferWithMemo indexes a 32-byte reference.
Check a policy
TIP-403 allow/block lists run before the transfer.
Batch and delegate
Many calls, one signature, or a key with limits.
Howard Hughes· Corporate treasury
Month-end
Always
Reconciliation
“We're working to solve this with Tempo as a single, trustworthy ledger across every entity and every payment rail, while protecting the security of our sensitive information.”
Read story
DoorDash· Marketplace payouts
Days
<1 second
Dasher payouts
“If we can get merchants and Dashers their money faster, and do that in a way that's affordable for them, that's a no-brainer for the entire ecosystem.”
Read story
Karta· Self-custody money app
Live signature
Access Key
Card auth
“Tempo is the first chain where we didn't have to trade self-custody for a product that actually works.”
Read storyContinuous reconciliation
Howard Hughes: from month-end to always.
Refunds and splits
DoorDash: multi-party flows as code.
Async card auth
Karta: access keys sign without a live prompt.