Enhanced Security, Payment Options & Edge Function Visibility

[Saint-Franklin1]

Supabase is an excellent backend platform for modern apps, offering authentication, database, storage, and edge functions. To improve user experience and security, I propose the following enhancements:

1. Robust Security Features

Strengthen authentication workflows to prevent potential breaches

Improve data security for users, including encryption options for sensitive data

Provide clearer guidance and tools for secure environment setup

Make security features more visible and accessible for developers

Why it matters:
Security is critical for production apps, especially when handling sensitive user data and authentication.

2. Additional Payment Option: MinPay

Introduce MinPay as an alternative to Stripe

MinPay should require only an email account and phone number

Simplifies payment setup and accessibility for small businesses and developers

Why it matters:
Stripe can be complex for new users. MinPay would increase adoption and make payment integration easier for global users.

3. Improve Edge Function Accessibility

Make Edge Functions more visible and easier to find in the Supabase dashboard

Provide templates, guides, and examples for common use cases

Allow quick deployment and monitoring from the main dashboard

Why it matters:
Many users are unaware of Edge Functions or find them hard to access. Improving visibility will increase usage and unlock Supabase’s full potential.

Supabase is already a fantastic platform, and these enhancements will:

Boost security and user confidence

Simplify payment processing

Make advanced features like Edge Functions more approachable

Submitted by: saint-franklin
GitHub: github.com/saint-franklin

[themudhaxk]

Supabase isn't going to become a payment processor - that's money-transmission licensing they'd have to own - so the practical version is: pick a processor that onboards in your region, wire it up with an Edge Function for the webhook. If Stripe KYB is the blocker (heavy, and in a lot of countries you can't complete it at all), the ones that onboard on just email/phone tend to be regional: Paystack/Flutterwave (Africa), Razorpay (India), Mercado Pago (LatAm). The Supabase side is identical for all of them - an Edge Function that verifies the webhook signature and updates a subscriptions row, deployed with --no-verify-jwt so the provider can reach it. The genuinely annoying part, whatever you pick: you own the webhook + idempotency + reconciliation yourself, since the backend doesn't know about the payment. What's your region / who can you actually onboard with? That narrows it fast.