Visible routing rules
Does not present the selected bank or rail as a black box; it explains the balance, reserve, limit, time, speed and cost sequence behind the recommendation.
Separation of intent and movement
A request received through Telegram or another channel creates a payment intent for verification; it never initiates money movement by itself.
Controlled multi-bank capacity
Bank activity, supported rails, transaction/daily limits and minimum reserves are evaluated together to make account capacity visible.
Human-approved consequential threshold
Ambiguous recipient, amount, account or rule context is routed to review instead of being guessed for the sake of speed.
Customer-stated intent
Account and institution conditions
Limit, eligibility and time context
Approval and decision record
Evaluate financial options without sacrificing authority and responsibility boundaries for speed.
Customer-stated intent
Account and institution conditions
Limit, eligibility and time context
Approval and decision record
The system underneath the interface.
Smart Finance Route separates financial intent, validation, routing recommendation, human approval and provider execution into distinct trust domains. The rules engine operates only on versioned bank conditions and authorized account data; a recommendation record is technically separate from money movement.
Intent ingestion
Authorized channel, webhook signature and unique update identity are validated before amount, recipient and IBAN become a structured record.
Versioned rules engine
Bank activity, rail support, available balance, minimum reserve, transaction/daily caps, speed, cost and priority execute in a defined evaluation order.
Review state
The request enters an explicit state such as pending_review; authorized users see the recommended route, eliminated options and rationale together.
Secure data boundary
Sensitive fields such as IBAN are encrypted at rest; bank passwords and OTPs never enter application source or browser storage.
Provider adapter
Live execution occurs only through customer authorization and licensed bank/open-banking flows, with results tracked as separate transaction and notification records.
Cross-cutting contracts that make the architecture trustworthy
- Signed webhook and idempotent updates
- Encrypted sensitive financial data
- Versioned explainable rule evaluation
- Maker–checker human approval
- Separation of recommendation and money movement
The system does not execute automatically before real bank rules and account authority are verified. Receiving a message, recommending a route and moving money are three separate steps; the consequential final step requires customer authorization, provider verification and human approval.
We explicitly design where the system must stop.
The system ranks options and explains why; it separates recommendation from money movement and leaves final approval with a person.
Operational need
When financial options are evaluated across separate channels, decision rationale, authority boundaries and human approval can become unclear.
The Corixo approach
Smart Finance Route separates information collection, option evaluation and human approval into a controlled decision-system approach.
The goal is not to create more screens. It is to form the right decision inside a more visible, explainable system with clear responsibility.
Intended value
More explainable options, clearer authority boundaries and preserved human control at consequential steps.
Questions we address
- In what order should financial options be evaluated?
- Where should automation stop and request human approval?
- How should decision rationale be recorded?