Connect multiple gateways to under one sdk, and manage subscriptions under one dashboard
Fype turns checkout, routing, webhooks, subscriptions, and provider switching into one orchestration layer your team can see and tune in real time.
Drop in Fype once, then change providers, route rules, and recovery logic from the dashboard while checkout keeps moving.
const checkout = await fype.checkout({
gateway: "auto",
recovery: true,
subscriptions: "native",
});
// dashboard changes apply instantly
Payment succeeded
Routed by live gateway health
Fype Corescore & route
99.7%
Auth rate
2.1s
Retries
24k
Events
Recurring billing, recovery, experiments and feature gating — one engine that keeps mandates alive and revenue compounding across every Indian gateway.
Fype bridges the gap between traditional payment gateways and autonomous agents. Expose clean APIs, local environments, and ready-to-run MCP servers instantly.
Launch local checkout sandboxes, configure proxy tunnels, and test webhooks locally in seconds.
Expose payment routing, balances, and analytics directly to AI Agents using LLM-native schema integration.
Markdown-formatted endpoint instructions, system-prompt injection scripts, and clear context metadata.
Can’t find the answer you’re looking for? Reach out to our support team or consult the agent docs.
Contact SupportFype is a decoupled payment orchestration engine. You integrate our unified SDK once, and it handles routing checkout sessions, managing secure transactions, and connecting to multiple gateways (like Stripe, Razorpay, Cashfree, and PayPal) without requiring separate backend integrations.
Fype is built AI-ready out of the box. We expose native Model Context Protocol (MCP) servers, structured schemas, and clean markdown documentation so autonomous agents can safely query balances, check checkout statuses, and execute refunds without custom API integrations.
No. Fype's adapter pattern completely decouples gateway logic from your application. You can add, remove, configure routing logic, or switch gateways directly from the Fype dashboard in real-time with zero code changes or redeployments.
If a recurring subscription charge is declined, Fype's subscription engine automatically triggers customizable dunning policies (like backoff retries, smart timing, or alternative gateway failovers) to recover revenue silently in the background.
Yes. Instead of writing custom handlers for Stripe, Cashfree, and Razorpay webhook shapes, Fype normalizes all incoming gateway events into a single, standardized webhook contract, saving your developers hours of integration effort.
