Seatext library / BotRefund evidence
Why does BotRefund require affiliate platform access?
BotRefund requires affiliate platform access to perform exact payout reconciliation, matching your internal traffic data against the specific commission records generated by your affiliate network. While you can start by tracking UTM and click...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
Platform Access Unlocks the Transaction Data BotRefund Needs
Affiliate platform access provides the transaction data BotRefund needs to verify and issue refunds. Without that connection, BotRefund can detect suspicious behavior on your site but cannot confirm which commissions should actually be paid. Platform access bridges the gap between behavioral evidence and financial reality.
When you connect your affiliate network, BotRefund can pull the exact payout records. It compares those records against the click and UTM data from your own tracking script. That comparison is the core of payout reconciliation. It turns raw behavioral signals into clear approve, hold, or reject decisions.
The Exact Data Elements BotRefund Gets from Your Affiliate Platform
Platform access gives BotRefund the financial records that sit in your affiliate dashboard. These records contain specific fields needed for a precise audit. The main data elements include:
- Transaction ID: A unique identifier for each sale or signup.
- Click ID: The reference that links the commission back to the original affiliate click.
- Affiliate ID: The network account that claimed the commission.
- Commission amount: The exact payout value for that conversion.
- Conversion timestamp: When the sale or signup occurred.
- Status: Whether the commission is pending, approved, or already paid.
These data points allow BotRefund to match each commission against the behavioral evidence from your website. The tracking script captures UTM parameters, click IDs, and session behavior. Platform access pulls the final commission record. Together, they tell you whether the attribution path is clean or was manipulated.
Without platform access, you would need to manually export payout CSVs and cross-reference them by hand. That process is time-consuming and error-prone. Platform integration automates the matching and gives you a single source of truth.
A Sample Reconciliation Cycle: From Click to Payout Decision
To understand how platform access works, walk through a real payout cycle. Assume you run an online store and pay affiliates on a cost-per-sale basis. Here is a typical sequence:
- Click capture: A visitor clicks an affiliate link with a UTM code. BotRefund's tracking script logs the click ID, source, and timestamp.
- Behavior monitoring: The script observes the visitor's session. It records mouse movement, scroll depth, and time on page. Any anomalies are flagged as evidence.
- Conversion: The visitor completes a purchase. The affiliate network logs a commission and sends a transaction ID to your platform.
- Data sync: BotRefund pulls the new commission record from your affiliate platform. It now has the click ID, transaction ID, and payout amount.
- Matching: BotRefund matches the click ID from your website data to the click ID in the commission record. If they align, it proceeds to analyze the attribution path.
- Attribution analysis: BotRefund checks the timeline of events. It looks for redirects, cookie drops, or iframe calls that occurred in the final seconds before checkout. These are classic signs of hijacking.
- Decision: Based on all evidence, BotRefund assigns a status: Approve, Review, Hold, or Reject. Your team receives a report with the reasoning for each decision.
This cycle repeats for every payout period. Platform access makes the process near real-time. You no longer need to wait for manual CSV exports or worry about missing data.
Integration Limitations and Security Controls
Platform integration is powerful, but it has boundaries. BotRefund treats the connection as read-only. It does not modify your affiliate settings, change tracking pixels, or alter your commission structure. You retain full control over final payout decisions.
Most affiliate networks offer a secure API. BotRefund uses that API to retrieve payout data. The integration only reads the specific fields needed for reconciliation. It does not request access to unrelated account information. This keeps the connection focused and minimizes security risk.
Not every network exposes the same data. Some networks may lack a full API or limit the available fields. In those cases, BotRefund supports manual CSV upload as a fallback. You can still reconcile payouts, but the process becomes partially manual.
Data privacy is another consideration. BotRefund stores the minimum amount of data needed for the audit. Behavioral evidence and payout records are combined only for the purpose of detecting fraud. The system does not sell your data or use it for unrelated marketing.
How a Hijacked Commission Is Detected and Declined
Consider a practical example. A customer visits your site from a Google search ad. They browse for a few minutes and add an item to the cart. Just before checkout, a browser extension like a coupon helper activates. The extension silently sends a request to its affiliate server, dropping its own tracking cookie. The extension now claims the last-click attribution.
The sale completes, and your affiliate network records the extension as the referring affiliate. You owe a commission to that extension, even though it did not bring the customer to your site. The real driver was your Google ad.
BotRefund detects this scenario. The tracking script captures the full attribution path, including the final-second redirect. Platform access pulls the commission record that lists the extension as the affiliate. BotRefund compares the timestamps. It sees that the affiliate-only activity happened milliseconds before checkout, with no prior interaction from that affiliate. The behavioral evidence shows a normal user session with no clicks on any extension link.
BotRefund flags the commission as Reject and provides the evidence in the report. Your finance team can decline that payout with confidence. Without platform access, you would see the commission but have no way to prove it was hijacked. The transaction data from the platform is the missing piece that transforms suspicion into a documented decision.
Choosing Between CSV Upload and Platform Integration
| Feature | Manual CSV Upload | Platform Integration |
|---|---|---|
| Setup Effort | Low (requires periodic exports) | Moderate (one-time connection) |
| Reconciliation Speed | Delayed by manual processing | Near real-time or automated |
| Data Accuracy | Risk of human error | High (direct system sync) |
| Workflow | Periodic batch review | Continuous monitoring |
| Automation Level | Manual upload and mapping | Automated pull and matching |
The right choice depends on your volume and available resources. If you process fewer than a hundred commissions a month, CSV upload may be enough. For larger programs, or when you want to catch hijacking immediately, platform integration is worth the setup time.
You can start with CSV upload and move to platform access later. BotRefund is designed to work either way. The key is that you eventually get the transaction data needed for full verification.
Frequently Asked Questions
Can I use BotRefund without connecting my platform?
Yes. You can start by installing the tracking script to monitor traffic and attribution paths. You can then upload payout CSVs manually to reconcile commissions until you are ready to connect your platform.
Does BotRefund change my affiliate settings?
No. BotRefund provides evidence and recommendations. Your team retains full control over which commissions to approve or reject based on the provided audit reports.
What happens if I don't audit my affiliate payouts?
You risk "double-paying" for conversions. This happens when you pay a commission to an extension or hijacker for a sale that was already driven by your own organic or paid search efforts.
Is the integration secure?
BotRefund uses the integration to read payout data for reconciliation purposes. It does not alter your affiliate network settings or interfere with your existing tracking pixels. Access is read-only and limited to the required fields.
Does platform access guarantee every commission is correct?
Platform access provides the data needed for verification, but no system is perfect. BotRefund uses the data to detect manipulation signals. Some edge cases may require manual review, which is why the report includes a Review category.
How long does it take to connect my affiliate platform?
Setup time depends on the network. Most connections can be completed in minutes once you have API credentials. The process is a one-time configuration.
Expert perspective: In affiliate programs, the most expensive fraud is not bot clicks. It is hijacked attribution. Platform access lets you see the final commission record and match it to the user journey. That is where you catch the real losses.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
- Rewardful: Automated Refund Handling on Affiliate Payments
- Ecommerce Support in 2026: The AI Bot Should Be Doing the Refund, ...
- Affiliate programs
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.