Picture this

Who it is for

A brother running the shop, a nephew handling a wedding: you write the rules in plain words, the person pays from a contract with their own wallet, and a payment that breaks a clause is refused and stamped with that clause. Anything over your ask line waits for you.

Two ways to own it

What you get

Base$299

$75 deposit to reserve

The full app from Terry's Arc portfolio: live surface, contracts on Arc, about page, handover of code and deployment.

You choose: brand name
You choose: accent color
You choose: domain

Customfrom $2,500

Built around you

Reshape it entirely: new features, your flows, your brand end to end, integrations you need. We scope it with you.

Everything in Base
Custom features and design
Priority build

Why it is new

What exists today, and what this does differently

What is new

Plain language mandates compiled into enforced spending rules with recorded refusals were not found.

Closest things out there

Safe spending limits; Coinbase spend permissions.

Checked with web searches in October 2026. A search is not proof that nothing similar exists, and the market moves fast, so we recheck before every build.

What it unlocks

The human in it

Built for Arc's sub second, USDC native settlement.

The Regatta Board

Races it can enter

hackathon · Circle · upcoming

Arc / Circle developer programs and hackathons

unknown

Official page ↗

Answers Arc's Request for Builders; check current terms.

Their rule on existing code: unknown

What you own

The whole app, not a starter kit.

The complete Charter app: hand someone money with one page of plain words rules, and a contract on Arc pays what the page allows and refuses the rest with the clause, with a paywall, owner console and helper agent built in.

Base price · $299

The user app, complete

Every buyer gets the same finished app. Basic branding and copy changes come through a quick form.

Three step onboardingHome

Shown once: write one page, the money obeys it, big ones wait for you.

Progress and next actionHome

Spent against budget, refusals, waiting asks and one clear next step.

Plain words page editorPage

Who may be paid, per payment cap, ask line, total budget and new vendor rule, signed on Arc.

Second spenderPage

A second person spending from the same page with narrower limits. Gated behind Family.

Payments judged by the pageSpend

Each payment is paid in a second, refused with its clause, or held for the giver.

Refusal stamps and share cardSpend

A refusal shows the clause, so it is the page saying no; share what happened.

Approvals inboxAsks

Approve or hold payments over the ask line; keep or reconsider refused new vendors.

Saved vendor bookAsks

Approve a vendor once for every page. Gated behind Family.

Sunday page and receiptsSunday

Paid, refused and waited this week, with receipts that show what is and is never on chain; suggestions gated behind Family.

Plans and settingsMe

Pricing from the owner paywall, USDC checkout, ask notifications, permissions and vision.

Open the full app demo

Add-on

Owner console

Your admin side: revenue, paywall editor, users, rules and the agent log.

Revenue and paywall editorRevenue

MRR, per payment fee, incoming USDC, accepted methods, live tier and gate editing.

Pages in useFamilies

Every live charter with budget used and refusals, plus template sends to planners.

RulesRules

Practice payments per draft, fee per payment, clause limit, new vendor age, sponsored fees.

Agent log and roadmapAgent

How the helper misread a rule and adapted, running costs, plus the priced Roadmap screen.

Top-up

Growth and referrals

Referral and growth mechanics, switched on when you are ready to grow.

Association evenings and referralsGrowth

Run a diaspora association evening and track spenders who become writers.

The money path, built in

How it earns for you

One page with one spender is free. Families pay for more pages and helpers, event planners pay for every client, and the owner can add a tiny fee per payment routed.

One PageFreeOne charter, one spender, refusals with the clause, receipts

Family$5 a monthUnlimited pages, a second spender, Sunday suggestions, saved vendor book

Event Planner$29 a monthCharters for every client, shared vendor lists, branded Sunday pages

Optional fee of a fraction of a cent per payment, set by the owner. Arc fees are around a cent per payment or refusal and can be sponsored.

Prices are yours to set. Illustrative, not a promise of income.

Growth loops, built in

How it spreads

Spenders who see the page work write their own for the next family event
Refused fake vendor share cards travel in family groups
Event planners run every client budget on a page
Diaspora association evenings where members write a first page
Shared templates for weddings, school fees and house repairs

Roadmap · build the next phase with us

Where it goes next

v1 included

The full charter app

Plain words page compiled to rules
Instant payments inside the rules
Refusals stamped with the clause
Ask line approvals and Sunday page
Paywall, owner console, helper agent

Included

Vendor book and UPI payouts

Shared vendor books per city
UPI and bank payout to vendors
Charter templates for weddings, school fees and care
WhatsApp approvals

Add-on from $450

Charters for organisations

Diaspora associations funding projects back home
Multi signer pages
Public charters with open receipts
Accountant export

Add-on from $1,100

For investors and grant reviewers

The pitch, ready

Hand someone your money with one page of rules, and the contract refuses anything the page does not allow.

Problem: Families abroad send large sums home for weddings, fees and repairs. Trusting a relative means trusting every vendor who pressures them, and saying no falls on the relative.

Solution: The giver writes one page in plain words. A contract on Arc pays what the page allows in a second, refuses the rest with the clause number, and holds big payments for the giver's tap.

Why now: Arc's sub second USDC settlement and cheap model compilation of plain words rules make per payment enforcement practical for a family budget.

