Starting out
Under $100k processed per month
2.6% + $0.25 per transaction
0.30% + 5¢ under Stripe- Every API, SDK, and MCP tool included
- Subscriptions and invoices at $0
- Sandbox with no signup gate
Same cards, same security, same afternoon integration. 0.3% and 5¢ less on every transaction than Stripe — and the rate drops again as you grow.
PCI DSS Level 1 No monthly fee, no minimum MCP server for AI agents
$66,000 a year vs. Stripe
That's $5,500 back every month.
Card rates only, compared against Stripe's published 2.9% + $0.30. Assumes a $50 average transaction and no international, dispute, or billing-software add-ons on either side. Your tier is set by last month's volume and applies automatically.
Why Strtups
We built the payments API we wanted to use: one published rate card, an integration you finish in an afternoon, and tooling your AI agent already knows how to drive.
The rate you see is the rate you pay. Published tiers, applied automatically by volume. No sales call, no negotiated pricing that someone else got a better version of.
An integration you finish today. A typed SDK, a REST API that behaves the way you already expect it to, and drop-in card fields so no card number ever reaches your servers.
PCI DSS Level 1, from day one. Tokenised cards, 3-D Secure, signed webhooks, and encryption at rest. The compliance burden stays on our side of the line.
Your AI agent can build it. An official MCP server plus agent-readable docs, so Claude or Cursor can wire up checkout and test it against sandbox without you pasting anything into a chat window.
Subscriptions and invoices cost nothing extra. Recurring billing is not a second product with a second percentage attached. It is part of the API, at $0.
Payouts on your schedule. Standard, next-day, or instant — picked per payout rather than locked to your account, so cash flow is a decision instead of a setting you made once.
Developer experience
Charges, customers, subscriptions, refunds, payouts, webhooks. Six resources, predictable verbs, and errors that tell you what to fix instead of what went wrong.
import { Strtups } from "@strtups/node"; const strtups = new Strtups(process.env.STRTUPS_API_KEY); // One call. The rate you were quoted is the rate you pay. const charge = await strtups.charges.create({ amount: 4900, // $49.00, in cents currency: "usd", source: token, // from the browser SDK description: "Pro plan — monthly" }); charge.status; // "succeeded" charge.fee; // { total: 152, rate: "2.6% + $0.25" }
import os from strtups import Strtups strtups = Strtups(os.environ["STRTUPS_API_KEY"]) # One call. The rate you were quoted is the rate you pay. charge = strtups.charges.create( amount=4900, # $49.00, in cents currency="usd", source=token, # from the browser SDK description="Pro plan — monthly", ) charge.status # "succeeded" charge.fee.total # 152
curl https://api.strtups.com/v1/charges \ -H "Authorization: Bearer $STRTUPS_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $ORDER_ID" \ -d '{ "amount": 4900, "currency": "usd", "source": "tok_1MvC2k", "description": "Pro plan — monthly" }' # => { "id": "ch_9f2a", "status": "succeeded", # "fee": { "total": 152, "rate": "2.6% + $0.25" } }
// app/api/strtups/route.ts export async function POST(req) { // Throws if the signature does not verify. There is no // unsigned path, so a forged event cannot reach your code. const event = strtups.webhooks.verify( await req.text(), req.headers.get("strtups-signature") ); if (event.type === "charge.succeeded") { await grantAccess(event.data.customer); } return new Response("ok"); }
Built for AI
Payments is the part of the stack coding agents get wrong most often, because the docs are long and the failure modes cost real money. So we shipped the tools first.
One line to install, in Claude Code, Cursor, or any MCP client. Your agent gets typed tools instead of a scraped documentation page.
The MCP server is the fast path. Everything underneath it is built so an agent working from raw docs still gets it right.
Security
Cheaper processing is worth nothing if it moves risk onto you. It doesn't: the card leaves the browser encrypted and comes back to you as a token.
The highest certification a processor can hold, audited annually. Using our drop-in fields keeps your own scope at SAQ A.
Card numbers are encrypted in the browser and exchanged for a token. Your database only ever stores the token.
Risk scoring on every charge, with 3-D Secure step-up available per transaction so liability shifts when you need it to.
Every event is signed and every write takes an idempotency key, so a retry or a replay can never charge someone twice.
Pricing
Your tier is set by last month's processed volume and applies on its own. There is nothing to negotiate, nothing to renew, and no tier you can only reach by asking.
Under $100k processed per month
2.6% + $0.25 per transaction
0.30% + 5¢ under Stripe$100k – $5M processed per month
2.55% + $0.20 per transaction
0.35% + 10¢ under Stripe$5M+ processed per month
2.5% + $0.15 per transaction
0.40% + 15¢ under StripeGet in early
Tell us where to reach you and we'll send you keys the day Strtups Payments opens — earliest signups first.
Check your inbox for a confirmation. We'll email you the moment Strtups Payments goes live.