Integrating
Monitoring intents
A monitoring intent is a persistent instruction attached to an account: “when money arrives, do this.” The headline case is auto-debit — an intended debit that waits for a credit and is collected the instant funds land. It is event-driven: it fires on the incoming credit itself, not on a nightly batch that sweeps every account.
Why event-driven collection matters
No daily sweep → lower cost
There is no job scanning every account, every day to find ones that can now be debited. Only an account that actually receives activity is checked, and only if it has an active intent. Work is proportional to real events, not to the size of the book.
No escape window
With a batch sweep, a client could receive funds and spend them minutes later, slipping out before the sweep runs. An intent fires on the credit itself, so the waiting debit is collected the moment money lands — the client can’t outrun the batch.
How it works
1 · Register the intent
Create a monitoring intent on the account for an amount due (e.g. a bill or scheduled debit). It persists as active, waiting.
2 · A credit arrives
When any transaction touches that account, Digital Twin checks its active intents and reacquires the newly available funds toward the amount due.
3 · Realize or keep waiting
Collect fully → the intent is realized and closes. Partial funds → it collects what it can and stays active for the rest. It can be cancelled before anything is collected.
Two flavors
Auto-debit
A waiting debit (bill, scheduled collection) that realizes as credits arrive — the case above.
Auto-block / hold
Automatically block/hold funds as they become available — reserve incoming money instead of debiting it.
“Intent” is Digital Twin’s general term for a persisted, deferred instruction realized later on a trigger. Auto-debit and auto-block are monitoring intents; other kinds cover deferred entry adjustments. This page focuses on the balance-monitoring case.
Machine-readable, in-depth docs for AI coding agents: see llms.txt.