Roadmap
What is available, what is in the works, and what comes next
Float is pre-launch, and nothing is open for developer testing yet. This page shows where each part of the platform stands. Anything marked 🟡 is coming soon.
Platform status#
| Area | 🟢 Available now | 🟡 Coming soon |
|---|---|---|
| Access | Partner credentials issued directly by the Float team | Self-serve access and sign-up |
| Businesses | Registering and linking businesses, protected identifiers, wallet-based identity | n/a |
| Credit assessments | The full assessment process, including information requests and result handling | The production assessment engine and aggregate eligibility checks |
| Risk bands | Bands drawn from a versioned taxonomy, with expiry | The final band taxonomy |
| Events & notifications | An ordered event feed and signed notifications with automatic retries | Self-serve notification management |
| Verifiable assessments | Fingerprints, batching and proofs, with private detail kept by the owning partner | On-chain anchoring and revocation |
| Documents | Encrypted handling and forwarding | Secure document storage |
| Invoices & repayments | Recording invoices, tracking repayments and overdue status, collection, and Float's own on-chain verification | Automatic matching of invoice repayments seen on-chain |
| Credit lines | Credit ceilings, facilities, usage, live limits, settlements and on-chain observation | Faster on-chain indexing at scale |
| Reputation | Shared with consent, drawn only from Float-verified evidence | Reputation bands |
On-chain observation is available but switched on per environment. Where it is off, repayments are marked as not verifiable and reputation stays empty. Today it is limited to Solana devnet.
In the works#
Coming soon, roughly in order.
A portal where services sign up, call the Float API and see how many of their customers are likely eligible for credit, and why. A deeper, individual assessment follows once a customer accepts the terms.
Publish verification values on Solana, and revoke them when an assessment is withdrawn.
Secure storage with malware scanning and retention for the documents partners submit.
Delivery history in the dashboard, and the ability to resend a notification.
Matching repayments seen on-chain to the right invoice, using each invoice's repayment reference.
Faster, real-time tracking of on-chain activity, backed by a mainnet provider.
Confirming how failed settlement pulls look on-chain, once real examples are available.
A grace window, revocation while usage is outstanding, and scaling by amount.
A final set of fields, agreed with the team building the assessment engine.
Deciding the bands and which cross-partner evidence to share.
Recovery after default, disputes and restructuring.
A full technical reference, published once the API is finalized.
Under review#
| Item | Status today |
|---|---|
| Double-financing detection | The invoice fingerprint is recorded, and the detection itself comes later |
| Production document retention | A legal and compliance decision, and the policy can be configured once it is made |
| Usage-history format | An open format until the final fields are agreed |
| Final risk band taxonomy | The current taxonomy is a placeholder |
Later#
Platform capabilities
- Cancelling an assessment that is in progress
- Lists of past assessments and invoices, if partners ask
- Editing a business's details after it is created
Self-serve & security
- Self-serve access and notifications through a dashboard
- Standard machine-to-machine sign-in
- Consent granted directly by a customer's wallet, rather than attested by the partner
Operations
- Platform metrics and alert routing
- A health check for background processing