escrow-state-guard

Escrow state machine enforcement prevents invalid state transitions by validating that financial transactions follow a predefined sequence like PENDING to FUNDED to RELEASED. This skill intercepts modifications to escrow subsystems, ensuring strict operational invariants are met before any state change occurs.

To verify platform fee calculations including surge premiums during escrow transactions, you must validate the fee logic against the current state. This skill enforces accurate calculation of platform fees and surge premiums before modifications, preventing undercharging and revenue loss.

The best way to prevent fraud in a Stripe escrow subsystem is to enforce mandatory pre-change verification for all state modifications. This skill validates state transitions, KYC compliance, and fee calculations to maintain strict operational invariants and secure financial transactions.

You need state machine enforcement for financial transaction processing to prevent regulatory exposure and accidental payouts to unverified accounts. By validating KYC compliance and state transitions before modifications, this skill ensures adherence to financial regulations and prevents revenue loss.

You should use a verification skill for escrow service modifications whenever altering code that handles real money, such as EscrowService or DisputeService. It enforces pre-change checklist compliance, ensuring KYC verification and fee accuracy before any code changes are applied.