Shatale Happy Path Flows

How AI agents make purchases through Shatale — all scenarios from cold start to warm path

Agent (MCP)
Shatale API
User Action
Cold Start Warm Path New Agent Pre-Register Email Alias
Scenario A: Cold Start — New User Cold
1
Agent calls request_purchase
Agent wants to buy a hotel for a user Shatale has never seen
request_purchase({ publisher_user_id: "ext_123", merchant: "booking.com", amount: 150.00, currency: "EUR", description: "Hotel in Paris, 2 nights", user_hint: { email: "john@example.com", name: "John Doe", country: "FR" } })
↓
2
Shatale returns onboarding URL
User not found — creates pending intent + onboarding session
{ state: "action_required", phase: "onboarding", next_action: { type: "open_url", url: "https://app.shatale.com/onboarding/sess_abc" } }
↓ Agent shows URL to user
3
User verifies email
Opens link, email pre-filled from agent hint. Enters 6-digit OTP.
4
User confirms profile
Name + country pre-filled. User reviews and confirms.
5
User reviews purchase
"travel-bot wants to buy Hotel in Paris from booking.com for €150.00"
6
User grants delegation
Accepts ToS + authorizes agent for booking.com, max €150
7
User adds payment method
Stripe card form — details secured by Stripe
↓
8
Shatale issues one-time card
Merchant-locked virtual card, amount-limited, single-use
9
Agent receives card → makes purchase
{ state: "ready", phase: "payment", card: { pan: "4xxx...1234", cvv: "***", exp: "12/26", merchant_locked: true } }
Scenario B: Warm Path — Existing User Warm
1
Agent calls request_purchase
Same user, same agent — delegation already exists
↓ User found, delegation valid, policy approved
2
Shatale issues card immediately
No onboarding needed — straight to payment
{ state: "ready", phase: "payment", card: { ... } }
3
Agent uses card — done in <2 seconds
Scenario F: Returning User, New Agent New Agent
1
Agent B calls request_purchase
User exists (from Agent A), but no delegation for Agent B
↓ User found, profile complete, KYC done, payment on file
2
Only delegation consent needed
{ state: "action_required", phase: "delegation", requirements: [{ type: "delegation_consent" }] }
3
User approves new agent
Quick consent — no re-entering profile or payment
4
Card issued → purchase complete
Scenario E: Agent Pre-Registers User Pre-Reg
1
Agent calls register_user_profile
No purchase yet — just setting up the user
register_user_profile({ publisher_user_id: "ext_456", user_claims: { email: "jane@example.com", name: "Jane Smith", country: "US" } })
2
Shatale returns verification URL
{ claim_set_id: "claims_abc", verification_status: "pending_verification", next_action: { type: "open_url", url: "https://app.shatale.com/onboarding/..." } }
3
User verifies + confirms profile
No purchase context — just identity setup
↓ Later, when agent wants to purchase...
4
Agent calls request_purchase
User already exists — warm path or just needs delegation
Scenario H: Email Alias (No Purchase) Relay
1
Agent calls create_email_alias
request_temporary_credentials({ publisher_user_id: "ext_789", merchant_domain: "aws.amazon.com", purpose: "Create AWS account for client" })
2
Shatale returns relay credentials
{ relay_email: "abc123@relay.shatale.com", generated_password: "Xk9mP2...", expires_at: "2026-05-30T00:00:00Z" }
3
Agent uses credentials on merchant site
30-day TTL, merchant-scoped, pseudonymous until user claims

Shatale — AI Agent Payment Infrastructure
shatale.com · MCP Tools