Introduction
Fangate is a one-click payment tool built by creators, for creators. After years of struggling with unreliable or non-adult-friendly processors, we built the solution we needed ourselves.
What is Fangate?
Fangate lets any creator turn a single media file or custom service (UGC) into a secure sales link they can post on Telegram, X, Reddit, or anywhere else. Fangate is available as app and web app.
Fans pay instantly with cards or PayPal—no fan account, no paywall, no marketplace to get lost in. Think Clips4Sale infrastructure without the discovery page: no subscriptions, no revenue lock-in, just friction-free, adult-compliant payments that the creator fully controls.
Marketing site: https://fangate.app
Core Functionalities
| Feature | Description |
|---|---|
| One-click payment links | Generate shareable sales links instantly |
| Multi-format media | Photos, videos, multiple files per product |
| Multi-PSP payments | Stripe, PayPal, Epoch integration |
| Age verification | Yoti for buyer 18+ compliance |
| Identity verification | Veriff for creator KYC |
| Affiliate system | Referral codes and commission tracking |
| Consent management | Third-party consent for content |
| Wallet system | Balance tracking, holds, payouts |
| Multi-currency | USD, EUR, GBP support |
What Fangate Is NOT
- NOT a platform or marketplace (no discovery page)
- NOT an OnlyFans clone (no subscriptions)
- NOT restricted to adult content (works for any digital files)
- NOT forcing fans to create accounts
Use Cases
- Any paid file sharing (like WeTransfer + payment)
- Adult content monetization (primary use case)
- Music file sales
- Digital art sales
- Custom service payments (UGC)
Technology Stack
| Component | Technology |
|---|---|
| Backend | PHP 8.x + Laravel |
| Frontend | Flutter (iOS, Android, Web) |
| API | REST endpoints, JSON |
| Database | MySQL |
| Auth | Laravel Sanctum (Bearer tokens) |
| Admin | Filament panel |
API Overview
| Property | Value |
|---|---|
| Base URL (Production) | https://fangate.info/api |
| API Version | 1.0.0 |
| Protocol | HTTPS only |
| Authentication | Bearer tokens (Laravel Sanctum) |
| Response Format | JSON |
| Documentation Format | OpenAPI 3.0 (Swagger) |
Next Steps
- Set up authentication — Learn how to register, login, and use Bearer tokens
- Configure environments — Production, development, and staging URLs
- Handle errors — Standard response format and error codes