Stop-loss
Define a supported conditional sale with the relevant trigger, quantity, expiry and execution protection.
Conditional orders & recurring investing
Support intended stop-loss, take-profit and recurring purchase journeys with defined customer instructions, limits and cancellation paths.
Define a supported conditional sale with the relevant trigger, quantity, expiry and execution protection.
Set a supported target condition for a sale, subject to the provider’s trigger and execution rules.
Create a cancellable, bounded schedule for supported purchases, with the necessary funding and execution authority.
Select the supported asset, quantity or amount, timing or trigger, and applicable limits.
Explain authority, costs, expiry, cancellation and the conditions that can prevent execution.
Record the bounded instruction under the supported provider model.
Show active, cancelled, expired, skipped and executed states clearly.
Provider availability, liquidity, prices and the accepted instruction limits determine whether execution can complete.
Recurring purchases need matched funding within their accepted execution window.
The intended recurring model skips late cycles rather than automatically catching them up.
A little more detail
The practical details behind the intended offering.
No. These are intended capabilities. Provider fit, execution authority, funding and rollout scope must be agreed and verified.
No. A trigger is not a guaranteed fill. Provider execution conditions and the accepted protections apply.
The intended experience includes a cancellation path. The effective cancellation outcome must be confirmed against the provider state, including any action already in progress.
A conversation about your bank
Explore the products, responsibilities and integration path that fit your bank.