Five categories. One signature. The moments that matter.
Each category passes the same four-criterion test — high stakes, hard to reverse, documented vulnerability window, weak existing consent evidence. Each applies the same SoM Signature primitive. Each integrates at the moment where consent is the question. Where you start depends on your stack.
Same primitive. Five commercial environments.
Each category is independently authoritative — different regulators, different buyers, different threat surfaces. Together they cover the most acute hard-to-reverse transaction surfaces in the market today.
Was this push payment authorized — or coerced?
APP scams, real-time payments fraud, high-value wires, in-branch teller decisions, cross-border SEPA Instant. The transaction looks legitimate; the customer looks like themselves; only the consent is in question. Bank-side integration at the wire authorization or step-up moment.
- APP scam protection (PSR)
- RTP / FedNow / Pix fraud
- High-value wire transfers
- Card-not-present step-up
- In-branch teller alerts
- Cross-border SEPA Instant
Was this fiduciary decision freely made?
Elder financial exploitation, discretionary trade authorization, Reg BI care obligations, capacity-relevant decisions, beneficiary changes. The hardest questions in wealth share a common evidentiary gap. Engagement-mode capture during advisor-client video consultations; dual-template reporting for client and reviewer.
- Elder exploitation (2165)
- Fiduciary engagement (Reg BI)
- Discretionary trade auth
- Capacity-relevant decisions
- Beneficiary changes
- Large distributions
Agents need a signature, not just a scope.
OAuth tokens prove an AI agent is allowed to call an API. They don't prove a human freely authorized the underlying action. Authorization-class signatures bind to delegation moments; scope, TTL, and agent ID carry through every downstream call. Framework-agnostic SDK; bank-side and contract-side verification.
- Agent-initiated payments
- Autonomous invoice processing
- Scheduled background actions
- Agent-to-agent transactions
- Smart contract authorization
- Recurring subscription auth
Your keys, your coins, your consent.
Hardware wallets prove who holds the keys. SoM Sig proves the key-holder is acting freely. Wrench attacks, pig-butchering schemes, drainer approvals — defended at the signing surface, on-device, self-custodial. No third-party trust required; verification library open-source-committed.
- Wrench attacks / coercion
- Pig-butchering scams
- Drainer-contract approvals
- SIM-swap recovery hijack
- Compromised endpoint signing
- Multi-sig per-signer attestation
Six figures wired. Deed recorded. Consent verified.
Closing-wire BEC, elder asset stripping, coerced quitclaim deeds, predatory refinances. The documents are valid; the signatures are real; the consent was the gap. Two integration points working together: bank-side wire authorization catches the BEC at T-1; title-side closing-surface captures the genuine consent at T+0. Multi-party transaction architecture demands multi-point integration.
- Closing-wire BEC fraud
- Elder real estate stripping
- Remote Online Notarization
- Mortgage origination signing
- Reverse mortgage origination
- Foreclosure rescue protection
All five categories, side-by-side.
A reference view for the visitor who's evaluating multiple categories at once — typically a platform engineer or a CRO weighing where to integrate first.
Sarah, 67
Margaret, 81
scope-bound delegation
Marcus
Sarah & Mark
Same primitive, shared edges.
The categories aren't independent silos. Six natural cross-pattern connections describe how integrations in one category compose with integrations in another. Most design partners eventually run more than one.
Two ways to find your starting point.
Most visitors arrive knowing their industry or knowing the threat they're trying to address. Either entry point leads to the same sub-pages — routed by what's most familiar.
By industry
What kind of organization are you?
- Bank, credit union, payment processor Banking
- Broker-dealer, RIA, family office, trust Wealth
- AI platform, agent framework, fintech building agents Agentic
- Wallet provider, exchange, MPC custodian, smart-contract wallet Crypto
- Title company, mortgage lender, RON platform, real estate brokerage Real Estate
By threat
What pattern of loss are you trying to address?
- Authorized push payment fraud, coerced wire transfers Banking
- Elder financial exploitation, undue influence, Reg BI gaps Wealth
- Prompt injection, scope creep, agent-credential theft Agentic
- Wrench attacks, pig-butchering, drainer approvals Crypto
- Closing-wire BEC, coerced quitclaim deeds, asset stripping Real Estate
Not seeing your category? It may qualify under the same framework. Write us at thesis@rtscale.ai with a description of the transaction class.
One demo. Your scenario. The category that fits.
The 30-minute demo starts from your specific use case — not a generic walkthrough. Whether you're integrating at a wire-authorization surface, a CRM, an agent SDK, a wallet signing flow, or a title closing system, we'll show you exactly how the signature primitive applies to the moments in your stack that matter most.