Go Developer for Stable Lieferando Checker Fix (409 Conflict, Fingerprint, PKCE...)

We just received a new potential client request and we’re looking for experienced Go developers who want to take this on.
The client already has a Golang-based Lieferando.de checker that works for a few lines but becomes unstable due to multiple issues. After a short run, different conflicts stack on top of each other until Lieferando blocks the entire flow.
🔧 Technical Issues to SolveThe current checker suffers from:

1. Missing / static browser fingerprint headers
   
2. Repeated PKCE state & returnUrl values
   
3. Turnstile + rate limit triggers due to:
   • solves happening too fast
     
   • same fingerprint reused
     
   • too many requests too quickly
     
4. Proxy/TLS mismatch that Lieferando detects, causing conflicts
   

🔨 Required FixesA stable solution must:

• Implement dynamic browser fingerprints
  
• Fix PKCE state + returnUrl generation
  
• Add timing & pacing between requests
  
• Adjust the Turnstile handling flow
  
• Improve proxy validation & rotation
  

Once these are addressed, the checker should run consistently without 409 conflicts or flow interruptions.

---

📩 Freelancers: How to ApplyIf you’re able to handle this:
👉 Reply with:

• Your approach
  
• Your quote
  
• Your timeline / delivery estimate
  

👉 Then DM me directly or join BrandForge and message @Mxstermind:
🌐 https://brandforge.gg
💬 Telegram: https://t.me/brandforge_gg
🟣 Discord: https://discord.gg/brandforge