FxTrade
The planned Flowesome trading platform: place an order, follow its execution and inspect the evidence of its treatment and settlement.
For traders, desks and institutions within a first market and user profile that remain to be defined.
FxTrade
Follow an order from instruction to settlement
FxTrade is intended as a complete trading product. A first useful scope must define its market, order types, execution and settlement, together with the required access, liquidity and integrations.
Illustrative product flow
- 1Choose a supported market and review its rules and permissions.
- 2Submit an order with explicit price, quantity, expiry and authority.
- 3Follow the execution observations supplied by the market integration.
- 4Inspect fills and refusals separately from settlement and external delivery.
- 5Reconcile unresolved outcomes using the evidence and procedures of that market.
Market access
Identify supported instruments, venues and participant permissions for a defined market.
Orders
Make side, size, price conditions, expiry and authorization visible before submission.
Execution
Explain observed fills, partial fills, refusals and ordering decisions within the selected execution model.
Settlement and records
Show settlement evidence separately from fills, with records useful to the user and relevant operations teams.
What FxTrade is designed to address
The problem
An order, a fill and a settled position are different facts. Their records can cross venues, operators and custodians.
A useful trading interface must explain these differences while meeting market access, liquidity, execution and operational requirements.
The Flowesome answer
FxTrade is designed to connect the trading journey to explicit authority and inspectable execution and settlement evidence.
Ordering and extraction-resistance designs require their own defined assumptions and evaluation. A product blueprint alone does not establish fair execution or a non-extraction guarantee.
An order and a settled trade are different facts
These design distinctions are evaluated against a particular market profile; they are not automatic stages or an executed demonstration.
- 1Declared
- The order states its conditions and authorization.
- 2Ordered
- The applicable rules determine its position and treatment.
- 3Filled
- Execution evidence supports a full or partial fill, or a refusal.
- 4Settled
- The relevant settlement system supplies its own evidence and limits.
- 5Delivered
- An external custodian or rail requires a separate observation; a fill does not establish delivery.
Trading capabilities under design
The FxChain capabilities this product is designed to use. They are shared, not owned: the same capability can serve other Flowesome products and third-party applications.
Constrained orders
Express order conditions and delegated authority before execution.
Ordering evidence
Make the applicable ordering rules and observed conflicts inspectable.
Execution records
Associate fills, partial fills and refusals with their supporting observations.
Settlement views
Keep market execution, protocol finality and external delivery distinct.
Where it sits, and why that matters
FxTrade follows FxWallet in the proposed presentation of the application family, before FxPay and FxBank.
Trade before Pay is a product hypothesis. Delivery priority depends on a defined market, identifiable users, liquidity, settlement and integration dependencies. Shared payment capabilities may be needed before the FxPay product ships.
Products
Foundation
FxChainWhat is real, stated plainly
Proven today
- Published product direction and blueprint
In development
- No operational market integration is established by this page
Later gates
- A defined initial trading market and user journey
- Execution, settlement and institutional records within that profile
Not claimed
- A trading service, order book, listings or market volume
- Liquidity providers or live market data
- Regulatory authorization or proven extraction resistance
Proven today, or practised on the lineIn development / qualifiedDirection: planned or researchLater gateNot claimed
Security and authority boundaries
Conditions and responsibilities that must hold for the applicable product or protocol profile.
- The first market must identify its participants, rules, access model and applicable obligations.
- Execution, settlement and custody dependencies require their own qualification.
- Neither a protocol property nor a signed order establishes every property of the complete trading product.
Gates, not dates
- 01
First market definition
PlannedSelect a bounded market, target users and the execution, settlement and liquidity model.
- 02
Qualified prototype
ReservedExercise the chosen market and integrations with inspectable outcomes.
- 03
Public trading service
ReservedDepends on product, operational and applicable regulatory requirements.
Explore the family
Discuss a workflow about FxTrade.
info@flowesome.com - we answer with what is provable today and what is staged for tomorrow.