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.
Integration Architecture
Fype is designed to be decoupled. This means your application logic remains agnostic of the underlying payment gateway.The Decoupled Lifecycle
The diagram below describes the typical integration flow:Key Integration Points
1. Server-to-Server API
You interact with Fype’s REST API from your backend to create payments, fetch details, and process refunds.2. Hosted Checkout
Instead of building complex payment forms for every gateway, you redirect customers to Fype’s hosted checkout. Fype handles:- Rendering the appropriate UI for the selected provider.
- Communicating with gateway SDKs.
- Validating signatures on the client side.
- Handling 3D Secure redirects.
3. Standardized Webhooks
Fype acts as a translator. When a gateway sends a webhook (which varies wildly between providers), Fype normalizes it into a standardFype Event and forwards it to your server.
4. Idempotency
For all state-changing operations (like creating a payment), Fype supports theIdempotency-Key header. If your server retries a request due to a network timeout, Fype ensures you don’t create duplicate payments for the same intent.