Finvoice

Finvoice tackles one of the most overlooked inefficiencies in global finance: small businesses sitting on unpaid invoices, unable to access the capital they're already owed — because traditional invoice factoring demands full transparency into their customer relationships. Handing over debtor names, payment histories, and financials to a bank or middleman is a dealbreaker for most SMBs. Finvoice eliminates that tradeoff entirely. The core innovation is a fully private invoice factoring pipeline built across two blockchains. Debtor identity is ECIES-encrypted client-side before anything touches a ledger. Credit scoring runs inside a Flare TEE (Trusted Execution Environment) — meaning an AI model evaluates the invoice using real debtor data, inside a cryptographic enclave, and the identity never escapes. What comes out is a signed, TEE-attested risk grade (A–D) and yield rate, minted as an Attestation NFT on Hedera. Funders see the grade. Nobody sees the debtor. The architecture is just as bold as the privacy model. There is no traditional database — zero Postgres, zero MongoDB. All application state lives on Hedera Consensus Service topics as encrypted append-only event logs, replayed into memory on startup. Invoices and receipts are tokenized as Hedera NFTs using pure @hashgraph/sdk. Debtors approve via a one-click PDF email link — no wallet, no blockchain knowledge required. Auth is handled by Dynamic.xyz, bridging EVM and Hedera wallets in a single session across Flare Coston2 and Hedera Testnet. Finvoice proves that real-world asset tokenization doesn't have to sacrifice privacy. The entire invoice lifecycle — creation, debtor approval, AI scoring, marketplace listing, funding, and settlement — runs with cryptographic guarantees at every step, on live deployed infrastructure, with zero traditional backend. It's a complete, production-grade DeFi primitive for a $3.5 trillion market that's never had a privacy-preserving alternative.

Hedera as a Zero-Infrastructure Backend Every piece of application state in Finvoice — invoice created, debtor approved, AI scored, funder invested, settlement complete — is written as an encrypted JSON message to a Hedera Consensus Service topic via TopicMessageSubmitTransaction. Debtor PII is ECIES-encrypted client-side before submission, so the public ledger only ever holds ciphertext. On startup, the server replays every message from both HCS topics to reconstruct a full in-memory state cache. That's the entire database layer — no Postgres, no MongoDB, no credentials, no schema migrations. Just append-only consensus messages on a public ledger, with auditability baked in by design. Tokenization runs entirely through @hashgraph/sdk with zero Solidity on Hedera. Two NFT collections power the product: Attestation NFTs carry the AI-verified risk grade and yield as on-chain metadata, and Receipt NFTs prove funder investment and are burned on settlement. All payment flows — advances to suppliers, returns to funders — move in HBAR via TransferTransaction. Flare TEE for Private AI Scoring The hardest product problem was this: how do you generate a trusted AI credit score without revealing who the debtor is? Flare's TEE Extensions are the answer. A single Solidity contract on Coston2 relays typed instructions (CREATE, APPROVE, SCORE) to our registered TEE Extension (ID 251, PRODUCTION) via ITeeRegistryV1.requestInstruction(). Inside Flare Confidential Compute, the handler decrypts the debtor PII using the TEE node's /decrypt endpoint, feeds the full invoice context to GPT-4o-mini, receives a structured JSON score (grade A–D, discount basis points, reasoning), hashes the result with keccak256, and signs it via /sign using the TEE's attested key. A deterministic fallback scorer handles OpenAI downtime by evaluating payment history, jurisdiction risk, and maturity duration locally. The debtor's identity and AI reasoning exist only in enclave memory — only the signed grade and yield leave the TEE. Dynamic.xyz for Seamless Multi-Chain Auth Three user types (suppliers, debtors, funders) interacting across two chains (Flare and Hedera) would normally require separate auth flows. Dynamic.xyz collapses this into a single session — DynamicContextProvider is configured with custom Hedera Testnet network settings alongside EthereumWalletConnectors, so users connect once and interact with both chains without switching wallets or contexts. Supplier identity is resolved at invoice creation, wallet-specific dashboard data is fetched via useUserWallets, and marketplace funding is gated behind the same auth check.