Skip to main content
When positions in your users’ Safes drift from the target allocations defined by their Basket, Blend creates a flow plan. Flow plans are how the system proposes and executes rebalances. You review and approve them in the admin portal.
Flow plans are scoped to your Account Types, not to Baskets. You manage flow plans for the accounts your neobank operates. Risk Architects define the strategy. You decide when to act on drift.

​
How It Works

1

Drift detection

Blend monitors all accounts under your Account Types. When a position drifts from its target allocation beyond the configured threshold, a flow plan is created with status PENDING_APPROVAL.Each flow plan includes a drift snapshot: the current vs. target allocation at the time of detection, plus the total drift balance in USD.
2

Review

Pending flow plans appear in your admin portal under the Account Type’s flow plans tab. For each plan, you can see:
  • The Safe address and user address
  • The total drift balance (how far off-target the position is, in USD)
  • The number of transfer nodes (individual asset movements needed)
  • When the plan was created
Flow plans can be automatically removed if market conditions change and the position returns to sync before you review it.
3

Approve or cancel

After reviewing, you can:
  • Approve: Moves the plan to QUEUED status. A solver picks it up and computes the optimal route.
  • Cancel: Dismisses the plan. The position stays at its current allocation.
You can cancel a flow plan from either PENDING_APPROVAL or QUEUED status.
4

Execution pipeline

After approval, the flow plan moves through an automated pipeline:
  1. QUEUED - Waiting for a solver to pick it up
  2. SOLVING - The solver computes the best route across chains and protocols
  3. EXECUTING - On-chain transactions are in progress
  4. SETTLED - Done. The transaction is recorded for auditability.
If execution fails, the plan moves to FAILED.

​
Flow Plan States

StatusDescriptionCan cancel?
PENDING_APPROVALAwaiting your review. May be auto-removed if drift resolves.Yes
QUEUEDApproved, waiting for solver.Yes
SOLVINGSolver is computing the optimal route.No
EXECUTINGOn-chain transactions in progress.No
SETTLEDRebalance complete. Archived with transaction details.No
FAILEDExecution failed. Can be retried.No
CANCELLEDDismissed. Archived.No

​
Batch Operations

For Account Types with many accounts, you can batch-approve all pending flow plans at once. This moves every PENDING_APPROVAL plan for that Account Type to QUEUED. Use batch approve when you trust the drift detection and want to rebalance all accounts together.
Each flow plan execution incurs a fee. Batch-approving a large number of plans triggers fees for each one. Review the pending count before confirming.

​
What Flow Plans Contain

Each flow plan includes:
FieldDescription
Drift snapshotA point-in-time record of how each position has drifted from its target allocation
Total drift balanceThe total deviation in USD across all positions
Transfer nodesThe individual asset movements the solver will execute (source chain, destination chain, token, amount)
Account infoThe Safe address and user address for the affected account

​
Next Steps

Account Types

Create and manage your product offerings.

Deposit & Withdraw

Implement funding flows with the SDK.

Integration Fees

Understand the fee structure for neobanks.

Risk Architects

Learn how Risk Architects define the strategies your Account Types use.
Last modified on March 20, 2026