Paynow API Access – Supabase IP Restrictions & Recommended Workaround

Paynow API Access – Supabase IP Restrictions & Recommended Workaround

Please note that some Supabase IP addresses used by Paynow integrations have been blocked due to abuse by other merchants.

Because platforms like Supabase and Firebase use shared IP infrastructure, certain merchants were making excessive or improper requests (e.g., continuously polling transaction status), which led to those shared IPs being blocked.

As a result, Paynow is unable to selectively unblock individual users on those shared IPs.

Recommended Workaround

To avoid this issue, you can use one of the following approaches:

  1. Use a dedicated static IP address, or
  2. Proxy all Paynow API calls through your own VPS (e.g., Contabo or any hosting provider)

Suggested Flow

  • Your Supabase Edge Function should call your VPS endpoint
  • Your VPS then forwards the request to Paynow
  • The response is returned back through the same path

The key point is that the VPS provides a static, dedicated IP, unlike Supabase.

Important Clarification

  • Only IPs that have shown abusive behavior are blocked
  • Paynow does not block international IPs by default
  • The restriction is based on traffic patterns and misuse, not location