GoKwik Checkout Redirecting to Native WooCommerce Checkout

? Overview

In some cases, when users click on “Buy Now” or “Proceed to Checkout”, they may get redirected to the default WooCommerce checkout instead of the GoKwik checkout.

This typically happens due to caching layers, Cloudflare restrictions, or integration conflicts that block GoKwik scripts from executing properly.

? Common Causes

1. Caching Interference

• Plugin-level caching (e.g., WP Rocket, LiteSpeed, etc.)
• Server-level caching
• CDN caching (Cloudflare, etc.)

2. Cloudflare Security Restrictions

• Bot Fight Mode enabled
• Firewall rules blocking GoKwik requests
• Proxy/CDN interfering with JS execution

3. Script Blocking / JS Issues

• GoKwik script not loading properly
• Theme conflicts overriding checkout behavior
• Custom “Buy Now” button not mapped to GoKwik

4. IP Blocking / Firewall Restrictions

• Hosting provider blocking GoKwik IPs

? Recommended Fix

Please follow the steps below:

✅ Step 1: Clear All Caches

• Clear plugin cache
• Clear server cache
• Purge CDN cache (Cloudflare, etc.)

✅ Step 2: Update Cloudflare Settings

If you are using Cloudflare:

• Disable Bot Fight Mode
• Ensure:
  • No aggressive caching on /cart and /checkout
  • JavaScript is not blocked

✅ Step 3: Whitelist GoKwik IPs

Add the following IPs in your hosting / firewall / Cloudflare allowlist:

• Sandbox (Testing): 13.200.124.145
• Production (Live): 52.66.34.242

✅ Step 4: Basic Browser Validation

• Clear browser cache
• Test in Incognito mode
• Try a different browser/device

✅ Step 5: Verify Button Behavior

• Ensure “Buy Now” / “Proceed to Checkout” is not overridden by theme/custom code
• Check that GoKwik script is properly integrated

? Expected Outcome

After applying the above steps:

✅ GoKwik checkout should trigger correctly

❌ No redirection to WooCommerce checkout

? If Issue Persists

Please share the following details with the support team:

• Affected product URLs
• Screen recording of the issue
• Any recent theme/plugin changes
• Confirmation of Cloudflare/cache settings

? Notes

• This issue is most commonly caused by Cloudflare or caching layers
• Resolving these usually fixes the issue immediately