Skip to main content
Settlement rules define when a batch of transfers settles — by balance threshold, time of day, event, or manual request. Rules run per wallet, so you can have different cadences for different merchants, agent wallets, or business lines.

Why rules matter

Without rules, settlement follows the tenant’s default window cadence. With rules, you can:
  • Sweep balances above a threshold automatically
  • Pay out merchants only once a certain volume accumulates (amortize rail fees)
  • Trigger on events — close day’s books at midnight local time
  • Emergency settlements — force immediate settle during incidents

Rule anatomy

Create a rule

Trigger types

Rules with the same wallet but different triggers are evaluated in priority order (lower first). First matching rule wins.

Action types

List + inspect rules

Per-rule execution history:
Shows every time the rule fired, what it did, and any errors.

Update / disable

Disabling is reversible; deletion isn’t — DELETE removes the rule and its execution history.

Manual settlement

Bypass all rules and settle a wallet immediately:
Common during accounting period closes or incident response.

Common rule patterns

Daily merchant payout at 2am Eastern:
Sweep balance above reserve:
Settle after every 100 x402 payments:
Hold 10% for chargeback reserve (90-day release):

Endpoints

Interaction with windows

Rules and windows compose:
  • Windows define the maximum batching cadence
  • Rules can trigger settlement earlier than the window
  • Rules never delay past a window — windows are the ceiling
Example: window is “every 4 hours”, rule is “balance above $10k”. Settlement fires whichever triggers first.