Inspiration

School messages contain small but consequential obligations: what to pay, by when, for which event, and what happens when plans change. A payment receipt in one app and the original message in another leave a parent reconstructing the story. Tomorrow Ready keeps the message, the parent's decision and the receipt together.

What it does

Paste a fictional school message. AI proposes one explicit amount, currency and deadline, with exact quotations from the message. The parent reviews the draft and the fixed test recipient before saving. The reviewed obligation opens PayPal Sandbox; a separate test buyer approves the order. The local server verifies and captures it, and displays Paid only when PayPal reports a matching completed capture.

If the school cancels the event, a person reviews and confirms the cancellation. The payment record survives. The app flags that a refund needs attention and prevents a new payment attempt for that record. It does not claim a refund happened automatically.

How we built it

The interface uses React and TypeScript with a Vite local server. Fireworks serves accounts/fireworks/models/muse-spark-open for live structured extraction. The server validates exact source quotations, currency/amount and an explicit ISO deadline. AI cannot select the payee or call payment operations.

PayPal integration is central: Sandbox OAuth 2.0 and Orders v2 create, buyer approval, capture and GET readback. The server binds each obligation to its amount, currency, merchant and reference. Stable request identifiers and a durable local ledger support recovery. If a dispatched request has an uncertain outcome, the app blocks blind retries and asks for reconciliation.

Secrets stay in a local ignored file; the browser receives no client secret or AI key. The API accepts only the local interface's origin and uses CSRF protection. This is a single-user local prototype, not a public payment backend.

What is new in this entry

This standalone Tomorrow Ready prototype began in October 2026 during the submission period. The broader DuetNest idea predates the entry. An earlier Meta hackathon variant explored school-message planning; its submitted version remains separate on the repository's main branch.

On November 4 we built the PayPal-specific payment extraction/review UI, fixed Sandbox payee binding, create/approval/capture/readback workflow, durable payment state, idempotency/recovery guards, and cancellation with receipt retention. The entry uses the codex/paypal-hackathon-20261104 branch. We disclose the reused repository foundations rather than claiming the whole repository was created for PayPal.

Challenges and what we learned

An AI draft is not permission to pay. A checkout return URL is not proof of a completed capture. A cancelled event is not a refund. Separating those states was the main design and engineering challenge. Exact quotes help a parent review the evidence; they do not prove a message's meaning or legitimacy.

What we verified

We completed an actual PayPal Sandbox order and capture for EUR 12.50 with fictional data, independently read it back from PayPal, and verified that the receipt remains after cancellation and browser reload. Two live Fireworks extraction requests accepted the sample; this is demonstration evidence, not a general accuracy benchmark. Fifteen targeted tests cover validation, origin/CSRF restrictions, duplicate actions, approval, receipt matching, uncertain outcomes and restart/cancellation recovery. Desktop and 320 px views were inspected.

The 2:22 demonstration combines actual recorded app interaction and captures from the successful Sandbox run. Idle time is removed; synthetic English narration and fictional data are disclosed. It is not an uncut latency benchmark and contains no real-money payment.

Try it

Use the public PayPal branch linked below. Its root README contains complete local setup and run instructions for Node 26, PayPal Sandbox and Fireworks. Open http://127.0.0.1:4322/payments.html after starting the local server. The earlier Meta GitHub Pages walkthrough is a different route and is not the PayPal application.

What's next

School onboarding, a reviewed refund workflow and multi-user operation with a transactional database and validated webhooks. Real-family usefulness and measured time savings remain to be tested. This submission demonstrates the bounded source-to-payment workflow with sandbox funds.

Built With

Share this project:

Updates

Submission history