Documentation Index

Fetch the complete documentation index at: https://docs.fype.dev/llms.txt

Use this file to discover all available pages before exploring further.

​

Introduction to Fype

Fype is a decoupled payments orchestration engine. It acts as a middleware layer between your application and various payment gateways (like Razorpay, Cashfree, or Stripe).

​

Why Fype?

​

1. Unified Interface

Integrating multiple payment gateways usually requires writing specific code for each one. With Fype, you integrate once and use any supported provider.

​

2. Zero-Lock-in

Moving from one gateway to another typically involves significant refactoring. Fype allows you to switch providers via the dashboard without touching a single line of your integration code.

​

3. Decoupled Checkout

Fype provides a managed checkout experience. You create a payment on your server, receive a checkout_url, and redirect your customer. Fype handles the heavy lifting of communicating with the gateway, verifying signatures, and managing the payment lifecycle.

​

4. Developer Experience

• Idempotency: Built-in support for Idempotency-Key headers to prevent double-charging.
• Sandbox Environment: A robust simulator to test all success and failure scenarios without real money.
• Standardized Webhooks: Receive the same webhook payload regardless of which gateway processed the payment.

​

How it Works

1. Merchant Server: Calls the Fype API to create a payment.
2. Fype API: Orchestrates with the configured gateway and returns a checkout_url.
3. Customer Browser: Redirected to the checkout_url to complete the payment.
4. Fype Engine: Validates the payment with the gateway and transitions the status.
5. Webhook Worker: Delivers a standardized webhook to the merchant’s server.
6. Merchant Dashboard: Provides a single pane of glass to manage payments and configurations.