FxBank
The Flowesome banking platform under research, with a long-term neobank ambition: bring account services, transfers and financial oversight into a clear user journey.
For people and businesses whose precise services, jurisdictions and operating arrangements remain to be defined.
FxBank
A banking experience with explicit responsibilities
The product vision includes accounts, payments and financial oversight. Its actual service scope depends on the entities, partners, responsibilities and permissions required for each offered activity.
Illustrative product flow
- 1Identify the service, responsible entity and applicable user rights.
- 2Review the supported account and rail arrangements.
- 3Authorize a supported operation within its defined scope.
- 4Follow observed processing, settlement and external delivery separately.
- 5Use the responsible provider and evidence to resolve questions or interruptions.
Accounts and balances
Explain what a user holds, which entity provides it and what rights and limits apply.
Transfers and payments
Make recipient, currency, fees, timing and the applicable external rail visible.
Financial oversight
Bring transaction records, permissions and unresolved operations into one understandable view.
Service and recovery
Identify who handles reconciliation, disputes and interrupted operations, with explicit escalation paths.
What FxBank is designed to address
The problem
A banking interface can combine records from several institutions and rails. Users need to understand what each balance or payment record actually represents.
Technical attestations, contractual rights, operational availability and the right to provide a regulated service require different evidence.
The Flowesome answer
FxBank explores a complete banking product with visible responsibilities and evidence for the services a user would rely on.
Shared protocol controls and rail observations could support that journey. They do not themselves establish deposits, solvency, a license or a right to offer banking services.
A technical record and a banking right are different facts
These research distinctions help define the product; they do not establish a current banking relationship.
- 1Mandate
- Who may perform the operation, within which limits and duration?
- 2Provider observation
- What has a named provider actually reported, and when?
- 3User right
- Which agreement or instrument establishes the relevant claim or entitlement?
- 4Outstanding obligation
- Who remains responsible for delivery, reconciliation or a dispute?
- 5Permission to operate
- Which entity has the required permissions for the particular service and jurisdiction?
Capabilities considered for the banking platform
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.
Account and rail evidence
Associate external records with their issuer, purpose, observation time and scope.
Dependency observations
Inspect the specific condition reported by an attestation without treating it as proof of solvency or future availability.
Reconciliation
Distinguish protocol records from external delivery and the obligations still outstanding.
Operational responsibility
Make permissions, provider duties and supported recovery procedures explicit.
Where it sits, and why that matters
FxBank is the later banking direction in the proposed FxWallet, FxTrade, FxPay, FxBank presentation. Its ambition remains a complete banking platform.
Connections to financial providers and external rails may be needed by other products earlier. Those shared integrations do not have to wait for the FxBank product, and each has its own authorization and qualification.
Products
Foundation
FxChainWhat is real, stated plainly
Proven today
- Published banking-platform vision and research direction
In development
- No operational banking integration is established by this page
Later gates
- A precise initial service and responsibility model
- Evaluation of provider and rail requirements
Not claimed
- Banking status, a license or regulatory authorization
- Deposits, customer accounts or live banking services
- Established banking partners or guaranteed service availability
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 legal nature of accounts, balances and services must be explicit for the actual arrangement.
- A health receipt states a bounded observation; it is not automatically solvency, a custody right or future availability.
- Fallback procedures depend on the rail and operating agreement; no permission-free recovery is promised.
- A service release requires its own operational and applicable regulatory prerequisites.
Gates, not dates
- 01
Service research
ResearchDefine users, account services, rail requirements and responsible entities.
- 02
Bounded evaluation
PlannedAssess particular services and integrations with explicit assumptions and limits.
- 03
Provider arrangements
ReservedEstablish the contracts, responsibilities and permissions required by the chosen model.
- 04
Service release
ReservedOnly within the actual qualified and authorized scope.
Explore the family
Discuss a workflow about FxBank.
info@flowesome.com - we answer with what is provable today and what is staged for tomorrow.