James knew TutorClaw had a get_upgrade_url tool. He had built it in Module 9.3, Chapter 14. A learner asks about upgrading, the MCP server generates a Stripe Checkout link, and the learner pays. Simple enough.
But now he was thinking about the money. "The student clicks a link and pays. Then what? How does the MCP server know they paid? And how much does Stripe take from every transaction?"
Emma pulled up TutorClaw's revenue number. "$15,750 per month. Stripe's standard fee is 2.9% plus $0.30 per transaction. Let's see how much that costs."
You are doing exactly what James is doing. You built the payment integration in Module 9.3, Chapter 14. Now you need to understand what it costs and how the money flows through every system.
Stripe charges 2.9% plus $0.30 per successful transaction for US domestic cards. Since TutorClaw targets Pakistani learners paying in PKR, the actual rate is higher: Stripe's cross-border fee adds roughly 1% (making it ~3.9% + $0.30 for international transactions). The calculations below use the 2.9% US domestic rate as the baseline.
At TutorClaw's scale with the US domestic baseline:
The flat fee dominates. At $1.75/month subscriptions, Stripe's $0.30 per transaction is a larger cost than 2.9% of the payment amount. The Python calculator in Module 9.4, Chapter 4 computes both components and reports ~$1,647, which is the number to use for financial planning.
Stripe costs roughly 30 times what the entire infrastructure costs. In Architecture 4, payment processing is the largest single expense by a wide margin. Not compute, not storage, not the database.
The 2.9% percentage scales proportionally with revenue. But the $0.30 flat fee does not scale; it is the same whether the transaction is $1.75 or $10,500. This creates a disproportionate impact on low-price subscriptions:
For a Paid-tier subscriber at $1.75/month, Stripe's flat fee alone consumes 17% of the revenue. Add the 2.9% percentage fee ($0.05), and Stripe takes $0.35 of every $1.75 payment (20%). For Premium subscribers at $10.50, the combined Stripe take is $0.60 per transaction (5.7%).
This is why many subscription products bill annually instead of monthly: fewer transactions means fewer flat fees. If TutorClaw's 3,000 Paid subscribers switched to annual billing ($21/year), the flat fee drops from $0.30 x 12 = $3.60/year to $0.30 x 1 = $0.30/year per subscriber. That saves $9,900/year across the Paid tier alone.
Here is the complete sequence when a learner upgrades from Free to Paid:
The entire flow happens without any manual intervention. No admin panel, no batch processing, no nightly sync. The webhook fires within seconds of payment, and the tier change takes effect on the very next MCP call.
Stripe handles four distinct scenarios in TutorClaw:
The monetization gate is server-side. The MCP server checks the learner's tier on every get_learner_state call. If a payment fails and the grace period expires, the tier reverts to free automatically.
James traced the flow on a piece of paper: MCP tool, browser, Stripe, webhook, PostgreSQL, next MCP call. Six steps, fully automated.
"It is like a freight broker's commission," he said. "Every shipment that goes through the broker, they take a percentage. You could handle logistics yourself, but the broker has the network, the insurance, the compliance paperwork. You pay 2.9% for not having to build all of that."
"Exactly," Emma said. "And at roughly $1,650 per month, Stripe is the most expensive line item in Architecture 4. Thirty times the infrastructure cost. More than the server, the database, and content delivery combined."