Balances should
empty themselves.

Two automations, two shapes of discipline

OrbChain gives you two standing-movement primitives, and the difference is what triggers them:

• Auto-payout rules trigger on amount. "When my USDT_TRC20 balance reaches 500, send it all to this address." The moment the threshold is crossed, the full balance goes out — your exposure is capped at the threshold, permanently, no matter how good sales get. This is the risk-management shape: the rule is really a ceiling on how much of your money can ever be sitting here.
• Payout schedules trigger on time. "Every day (or week — anywhere from hourly to monthly), if the balance is above a floor, sweep it to this address." This is the bookkeeping shape: predictable arrival times, one on-chain transaction per period regardless of how many payments came in, and a minimum-amount floor so quiet days don't waste a network fee on dust.

Both are per-coin and configured in the dashboard in under a minute. Run them together: a schedule for rhythm, thresholds as the tripwire for unexpectedly good days.

What "automatic" means when money moves

Automation that moves funds has to fail conservatively, so the boring details are the important ones:

• Every automatic movement is an ordinary payout — it appears in your payout history with a track_id and a tx hash, and fires the same signed payout.confirmed / payout.failed webhooks as an API call. There is no separate, less-visible pipe for automated money.
• Failures re-credit and back off. If a broadcast fails, the balance is restored atomically and the rule cools down before retrying — no rapid-fire retry loop burning attempts against a temporarily broken destination.
• Idempotent by construction. Rule executions carry their own idempotency keys, so a worker restart can't double-send a sweep.
• Network fees come out of the swept amount, same as any payout — schedules with a sensible minimum floor keep the fee a rounding error rather than a percentage.

Composing a hands-off treasury

The pattern that falls out when you combine the pieces already on the platform: incoming payments auto-settle into your stablecoin, the stablecoin balance auto-pays to your hardware wallet at a threshold, and the only human action left in your entire money pipeline is spending it. For teams, the same rules drain into a treasury multisig; for the platform pattern, a schedule keeps the float you need for user withdrawals and sweeps the excess.

When manual is right

Honest boundary: if your payout destination changes often, or you're actively converting between coins before withdrawing, standing rules will fight you — automation wants stable destinations and a stable policy. Set the rules for the 95% steady-state flow and use the ordinary payout API or dashboard for the exceptions. The goal isn't zero manual payouts; it's that forgetting to withdraw is no longer a thing that can happen.