The backend 400 error is separate — your backend at                                    
                                                                                         
  https://mayadev.mayaresearch.ai/api/v5/payment/google-play/verify is rejecting the     
  verification. That needs to be fixed on the backend side (likely Google Play service   
account                                                                                  
  credentials not configured on prod).                                                   

⏺ The 400 means the request did reach the backend but verification failed. Let me check
  what could cause a 400 on the verify endpoint:                                        
                                                                                         
  Read 1 file (ctrl+o to expand)    
                                                                                         
⏺ The 400 comes from result["error"]. The possible error messages from                 
  verify_google_play_purchase are:                                                       
                                                                                         
  1. "Could not verify Google Play purchase" — both v2 and v1 API calls failed (service  
  account issue)                                                                         
  2. "Subscription status: {status}" — verified but status not in PREMIUM_STATUSES       
  3. "No plan found for product: {product_id}" — product_id doesn't match any plan in DB 
  4. "Failed to create subscriptions" — DB insert failed                                 
                                                                                         
  Most likely it's #1 — service account credentials not on prod. Let me check what's     
  needed:                                                                                
                                                                                         
  Searched for 1 pattern, read 1 file (ctrl+o to expand)                               
                                                  
⏺ That's the issue. On your prod cluster, you need:
                                                                                        
  1. google-play-service-account.json file deployed alongside the app (or mounted as a   
  secret)                                      
  2. GOOGLE_PLAY_PACKAGE_NAME env var set correctly (defaults to com.india.mayaai — is   
  that your package name?)                                                               
                                                                                         
  Check on your prod cluster:                                                            
  - Is google-play-service-account.json present in the container?                        
  - Are the env vars GOOGLE_PLAY_PACKAGE_NAME and GOOGLE_PLAY_CREDENTIALS_PATH set?      
                                                                                       
  If you're using Kubernetes, you'd typically mount the service account JSON as a secret.
   Without it, the Google API call fails and you get the 400 "Could not verify Google    
  Play purchase".                                                                        
                                                                                         
─────────────────────────────────────────────────────────────────────────────────────────
❯                                                                                       
─────────────────────────────────────────────────────────────────────────────────────────
  ⏵⏵ bypass permissions on (shift+tab to cycle)                  10% until auto-compact