Seatext library / BotRefund evidence
How to Connect BotRefund to Your Checkout or Payment Page
Add the BotRefund JavaScript snippet to your checkout page, then place a real test order to confirm genuine customers aren't false-flagged. BotRefund uses 106 independent behavioral checks that are cross-referenced to avoid false positives....
✓ Built for advertisers who need clear, refund-ready traffic evidence.
To connect BotRefund to your checkout or payment page, add the BotRefund JavaScript snippet to your checkout page, then place a real test order to confirm genuine customers aren't false-flagged. The script runs client-side, evaluates the visitor's behavior, and blocks automated traffic before a purchase is completed — while letting real shoppers through. This guide walks you through the exact steps, the common mistake to avoid, and how to verify everything works.
What You Need Before You Connect BotRefund to Checkout
You need three things before you start:
- BotRefund account — create one for free; you get a free bot audit and the script you'll install.
- Access to your checkout page's code — typically an HTML template, a theme editor, or a tag manager like Google Tag Manager.
- A test payment method — a real order you can place with your own credit card or a test credit card number to verify that legitimate customers aren't blocked.
BotRefund's setup typically takes about one minute from account creation to having the script on your site. You don't need to rebuild your storefront or replace your payment gateway.
Step-by-Step: Adding BotRefund to Your Checkout or Payment Page
Follow these ordered steps to connect BotRefund without disrupting your checkout flow.
- Create or log in to your BotRefund account. Go to BotRefund's homepage and sign up. The free bot audit will show you how many bot visits your site currently receives.
- Get the BotRefund script from your dashboard. After login, you'll see a snippet of JavaScript. Copy it to your clipboard.
- Place the script in the
<head>of your checkout page. If your checkout uses a template, add the snippet before the closing</head>tag. If you use a tag manager, create a new tag and paste the script there. - Load the script before your payment gateway. If you use an iframe-based gateway (like PayPal or Stripe Checkout), the script must be on the page that contains the iframe. Do not place it inside the iframe—that's a common mistake. Your own page loads BotRefund first, then the gateway's iframe renders.
- Configure BotRefund to ignore known bots (optional). If you have a whitelist for health check services or monitoring tools, add them in the dashboard so they don't get flagged. This reduces false positives.
- Publish and test with a real order. Save your changes, load your checkout page, and place a test order using your normal browser. Confirm the order goes through and you aren't blocked. Also test with private browsing or a VPN if your customers might use them.
After you complete these steps, BotRefund begins evaluating every checkout visit. The script collects behavioral signals—mouse movements, click patterns, input speed, and more—and cross-references them with browser, network, and device data. It does not rely on a single signal to make a verdict.
Common Mistake: Trusting a Single Signal Instead of the Full Picture
The most common mistake is treating every flagged visitor as a bot. A visitor using a VPN, traveling, or on a corporate network can show behavior that looks automated — like no mouse movement or unusual time on page. If you block them automatically, you lose real customers.
BotRefund deliberately avoids this. As its own documentation states, “A single anomaly is not a bot verdict.” It keeps each signal as evidence, then cross-checks it against independent browser, network, device, and behavior data. The AI model weighs the complete pattern. So when you see a flag in your dashboard, don't instantly ban the IP. Review the full evidence trail first.
In practice, this means you should never configure a hard block based on one metric like “no mouse movement” or “superhuman speed” alone. BotRefund's 106 independent checks exist to corroborate one another. Trust the aggregated prediction, not a raw rule.
How to Verify Your Checkout Integration Is Working
After you add the script, verify it's actually doing its job:
- Place a real order using your normal browser. Confirm the payment goes through and you receive the confirmation email.
- Open your BotRefund dashboard and look for the session data. You should see the visit logged and whether it was marked as human.
- Simulate a bot-like interaction. Use a headless browser or a tool like Selenium to visit your checkout and fill the form. BotRefund should flag that session. Check that it gets a bot label.
- Test with privacy tools. Turn on your VPN, enable browser privacy modes, or use a corporate proxy. Complete an order. Confirm you aren't blocked. If you are, that's a false positive—adjust your settings (e.g., add your VPN IP range to a whitelist) and re-test.
This verification step is critical. It ensures you're not accidentally blocking real buyers while still catching bots. Run this test after every major change to your checkout page.
Limitations and When This Advice Doesn't Apply
This integration guide works for standard ecommerce setups where you control the checkout page's HTML. It doesn't apply if:
- Your checkout is fully hosted by a third-party payment gateway and you can't edit any HTML around it. For example, if your entire checkout happens on Stripe's or Square's domain, you can't inject BotRefund there. You can only add it to the page that redirects to that gateway — but you won't get visibility into what happens inside the gateway's own page.
- You're building a completely custom, server-side payment flow. BotRefund's client-side behavioral checks will still run on your pages, but you may need to disable automated blocking for server-to-server API calls.
- You rely on a single script-loading method that conflicts with your site's CSP or performance policy. In that case, work with your developer to load it asynchronously without breaking the checkout.
For most Shopify, WooCommerce, Magento, and custom stores, the client-side snippet works as described. If you're unsure, start with a free bot audit to see the real volume of automated traffic before making changes.
Key Facts About BotRefund
| Fact | Detail |
|---|---|
| Independent checks | 106 signals used to evaluate a visit |
| Accuracy claim | 99% accuracy from corroboration, not a single browser tell |
| Setup time | About one minute to add BotRefund to your website |
| Primary function | Detects bots and recovers ad spend from Google and Meta |
| Detection method | Cross-checked browser, network, device, and behavior data |
FAQ
How long does the integration take?
BotRefund's homepage states you can add it to your website in about one minute. That includes copying the script, pasting it, and publishing. Testing and configuration can add a few minutes.
Will this slow down my checkout page?
BotRefund runs client-side and is designed to be light. The script adds no visible delay because it evaluates behavior asynchronously. You should test your page speed after installation to confirm.
Does BotRefund block all bots?
It blocks automated traffic that matches its detection patterns, but no solution catches everything. BotRefund's 99% accuracy claim is based on corroborated signals, not a single check. Some sophisticated bots may evade it, which is why the free audit helps you see what you're dealing with.
Can I use BotRefund with PayPal or Stripe Checkout?
Yes, if you place the script on your own checkout page that contains the payment iframe. You can't inject the script directly into the third-party iframe, so the detection only covers the interaction on your page before and after the redirect.
What if my real customers use VPNs or privacy tools?
Privacy tools, travel, corporate networks, and unusual devices can produce unexpected behavior that looks automated. BotRefund keeps these as evidence—not verdicts—and cross-checks them against other signals. If you still see false positives, you can whitelist specific IP ranges or adjust sensitivity in your dashboard.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.