Paytivo
Paytivo turns the conversations where business happens into the workflow that gets it paid. AI identifies agreed work in client chats and prepares invoices for review. Freelancers can send invoices, track outstanding balances, and connect billing to accounting—all in one workspace.
Our product vision brings two ways to pay into that workflow: PayPal checkout and Web3 PYUSD payments powered by StealthOS, with private transfers that hide internal amounts and recipient details on-chain.
Inspiration
A freelancer's agreement often lives in a conversation, while the invoice, payment link, follow-up and accounting record live in separate tools. Paytivo connects those steps so the person doing the work can review the agreement once and carry it through billing.
What it does
Start with a natural-language description or selected client conversation. Paytivo prepares an editable invoice draft, lets the freelancer review the amount and terms, and delivers the invoice to the customer's Paytivo ID. The workspace shows sent and received invoices and outstanding balances. The invoice checkout brings PayPal and Web3 into the same customer journey.
AI assists the freelancer; it does not silently send invoices or approve payments. Connected accounting export is an explicit action scoped to the merchant's account.
How we built it
The application uses Next.js, React, TypeScript and Tailwind, with Supabase authentication and account-scoped invoice storage. Qwen on Groq converts work descriptions into structured drafts. The interface identifies the provider that actually generated each draft and clearly labels a local-parser fallback.
PayPal Orders v2 handles Sandbox order creation, buyer approval and capture. Server-side checks verify the order, amount, currency and status before recording a separately labeled sandbox-paid result. Durable request identifiers and reconciliation protect against duplicate requests and interrupted checkout.
The hosted Web3 integration uses StealthOS proving technology, browser-generated zero-knowledge proofs, a Paytivo-owned pool on Base Sepolia and a relayer. Commitments and nullifiers allow the contract to verify internal transfers without exposing readable internal amounts or recipient details. Funding transactions and timing remain public and may be correlated.
The app runs on Render. The public repository contains Paytivo-owned application and integration source under MIT. Separately licensed StealthOS SDK/proving assets, upstream contracts and the adapted TG Boss device connector remain private and are excluded from that release. The core invoice, AI and PayPal application builds independently.
Current implementation scope
The submitted PayPal integration uses Sandbox and virtual funds. The hosted Web3 flow uses a custom valueless test token on Base Sepolia, not PayPal-issued PYUSD. It verifies private internal transfers, but both participants' notes remain in the payer's browser: it does not yet deliver funds to a merchant or settle the merchant invoice. Production PYUSD settlement is the next integration milestone.
The chat-candidate scan uses conservative matching before review and AI drafting. QuickBooks export is implemented, with a full external accounting write still awaiting independent verification. Optional 0G integrations are present in source but are not configured in this hosted submission.
Challenges and what we learned
The difficult part is preserving the meaning of every state across systems. A generated draft is not an approved invoice; an approved order is not a captured payment; and a verified private transfer is not automatically merchant settlement.
We built explicit review steps, verified payment receipts, idempotent retries and resumable Web3 attempts around those boundaries. Privacy also requires honest treatment of metadata: hiding internal transfer fields does not hide public funding activity.
Accomplishments
We connected natural-language drafting, invoice delivery, a merchant/customer workspace, PayPal checkout and a working on-chain privacy integration in one product. Live Qwen drafting and both judge accounts were verified on November 11. The latest invoice-linked PayPal test created a buyer approval order successfully; standalone Sandbox capture has also been demonstrated. Fresh relayed Base Sepolia private transfers were verified on-chain.
What's next
Complete merchant-controlled private receipt delivery and verified PYUSD settlement, validate the full accounting export journey, and extend conversation-to-invoice automation with careful review and permissions. The aim is one continuous workflow from the agreement to the payment and accounting record.
Built With
- ethers.js
- groq
- next.js
- paypal
- qwen
- react
- render
- solidity
- supabase
- tailwind-css
- typescript