Terminal Wrapper Pattern

Problem

Revnets and other projects often need extended payment functionality that can't be achieved through ruleset data hooks alone. Common needs include:

• Dynamic splits specified at payment time
• Token interception and redirection
• Atomic multi-step operations (pay + distribute)
• Client-specific features without breaking permissionless access

Context / Trigger Conditions

Apply this pattern when:

• Building payment flows that need dynamic configuration
• Working with revnets where ruleset hooks can't be edited
• Need to bundle multiple operations atomically
• Want to intercept tokens for further processing
• Implementing "pay and do X" flows