Auto-withdrawals
A rule that sweeps settled funds to your own address on a schedule you set. Configured in the dashboard under 2FA — never over the API-key surface.
How a rule works
An auto-withdrawal rule is defined per asset: a destination address, a minimum threshold, and an interval. On each run, if the settled balance in that asset is at or above the threshold, the rule withdraws to the destination; if it isn't, the run does nothing and waits for the next interval.
| Setting | What it controls |
|---|---|
| Asset | Which balance the rule sweeps. One rule per asset. |
| Destination address | Where the funds go. Set under 2FA; changing it is a security event, not a config tweak. |
minThreshold | The balance below which a run is skipped — keeps you from paying a flat withdrawal fee on dust. |
intervalSeconds | How often the rule evaluates. |
Only settled funds move
Rules sweep the safe bucket only — funds from payments and deposits that reached Success / confirmed. Money credited at Accepted is spendable in your product but not withdrawable — it becomes withdrawable at Success, when the payment is irreversible. → Settlement & finality
What it costs
Each withdrawal carries a flat network-dependent fee, quoted in the dashboard before you confirm the rule. Set minThreshold high enough that the flat fee is a rounding error against the amount swept. → Fees & who pays what
Why there is no API endpoint for this
Movement of funds does not live on the API-key surface
There is no API-key endpoint for configuring or triggering withdrawals. Rules, destination addresses, and approvals are set in the dashboard under 2FA and role-based access. A leaked API key can read and create payments — it cannot move your money out. → Authentication
Runs are idempotent and logged
- A run either withdraws once or does nothing — a retried or overlapping evaluation never produces a double withdrawal.
- Every attempt is recorded with its outcome, so a rule that isn't firing tells you why: threshold not met, no settled balance, or a network-side failure.
- Withdrawals are visible alongside payments and deposits in the dashboard, attributable to the rule that produced them.
A rule that fits how you operate
- High-volume, thin margin: low interval, threshold well above the flat fee — funds don't accumulate, and the fee stays proportionally small.
- Low volume, large tickets: longer interval, higher threshold — one withdrawal per batch of orders.
- Treasury-controlled: no rule at all; withdraw manually in the dashboard when your finance process says so.
Next: Settlement & finality for what "settled" means · Going live checklist to set your rule before the first live payment.
Something unclear? payments@suward.com — we treat every integration question as a documentation defect.