Fantasmita Passport

Inspiration

Small businesses do not lack financial activity. They lack financial continuity.

An invoice lives in one tool, its payment in another, reimbursements arrive through chat, payroll runs from a spreadsheet, and financing requires starting from zero with another institution. This fragmentation is especially painful for international teams operating across currencies and borders.

I built Fantasmita Passport to turn that disconnected activity into a portable, privacy-preserving financial identity.

What it does

Fantasmita Passport is an agentic financial workspace for small businesses, international teams, and independent workers.

Its Magic Inbox turns emailed invoices, receipts, contracts, payment requests, and supporting documents into structured workflows. From one workspace, a business can:

Ingest accounts payable and receivable through the Magic Inbox Create, send, receive, and reconcile invoices Submit and approve receipt-backed reimbursements Prepare payroll and contractor payouts Settle international obligations using stablecoins Request working capital against eligible invoices Build a persistent financial passport from completed activity Reuse a Persona-verified identity across connected financial services Manage paid workspace subscriptions through Stripe Move between fiat and stablecoins through integrated on/off ramps

Instead of treating invoice factoring as a disconnected loan application, Fantasmita connects the financing request to the invoice, contract, counterparty, payment history, and supporting evidence already present in the workspace.

Every completed invoice, reimbursement, payroll cycle, settlement, and repayment contributes verifiable context to the Passport. Ordinary business operations progressively create reusable financial trust.

The knowledge entity graph

Underneath Fantasmita is a knowledge entity graph connecting people, companies, invoices, contracts, accounts, receipts, approvals, payments, and financial events.

The graph understands relationships: which contract produced an invoice, which customer owes it, which receipt supports a reimbursement, which policy applies, which payment settled an obligation, and which historical events support a financing claim.

Fantasmita is designed to connect with the financial systems businesses already use. Plaid, QuickBooks, Xero, and Conta Azul provide permissioned context for validating and reconciling bank activity, counterparties, invoices, ledger entries, expenses, and payroll obligations.

An invoice received through the Magic Inbox can be connected to a counterparty in QuickBooks, a payment observed through Plaid, and its corresponding accounting treatment in Xero or Conta Azul.

Reusable identity with Persona

Compliance should not force a user to repeat the same onboarding for every financial service.

Fantasmita integrates Persona as a reusable identity and verification layer across the workspace. Once an individual or business completes the appropriate verification, the resulting status can be permissioned and reused across invoicing, factoring, payroll, reimbursements, wallet operations, and fiat ramps without repeatedly collecting the same information.

Services consume the minimum verification outcome they require rather than receiving the user’s complete identity record. This reduces onboarding friction while keeping regulated actions behind consistent identity, KYB/KYC, and authorization checks.

Subscriptions and fiat access

Stripe subscriptions power the commercial layer of Fantasmita, allowing workspaces to activate and manage paid product access while keeping billing state connected to workspace permissions.

Integrated on/off ramps complete the movement between traditional and stablecoin financial systems. A verified user can fund a workspace from fiat, receive or hold stablecoins, execute international payments, and return funds to local rails from the same operating environment.

Persona verification is reused where a ramp or financial service requires it, so identity, subscription status, permissions, and transaction workflows remain coordinated rather than becoming separate onboarding silos.

Privacy-preserving verification

Fantasmita follows a verification-over-collection model.

External account credentials are not stored by Fantasmita. Sensitive source information is processed to produce the minimum verification result, attestation, or relationship required by a workflow. Where operational records must exist, Fantasmita minimizes retained information and applies workspace-scoped authorization.

Zero-knowledge proofs allow users and businesses to validate claims—such as account control, invoice eligibility, sufficient balance, completed payment, or satisfaction of a financing threshold—without exposing the complete private dataset behind them.

Privacy does not mean bypassing compliance. Fantasmita separates verification from disclosure: required conditions can be validated and risk controls enforced without indiscriminately exposing a user’s financial life.

Ghost Wallet and private international payments

International payments should not require exposing a company’s complete treasury position or commercial relationships.

Fantasmita’s Ghost Wallet provides a private execution layer for cross-border payments. A user can maintain a shielded balance and settle an international obligation without publicly linking every transaction to the broader operating balance or financial identity.

