How Tollstile compares
Tollstile compared with raw x402 middleware, MPP SDKs, edge gateways, and Stripe.
Pre-release · planned API
Tollstile does not compete with payment protocols or providers — it sits on top of them. The question it answers: once an agent can pay, what does the merchant still have to build?
| Raw x402 middleware | MPP SDK | Edge gateway | Stripe alone | Tollstile | |
|---|---|---|---|---|---|
| Several 402 protocols on one route | One | One | The platform's | Stripe's | Any configured rail |
| Runs inside your app | Yes | Yes | At the edge | Via API | Yes |
| Price locked by a signed quote | — | Challenge-bound | Varies | — | Yes, across all rails |
| Subscribers, credits, pay-per-call | Build it | Build it | Varies | Build it | Built in |
| Release or refund when the handler fails | Build it | Build it | Varies | Build it | Built in |
| Unknown outcomes reconciled with the provider | Build it | Build it | Varies | Per API call | Built in |
| Payment records live in | Your code | Your code | Platform dashboard | Stripe dashboard | Your database |
| Local development without a wallet | Testnet | Test mode | Varies | Test mode | Test rail |
| Moves funds | Facilitator | Provider | Provider | Stripe | Never |