Fix Geo Proxy Payment Redirects

I already route checkout traffic for the Geidia payment gateway through an iframe-based IP proxy so the request appears to originate from my VPS’s static address. That lets the initial payment page load, but once the JavaScript-based redirects kick in for 3-DS and the final callback, the flow escapes the tunnel and the gateway never notifies my Laravel callback URL. I need a clean, fully isolated solution that: • keeps every redirect—including the 3-DS challenge—inside the proxy path • forces the gateway to see only the server’s fixed public IP, never the shopper’s browser IP • returns the gateway’s success or failure response to my Laravel controller without breaking session or CSRF tokens You’ll be free to choose the most reliable approach— a dedicated redirect micro-service, or another method—as long as the logic stays transparent to my existing Blade views and doesn’t require customers to install extensions. Acceptance criteria 1. A shopper in a geo-blocked region completes a live card payment and reaches my “Thank You” page. 2. Laravel receives the signed callback payload and records the transaction. 3. All steps can be replayed from server logs showing a single source IP (the VPS). If you have solid experience with Laravel, reverse proxies, and payment gateway edge cases, let’s get this locked down.