Overview

What is Float

Float is a cross-platform credit infrastructure for service providers on Solana. It does three things:

Underwrites receivables

You submit an invoice or a credit line. Float returns an assessment.

Records obligations

After you finance, register the obligation. Repayments come from your reports or Float's chain observation.

Builds reputation

Portable business reputation, from evidence Float verifies independently.

Warning

Float is not a lender, pool, custodian or payment processor. It never disburses, holds, routes or moves funds. Your platform controls the capital and makes every financing decision.

flowchart LR
  B[Business] --> P[Partner platform]
  P --> F[Float]
  F --> U[Assessment]
  U --> D[Partner decides & finances]
  D -- "obligation + repayments" --> F
  F --> V[Float-verified evidence]
  V --> R[(Portable reputation)]

Two products, one platform#

Invoice financingAPI/RPC credit lines
You submitA receivableA credit-line request
After underwritingRegister an obligationOpen a credit facility with usage and settlements

Both share the same businesses, consent, underwriting lifecycle and reputation.

Partner-reported vs Float-verified#

Partner-reported

Everything you send about an obligation. Drives your bookkeeping. Never affects reputation.

Float-verified

What Float observes itself, on-chain. The only input to portable reputation.

See Architecture for the full rule.

The partner journey#

  1. Create or link the business

    Register the business you serve. If another partner has already verified the same wallet, you're linked to the same business. That is the only way two partners share an identity.

  2. Record consent (optional)

    Without the business's consent, reputation can't be read.

  3. Submit for underwriting

    Underwriting is asynchronous. You get an immediate acknowledgement and the result follows.

  4. Answer information requests

    If more is needed, provide the data or documents requested and the request resumes.

  5. Read the assessment

    You get a risk band, confidence, verification levels and reason codes. No approve/decline and no price. That decision is yours.

  6. Finance, then register the obligation

    Pay on your own rails, then register the obligation. Float gives you a repayment reference for the payer to include in the repayment transaction.

  7. Report repayments or a default

    These update your bookkeeping. Float verifies on-chain only where chain observation is enabled.

  8. Read portable reputation

    A summary of Float-verified outcomes. Never amounts, partners or invoices.

Environments and access#

Warning

Float is pre-launch. Every environment Float runs today is staging, whatever it is called in infrastructure or configuration. Names are not a signal of real-money readiness. Don't treat anything here as production-ready.

Your API key decides the environment, and test and live data never mix.

Test keys (fk_test_…)Live keys (fk_live_…)
UnderwritingSandbox. Mock results, not real assessmentsNot available. Requests return 503
KYBSandbox. Mock resultsNot available. Requests return 503
Chain observationSolana devnetNot enabled
Document uploadsNot available yet (503)Not available yet (503)

Float never moves funds in either environment. See the Roadmap for the full list of what is real, and the sandbox outcomes you can trigger with a test key.

Getting credentials. There is no self-serve signup yet. To get partner credentials today, contact the Float team directly.

Integration at a glance#

Authentication and environments

Requests are authenticated with a bearer API key. The key's prefix selects the environment.

Idempotency

Send an idempotency key on create requests so retries never duplicate. Replaying a key with the same body returns the original result; reusing it with a different body is rejected.

Events

Partners can poll an ordered event feed or receive signed webhooks carrying the same events.

Money and IDs

Money is an integer in minor units, sent as a string with a currency. IDs are prefixed (biz_, uwr_, obl_) and stable forever.

Exact endpoints are on hold while the API is finalized. See API Reference.