The knowledge graph can confirm that an obligation was satisfied while privacy proofs protect unrelated wallet activity, counterparties, treasury balances, and payment history. International commerce becomes private by default while preserving the evidence needed for legitimate compliance and auditing.

Voice-native operations

Fantasmita includes a real-time voice pipeline connected to the same permissioned tools and knowledge graph as the visual workspace.

A founder or finance operator can ask the agent to explain the Magic Inbox, identify overdue invoices, prepare a reimbursement, summarize payroll, assess whether an invoice may qualify for factoring, reconcile a payment, or prepare an international settlement.

The agent understands the request, retrieves the relevant entities, explains the proposed action, and prepares a reviewable workflow. Sensitive financial execution still requires the appropriate authorization and confirmation.

How it works

A supplier invoice can arrive through the Magic Inbox. GPT-5.6 identifies the supplier, amount, currency, due date, and supporting contract; connects the document to existing entities; checks for missing information and duplicates; and prepares the payable for approval.

For factoring, Fantasmita connects an accounts-receivable invoice to its customer, contract, terms, and payment history. It evaluates configured eligibility conditions, prepares an explainable offer, and monitors settlement and repayment. Outcomes update the Passport.

For reimbursements, the agent extracts the merchant, amount, date, currency, and category from a receipt, checks policy requirements, requests missing evidence, routes the claim for approval, and prepares the payout.

How I used Codex and GPT-5.6

Codex was not a one-time code generator. It became the engineering workspace through which I investigated existing modules, traced incomplete workflows, designed integrations, implemented changes, and verified end-to-end behavior.

I used GPT-5.6 and Codex across:

Passport and financial-entity modeling Magic Inbox ingestion and document classification The knowledge entity graph Plaid and accounting-system connectivity Persona identity reuse across financial services Stripe subscription and workspace-entitlement flows Fiat and stablecoin on/off-ramp orchestration Invoice creation, reconciliation, and settlement Invoice-factoring eligibility and lifecycle design Receipt-backed reimbursements Payroll and contractor payouts Voice-agent tools and authorization boundaries Zero-knowledge verification and private settlement Database schemas, failure states, and end-to-end QA

The most valuable part was maintaining context across the product. An invoice can begin as an email attachment, become a structured obligation, enter a factoring workflow, settle through a payment rail, and contribute to a company’s financial history. Codex helped reason across those boundaries rather than treating each feature as an isolated screen.

Primary Codex session: 019f49b7-57ce-7920-9307-b8c7566787e0

Supporting build sessions are documented in the repository README:

019f49b6-cb5b-7251-9dc6-a7e1ea3fbda9 019f4973-abf4-74b2-9a0a-6423720314c5 019f4834-1ab1-7893-822a-42b919daf27f 019f4819-7767-7561-a20c-98109237f641

Challenges

The hardest problem was maintaining trustworthy state across complete financial lifecycles. Every transition needs authorization, auditability, idempotency, and clear confirmation.

Another challenge was deciding where AI should act autonomously and where financial risk requires explicit approval. Fantasmita uses the model for interpretation, preparation, reconciliation, and explanation while preserving deterministic controls around sensitive execution.

Accomplishments

Unified invoicing, factoring, reimbursements, payroll, and private settlement around one financial identity Designed working capital as a continuation of ordinary business operations Connected agentic workflows to a contextual knowledge graph Applied zero-knowledge verification to business finance Created a voice-native product without hiding financial decisions behind an opaque chatbot Built for international and stablecoin-native businesses from the beginning Reused Persona verification across services instead of repeating identity collection Connected Stripe subscriptions and on/off ramps to the workspace lifecycle

What I learned

The strongest financial agent is not the one that triggers the most tools. It is the one that understands the relationships between documents, obligations, people, permissions, and money.

Business identity can also be created progressively. Software can build an explainable record from the work a company already does instead of forcing it to prove itself from scratch for every financial service.

What’s next

Next I want to deepen explainable invoice-financing decisions, portable privacy-preserving business credentials, and additional settlement and payroll rails.

The larger vision is a financial operating system where real work creates reusable trust—and reusable trust unlocks private payments and working capital.

Built With

• codex
• conta-azul
• next.js
• openai-gpt-5.6
• persona
• plaid
• quickbooks
• stablecoins
• stripe
• typescript
• xero
• zero-knowledge-proofs