A swap executes under the conditions of a transaction you approve now. An automated order adds a later decision: execute when a price or schedule condition is met. Understand where its funds wait, who triggers execution and how you cancel the unfinished portion.
Define the condition and the desired outcome
A buy-below order asks for execution when a reference price falls below a threshold. A sell-above order does the opposite. A stop-loss request reacts to an unfavorable price move. The condition tells the service when to act; the execution rules determine what exchange it can accept.
A strict minimum output can cause execution to fail when liquidity is insufficient. A wider tolerance can permit a worse fill. Calling an order a stop loss does not establish a guaranteed exit price during a jump, outage or thin market.
A schedule-based DCA divides an input budget across several rounds. A price-conditional schedule also requires a price to be inside a selected range. Check whether an unfilled round waits, retries or expires under that product's policy.
Identify the current custody model
Jupiter Trigger V2 uses a Privy-managed custodial vault shared by the wallet's orders. Its order records are offchain, with swaps executed when the conditions trigger. This differs from older descriptions that place each pending order in its own onchain PDA.
Creating an order therefore involves both a deposit and a service-side order record. Closing a browser tab or disconnecting the wallet does not retrieve the deposit or cancel the existing schedule. Preserve the order ID, vault information and deposit signature.
Use the documentation for the exact order generation you are using. A wallet integration can expose a different route from an old tutorial with the same button name.
Separate a USD trigger from a quoted exchange rate
In the V2 price-order model, the condition uses a token's USD price. At execution, the route exchanges the actual input and output assets under its permitted bounds. A price crossing alone does not promise a fixed quantity of output tokens.
Suppose a fictional instruction sells one token when its reference price reaches 150 USD. If the output is another volatile token, that output token's price also affects the amount received. Even a stablecoin output needs the route, fees and configured tolerance to determine the actual result.
Partial fills add another accounting dimension. Record input spent, output received and input still available. The original order size is not the amount already executed.
Equal spending buys unequal quantities
Work through a recurring purchase
Use a fee-free teaching schedule with 300 USDC split into three 100-USDC rounds. Execution prices of 100, 125 and 80 USDC per SOL produce 1, 0.8 and 1.25 SOL. Total output is 3.05 SOL, and the average purchase price is about 98.36 USDC per SOL.
The simple average of the three prices is about 101.67. That is not the cost per SOL because each round spends the same money but receives a different quantity. For actual orders, use net quantities and include charges in the unit you are measuring.
DCA spreads execution across observations. It does not make the final token value predictable. Three rising prices could leave you with less output than one earlier purchase; three falling prices produce another result.
Cancel the remaining commitment and verify the funds
For a price order, cancellation and retrieval can require a signed withdrawal flow. Expiration can leave funds in the vault rather than return them to the wallet. For V2 DCA, cancellation returns the unfilled remainder under its supported flow; rounds already executed remain completed swaps.
If two rounds in the 300-USDC example completed, reconcile their 200-USDC input and received SOL separately from the remaining 100 USDC. Confirm both the order status and the actual withdrawal transaction.
A pending cancellation can race with an eligible execution. Read final fills and transfers before deciding how much returned. A service status, signed request and accepted transaction answer different parts of that investigation.
Keep yield options visible as separate exposure
Some recurring products can lend idle input while waiting. If you enable that option, the order also depends on the lending receipt, its liquidity and its exit rules. An extra yield label changes the position you hold between rounds.
Choose the option only after reading that additional mechanism. For an ordinary schedule, a complete record still fits a short ledger: deposited input, completed fills, fees, unfilled balance and returned funds.
Sources and documentation
- Jupiter: Trigger V2 order model
- Jupiter: USD triggers and execution floors
- Jupiter: Trigger V2 execution and reconciliation
- Jupiter: scheduled and conditional DCA
- Jupiter: order cancellation and withdrawals
- Jupiter: cancel DCA and withdraw the remainder
Found an error or an outdated detail? Send a correction.
