NoteBuilt to a hackathon deadline and deployed to test networks. The finance and KYC adapters run against mock services, so the flow is complete end to end without touching a real ledger.
RECEIVABLE
Tokenised Invoice Financing by Windson Infotech, built on Solidity, Foundry, Hedera over 3 weeks.
A small business waits 30 to 90 days to be paid for work it has already done, and the financing that bridges that gap is slow because nobody downstream can cheaply verify the invoice is real. Putting invoices on a chain solves the transfer and solves none of the trust: a token representing a fake invoice is a fake invoice with extra steps and better liquidity.
Receivable puts verification before tokenisation. An adapter service checks an invoice against accounting and KYC providers behind a single API key, and only a verified receivable is minted — the contract is never asked to trust the submitter. A Chainlink CRE workflow triggers those off-chain checks from a signed request, keeping them outside the web application's trust boundary. Contracts are written and tested with Foundry and deployed to both Sepolia and Hedera, so settlement is not tied to one chain's fees or finality. The whole thing is a pnpm and Turbo monorepo, and the front end renders explicit “not configured” states instead of blank screens when a key is missing, so it stays demonstrable.
Verification first, tokenisation second — the order that decides whether any of the rest is worth anything.
SYSTEM DELIVERABLES
What we actually built, and why each piece had to exist — the scope as it shipped.
Verified Receivable Contracts
Solidity written and tested under Foundry, with deployment artefacts maintained for both Sepolia and Hedera rather than one chain treated as the default.
Verification Adapter
A service front-ending finance and KYC providers behind one API key, so minting is gated on a check the contract itself could never perform.
Chainlink CRE Workflow
Off-chain checks triggered from a signed request, deliberately outside the web application's trust boundary.
Monorepo And Deploy Path
pnpm workspaces under Turbo, with a deploy configuration that reaches contract artefacts four levels above the web app — the unglamorous part that decides whether it ships.