Market: Diaspora families sending money home, event planners, and small associations funding projects in their home towns.

The ask: Pilot partners: two diaspora associations and one wedding planner, plus Arc and Circle developer programs.

Funding is never guaranteed. Check each program's rules.

For hackathons and demo days

Your 2 minute demo

Home: meet Mathew, 58, in Dubai, funding his niece's wedding in Kochi.
Page: write five clauses and sign the page on Arc.
Spend: Anil pays the caterer, then a three day old decor account is refused under clause 3.
Asks: approve the hall balance before Mathew's shift.
Sunday: the weekly page and receipts, on chain and off.
Owner Agent: the misread total and the practice payment fix.
Owner Revenue: change the Family price and preview the Plans sheet.
Owner Growth and Roadmap: run an association evening, then request UPI payouts.

Many hackathons require code written at the event. See the Regatta Boardfor each race's rule.

Make it entirely yours

Custom work from $2,500: your own clause types and templates, local payout partners, extra languages, or a white label version for a planner or association. Scoped on a call.

Custom from $2,500

BLUEPRINT

Why it matters and how it really works

The need

Families and small businesses hand money to someone they trust for a job: a nephew running a wedding, a brother running a shop. Sending a lump sum means no limits; doing every payment yourself means you cannot sleep. People need to delegate spending with rules that actually hold.

What exists and what is new

Spending limits exist: Safe offers allowance and spending limit modules, and Coinbase spend permissions let an app spend within set limits. What we did not find is plain language rules compiled into enforced spending rules, read back to the owner before signing, where each refused payment is recorded onchain with the clause that refused it and big payments wait for the owner. High novelty in the packaging; the enforcement primitives are known.

The data it runs on

The rule numbers (caps, ask line, total budget), an allowlist of vendor addresses, every payment and refusal with its clause number, owner approvals, and a hash of the plain language page. The words, names, invoices and chats stay offchain.

1.The mission

Let anyone hand over money with rules attached, so trust in a person does not have to mean trust in every vendor who calls them.

2.Why people can't resist it

Refusals with a reason A no comes stamped with the clause, so it is the page saying no, not the nephew.

Sleep through it Small payments go through in a second; only the big ones wait for your tap.

The Sunday page One page back each week: paid, refused, waited, and one suggested change.

3.How it works for real

Wallets: Owner and spender sign in with passkey wallets (Privy or Circle Wallets). The charter itself is a smart contract holding USDC on Arc, where USDC is also the gas token.

Rule compiler: A model (for example a Claude Sonnet class model through OpenRouter) turns the plain words into structured rules, then runs practice payments and asks the owner when a rule reads two ways. The owner signs the structured rules, not the model's guess.

Charter contract: Enforces vendor allowlist, per payment cap, total budget and new vendor checks; payments to the same address within a window are summed so splitting does not slip under a cap.

Ask line: Payments over the ask line are queued in the contract until the owner approves with a passkey signature, or they expire.

Refusal records: Each refused payment emits an event with the clause number, indexed for the app and the Sunday page.

App and alerts: Next.js and Convex for the page, digest and push notifications; optional card or bank onramp to fund the charter with USDC.

4.Cost per use and pricing

Compiling a page with a mid tier model is a few cents per draft. Each payment or refusal on Arc is expected to cost around a cent in USDC (check current Arc fees). Example month for a family shop: 60 payments and 5 refusals is under $1 in fees plus about $0.20 of model calls.

One page Free

One charter, up to 3 rules, refusals recorded.

Family $5 a month

Unlimited rules, ask line approvals, Sunday page, two spenders.

Shop $15 a month

Several charters, staff spenders, export for the accountant.

5.Growth loop

The spender sees the page work and writes their own for the next family event. Share cards about a refused fake vendor travel in family groups.

6.Risks and guardrails

Misread rules: The model can misread a rule, so every rule is shown back in structured form and tested with practice payments before signing.

Vendor fraud outside the rules: A listed vendor can still overcharge; caps and the ask line limit the damage, they do not remove it.

Legal: This is a spending tool, not a trust or escrow service; check local rules on holding funds for others.

Key loss: Passkey wallets with recovery; the owner can always pull unspent funds back.

Network status: Arc is new; confirm mainnet availability and fees before launch.

7.Build order

Plain words to structured rules with read back
Charter contract with allowlist, caps and total budget on Arc testnet
Refusal events with clause numbers
Ask line queue and passkey approval
Spender pay screen
Sunday page by email

8.Where this is going

Now
An uncle in Dubai funds a wedding in Kochi with five rules.
Next
Shops give staff charters instead of the owner's card.
Later
Charters for AI agents: the same page limits what an agent may spend.
The big one
Delegated money with rules anyone can write, for every family that sends money home.

Costs and tools are estimates at the time of writing. General information only, not legal or financial advice.

OWNER PLAYBOOK

Own it, then chart your voyage

Nine routes from one vessel. Tap a port to open its chart.

Why own Charter

Charter: Hand someone your money with one page of rules, and the contract on Arc refuses anything the page does not allow. Using someone else's version means their rules, their brand and their revenue. Owning Charter means it is deployed under your wallet, carries your name, and every customer, partner and result builds your track record instead of theirs.