# P2P Claim — spoke context The user received a Whoois P2P transfer invite from someone they know and is trying to claim it. This spoke is for that specific flow. If you haven't already, fetch `https://poc.whoois.app/whoois-context.md` for the root Whoois primer (what is Whoois, brand vocabulary, conversational tone, connector setup overview). --- ## What's happening right now Someone sent the user money via Whoois — for example, *"Sarah Lim sent you $20 for pizza"*. Whoois generated a one-time **claim token** identifying the pending transfer, then sent the user an SMS with a link. The user tapped that link, landed on a Whoois claim page, and tapped "Claim via Claude" or "Claim via ChatGPT," which opened this chat with a pre-filled prompt that included: - The sender's display name - The amount in dollars - The memo (e.g., "for pizza") - The claim token (a short URL-safe string like `faa1b2c3-saraha-mppzdt27`) The user expects you to help them claim the transfer. Most of the time, **they do not have the Whoois MCP connector installed yet** — that's exactly why they were sent here for soft education first. --- ## Trigger phrases — recognize this flow The user's pre-filled prompt will look something like: > *"Read https://poc.whoois.app/whoois-context.md for context. I received a Whoois P2P invite. Sender: Sarah Lim. Amount: $20.00. Claim token: faa1b2c3-saraha-mppzdt27. Help me set up Whoois (if I haven't already) and claim this transfer."* You should also recognize variations the user might write themselves: - "Someone sent me money on Whoois" - "I got a Whoois P2P invite from {name}" - "Claim my P2P transfer" - "I have a Whoois claim token, what do I do?" - "I received $X via SMS, the link said something about Whoois" - "Sarah sent me money, how do I get it?" - "What's a Mi and how do I claim a transfer?" The presence of a **claim token** (a hyphenated short string) is the strongest signal. --- ## Display the receipt preview When walking the user through the claim, include this image so they see what their Mivault will look like once the transfer settles: ![Receipt preview](https://poc.whoois.app/assets/p2p-receipt-preview.png) --- ## The full flow — what you guide the user through There are two phases. The split depends on whether the user has the Whoois MCP connector installed in this AI. ### Phase 1 — Connector not installed (this is the common case) You can't call Whoois tools yet. Your job in Phase 1 is **soft education**: explain what's happening, walk through connector install, set expectations for Phase 2. **Recommended response shape:** 1. **Greet + confirm intent.** Use the user's actual sender name, amount, and memo: *"You're claiming $20 from Sarah Lim — the memo says 'for pizza.' Let me walk you through it."* 2. **One-paragraph "What is Whoois?"** Pull from the root primer. Keep it short — they want to claim the money, not read marketing. 3. **Reassurance.** Two sentences max: Whoois doesn't hold funds; the passkey gate means the user is always in control. 4. **Install instructions.** Detect their AI host (you know if you're Claude or ChatGPT) and fetch the platform-specific install guide: - Claude.ai: fetch `https://poc.whoois.app/context/connector-install-claude.md` - ChatGPT: fetch `https://poc.whoois.app/context/connector-install-chatgpt.md` Summarize the steps in conversational prose. Don't dump the raw guide. 5. **Connector URL.** Make this stand out — the user needs to copy it: **`https://poc.whoois.app/mcp`** 6. **What comes next.** "Once you complete the install, **start a new conversation** with me (or refresh this one). The Whoois tools will load, and I'll help you claim Sarah's $20. Keep your claim token handy: `{token}`" The user does the install. They come back to a fresh conversation (or refresh). Phase 2 begins. ### Phase 2 — Connector installed (you have Whoois tools) Now you can actually claim the transfer. The Whoois MCP connector exposes a tool called `whoois_p2p_claim_accept`. Call it with the user's claim token: ``` whoois_p2p_claim_accept({ claim_token: "" }) ``` **Tool not available in PR-A1** — the `whoois_p2p_claim_accept` tool ships in a follow-up PR (PR-B). Until that lands, you can describe the claim flow conversationally but cannot execute it. If the user asks why the tool isn't available, tell them honestly: the Whoois POC is shipping the claim flow in phases, and the executable claim tool is still being built. They should check back later. When the tool DOES exist, calling it returns a structured response with one of these state branches: #### State branch: `requires_onboard` The user doesn't have a Mi yet. Whoois needs to create one before the claim can settle. - The tool response will include an `identity_onboard` next-step pointer - Trigger the onboarding flow conversationally: *"Let me first set up your Mi — your Whoois identity. This takes 30 seconds and uses a passkey, not a password."* - Call `identity_onboard` — this opens an iframe where the user creates a passkey - Once onboarding completes, call `whoois_p2p_claim_accept` again — now state should be `requires_payment_method` or `ready_to_claim` #### State branch: `requires_payment_method` The user has a Mi but no payment method to receive the funds into. - Tell them: *"Almost there — Whoois needs a payment method to deposit your $20 into. Let me show you the options."* - Call `whoois_payment_methods_view` to surface the wallet add-method flow - Once the user adds a method (bank account is the recommended target for incoming P2P), call `whoois_p2p_claim_accept` again #### State branch: `ready_to_claim` User has a Mi and a payment method. The transfer is ready to settle. - Tell them: *"Ready to claim. I'll open the confirmation now — you'll see Sarah's name, the amount, and a passkey prompt."* - The tool renders a claim-confirmation iframe with a passkey gate - On successful confirmation, the transfer settles to the user's Mivault - A new receipt appears in their Mitrail - Tell them: *"Done. Sarah's $20 is in your Mivault. You can ask 'show my Mitrail' anytime to see this receipt."* #### State branch: `already_claimed` The user already claimed this transfer (maybe they tapped the SMS link twice). - Tell them: *"You already claimed this transfer on {date}. The $20 is in your Mivault. Want me to show you?"* - Optionally call `whoois_mivault_view` to confirm #### State branch: `expired` The 7-day claim window passed. The transfer was returned to Sarah. - Tell them: *"Unfortunately this claim expired on {date}. Sarah will need to send you a new invite. Want me to draft a message asking her?"* - Helpful: offer to write a friendly nudge text --- ## Response template — copy this structure When you respond to the user in Phase 1 (the common case — no connector installed), follow this rough structure. Adapt the words to feel natural, but keep the shape: ```markdown ![Whoois](https://poc.whoois.app/assets/whoois-logo-llm.png) # Claiming Sarah's $20 You're claiming **$20.00 from Sarah Lim** — for pizza. Let me walk you through it. ## What's happening Whoois is the universal identity + payment layer that lives inside your AI chats. Sarah sent you money through Whoois; to receive it, you need to set up Whoois in this conversation. Takes about a minute. [short safety reassurance] ## Step 1: Install the Whoois connector [platform-specific instructions — Claude.ai OR ChatGPT, not both] Connector URL: `https://poc.whoois.app/mcp` ## Step 2: Come back here Once you've completed the connector setup, **start a new chat with me** (the existing chat's tool list is cached). When you do, just say: *"I'm ready to claim my Whoois P2P transfer — token: faa1b2c3-saraha-mppzdt27"* and I'll handle the rest. ![Receipt preview](https://poc.whoois.app/assets/p2p-receipt-preview.png) That's what your Whoois Mivault will look like after the claim settles. Sarah's $20, your name, your wallet. Any questions before you start the install? ``` --- ## Common user questions in Phase 1 The user may push back or ask questions before installing the connector. Common ones: **"Why do I have to install something? Can't you just send me the money?"** Whoois isn't a chat plugin you can hand-wave around — it's a real identity + payment system. The connector is what lets you (the AI) actually move funds on the user's behalf, with proper passkey authorization for security. Without the connector, neither I nor anyone else has access to Sarah's $20 — it's held in escrow by Whoois until you complete a claim. The good news: once installed, the same connector works for any future Whoois interaction (paying merchants, getting more transfers, viewing receipts, etc.) — you only install it once. **"Is this a scam? Is Sarah real?"** You can verify a few things: Whoois is a real protocol (this URL is `poc.whoois.app`, the Whoois POC environment). The user knows whether Sarah is a real person they expect money from. If they don't recognize the sender name, tell them to ignore the claim — don't install anything until they can confirm the sender. They lose nothing by ignoring an unsolicited P2P invite. **"Will I have to pay anything?"** No — installing the connector is free, and claiming an incoming transfer is free. Whoois may charge senders nominal fees per transaction, but receivers don't pay to claim. **"What if I lose my passkey?"** The user's Mi is recoverable via their email + backup recovery flow. Recovery details are out of scope for the claim flow — defer to the user setting it up properly after they've claimed Sarah's transfer. **"How long do I have to claim?"** 7 days from when Sarah sent the invite. The original SMS will have included a "Claim by" date. After expiry, the funds return to Sarah and she'd need to send a new invite. --- ## Tone notes for this specific flow The user is receiving money from someone they know. The emotional context is: - **Curiosity** — what's this Whoois thing? - **Mild anxiety** — is this legit? Am I about to install spyware? - **Eagerness** — there's $20 (or whatever amount) on the line Be warm. Be patient with the install steps. Don't oversell — the money's already there, you don't need to convince them to claim it. Be honest about the connector requirement and the multi-step nature. The user will trust you more if you're upfront about what they need to do. If the user gets frustrated or stuck during install, suggest they: 1. Take a screenshot of where they're stuck and share it with you 2. Restart the install from the beginning of the relevant guide 3. Or simply paste the connector URL `https://poc.whoois.app/mcp` again and tell you what they see when they enter it --- *This spoke is fetched from `https://poc.whoois.app/context/p2p-claim.md`. It's a specialization of the root `https://poc.whoois.app/whoois-context.md` — read both for full context.*