CODARAB Redirect is a WooCommerce plugin that automatically moves buyers from a high risk store to the checkout page of a separate low risk site, protecting your PayPal, Stripe, or any other payment processor from suspension or permanent bans. When your primary domain is flagged or blacklisted, CODARAB Redirect keeps sales flowing without the customer ever noticing the switch. This article explains exactly how CODARAB Redirect works, its seven core redirection methods, and why high risk merchants rely on it as a long term payment protection strategy.
- CODARAB Redirect sends customers from a high risk WooCommerce store to the checkout of a clean, low risk second site.
- It supports three immediate redirect triggers: Add to Cart, Proceed to Checkout, and custom payment method selection.
- Orders are synced automatically and instantly between both sites so inventory and status stay consistent.
- Customers receive all order status emails only from the main high risk store, preserving a professional brand experience.
- An iFrame option lets the low risk checkout appear visually inside the high risk domain, hiding the redirect entirely.
- Product names are replaced with order numbers on payment receipts, preventing keyword-based detection by processor robots.
- CODARAB Redirect works alongside CODARAB Payments, Stripe, or any other processor on the second site.
- The iFrame feature is the most powerful cloaking method because the buyer never sees a domain change.
- Replacing product names with order IDs on receipts is a critical step for IPTV, digital goods, and high copy sellers.
- You need two WordPress sites to use CODARAB Redirect: one high risk and one low risk.
- Automatic order synchronization means you manage everything from one dashboard without manual data entry.
- If your domain is already on a payment processor blacklist, CODARAB Redirect is the recommended complementary solution to CODARAB Payments.
- What Is CODARAB Redirect and Why Do High Risk Merchants Need It?
- How CODARAB Redirect Works: The Two-Site Architecture
- The 3 Immediate Redirect Triggers Explained
- iFrame Checkout Cloaking: Staying on Your Domain
- Automatic Order Synchronization Between Two WooCommerce Sites
- Order Notifications: Keeping Customers Informed from One Store
- Hiding Product Names on Payment Receipts
- CODARAB Redirect vs CODARAB Payments: Which Do You Need?
- Prerequisites and Setup Requirements
- Common Mistakes High Risk Merchants Make Without a Redirect Solution
- Frequently Asked Questions
What Is CODARAB Redirect and Why Do High Risk Merchants Need It?
CODARAB Redirect is a WooCommerce plugin developed by CODARAB that solves one of the most persistent problems for high risk online sellers: getting banned or suspended by payment processors simply because of what they sell. The plugin redirects buyers from Site 1 (the high risk store) to the checkout page of Site 2 (a clean, low risk store), processing the payment there without exposing the risky domain to the processor.
Payment processors like PayPal and Stripe use automated systems, including Webhook monitoring, to scan domain names and product keywords. When your domain appears on a blacklist, even a well-configured payment gateway will trigger a ban. CODARAB Redirect bypasses this by routing the actual transaction through a domain that has no negative history.
This solution is particularly valuable for merchants selling IPTV subscriptions, digital products, peptides, high copy goods, or dropshipping items that standard processors classify as high risk. Instead of losing your account and your revenue overnight, you keep selling with zero interruption.
How CODARAB Redirect Works: The Two-Site Architecture
CODARAB Redirect operates on a dual-site model where Site 1 is your public-facing high risk store and Site 2 is a separate, clean WooCommerce installation that handles the actual payment processing. The customer browses and adds products on Site 1, but the checkout and payment happen on Site 2, either visibly via a redirect or invisibly via an iFrame.
Site 2 can use any payment processor you choose: CODARAB Payments, Stripe, or another gateway. Because Site 2 has a neutral domain name and no high risk product keywords exposed to the processor, it maintains a clean account status. The processor never sees the risky domain or product names from Site 1.
Here is the core flow:
This architecture means your payment processor account on Site 2 stays protected because it only ever processes orders from a neutral domain. The high risk branding, product names, and domain remain completely invisible to the processor.
CODARAB Redirect is designed to work transparently. Customers complete their purchase without confusion, and merchants manage everything from a single dashboard thanks to automatic order synchronization.
The 3 Immediate Redirect Triggers Explained
CODARAB Redirect offers three distinct trigger points that give merchants precise control over when and how customers are redirected from the high risk site to the low risk checkout. Each trigger serves a different checkout flow scenario.
Trigger 1: Add to Cart, Buy Now, or Order Now Button
When a customer clicks Add to Cart, Buy Now, or Order Now on Site 1, CODARAB Redirect immediately sends them to the checkout page of Site 2. This is the most aggressive redirect option and is ideal for stores where you want to minimize the time a customer spends on Site 1 before reaching the payment step.
It reduces cart abandonment by taking the buyer directly to the payment form. This trigger works well for single-product stores or stores where each product has a dedicated landing page.
Trigger 2: Proceed to Checkout Button
With this trigger, CODARAB Redirect waits until the customer clicks the Proceed to Checkout button in the WooCommerce cart. This allows the customer to review their cart on Site 1 before being redirected to Site 2 for payment.
This is the most balanced option for stores with multiple products, as it preserves the normal shopping experience before the redirect occurs. For more background on this subject, see WooCommerce official documentation.
Trigger 3: Custom Payment Method Selection
This trigger activates CODARAB Redirect when a customer selects a specific custom payment method on the checkout page of Site 1. This is the most nuanced option and is useful when you want to offer multiple payment routes, routing only certain methods through Site 2 while keeping others on Site 1.
For example, you could route card payments through Site 2 while keeping a cash-on-delivery option active on Site 1 without any redirect.
| Redirect Trigger | When It Fires | Best Use Case |
|---|---|---|
| Add to Cart / Buy Now | Immediately on product page click | Single-product stores, fast checkout flows |
| Proceed to Checkout | After cart review | Multi-product stores, standard shopping experience |
| Custom Payment Method | On payment method selection at checkout | Mixed payment routing, selective redirection |
iFrame Checkout Cloaking: Staying on Your Domain
CODARAB Redirect includes an iFrame cloaking feature that is arguably its most powerful capability for protecting payment accounts. Instead of redirecting the customer to Site 2 visibly, the checkout page of Site 2 is loaded inside an iFrame embedded on Site 1, so the customer sees their own domain in the browser address bar throughout the entire checkout process.
From the customer’s perspective, they are on highrisk.com/checkout. But the payment form they interact with is actually served from lowrisk.com. The processor only ever communicates with the low risk domain and has no visibility into the high risk domain at all.
This approach delivers two major benefits:
- Account protection: The payment processor never detects the high risk domain because it only processes requests from the low risk domain.
- User experience: Customers are never confused by a sudden domain change, which reduces checkout abandonment and builds trust.
The iFrame method is recommended for merchants whose high risk domain is already on a watchlist or who operate in highly scrutinized niches such as IPTV, digital subscriptions, or replica goods. You can learn more about the technical setup in the WooCommerce Checkout Inside iFrame guide.
Automatic Order Synchronization Between Two WooCommerce Sites
CODARAB Redirect synchronizes orders automatically and in real time between Site 1 and Site 2, so merchants never need to manually reconcile two separate order databases. The moment a payment is confirmed on Site 2, the corresponding order is created and updated on Site 1 instantly.
This synchronization covers all WooCommerce order statuses: Processing, Completed, Canceled, On Hold, and Failed. When the order status changes on Site 2, the change is reflected on Site 1 without any manual intervention.
The practical benefit is significant. You manage your business from the Site 1 dashboard as if the redirect never happened. Customer service, fulfillment, and reporting all happen in one place. There is no risk of a customer receiving conflicting information because both sites always show the same order state.
For merchants running high volume operations, this real-time sync prevents the operational chaos that would result from manually managing two separate order systems. The WooCommerce Order Sync Plugin documentation covers the technical details of how this synchronization is implemented.
Order Notifications: Keeping Customers Informed from One Store
CODARAB Redirect ensures that customers receive all order notifications exclusively from Site 1, the main high risk store, regardless of where the payment was actually processed. This design decision is critical for maintaining a professional and coherent brand experience.
Without this feature, a customer could receive duplicate emails: one from Site 1 and one from Site 2. This would immediately raise suspicion, confuse the customer, and potentially reveal the two-site architecture to both the customer and the payment processor.
By centralizing all communications through Site 1, the customer journey remains seamless from browsing to post-purchase. They receive the standard WooCommerce order confirmation, processing, and completion emails from the brand they recognize, with no indication that their payment was processed on a different domain.
This is especially important for subscription-based businesses such as IPTV providers, where recurring billing notifications and renewal reminders must come from a consistent source to avoid customer confusion and disputes.
Hiding Product Names on Payment Receipts
One of the most overlooked but strategically important features of CODARAB Redirect is its ability to replace product names with WooCommerce order numbers on payment receipts. Instead of showing the actual product name on the PayPal or Stripe receipt, the plugin displays only the order ID in the format Order#1234.
This matters because payment processor systems and automated robots scan receipt data for keywords associated with high risk categories. If a receipt shows “IPTV Monthly Subscription” or “High Copy Nike Shoes,” the processor’s algorithm can flag and suspend the account even if the transaction itself was legitimate.
By replacing product names with neutral order numbers, CODARAB Redirect removes the keyword signal entirely. The processor sees a generic order reference with no indication of what was sold. This significantly extends the lifespan of the payment account on Site 2.
This feature mirrors the same product name masking available in CODARAB Payments, ensuring consistent protection across both solutions. For a deeper look at how this works technically, see the article on replacing WooCommerce product names with order numbers.
CODARAB Redirect vs CODARAB Payments: Which Do You Need?
CODARAB Redirect and CODARAB Payments are complementary solutions that address different layers of the high risk payment problem. Understanding the difference helps you choose the right tool or combine both effectively.
CODARAB Payments is a WooCommerce payment gateway built on the PayPal API. It allows you to accept international card payments without the yellow PayPal button, hide product names on receipts, and convert PayPal earnings to USDT via RedoPay. It works on a single site and is ideal when your domain is not yet blacklisted.
CODARAB Redirect is the solution for when your domain is already flagged or when you want a proactive second layer of protection. It routes transactions through a clean second site, making the high risk domain completely invisible to the processor.
| Feature | CODARAB Payments | CODARAB Redirect |
|---|---|---|
| Payment processor | PayPal API (card processing) | Any processor on Site 2 |
| Number of sites required | 1 | 2 |
| Domain blacklist protection | Partial (via name masking) | Full (domain never exposed) |
| iFrame cloaking | No | Yes |
| Order sync | N/A | Yes, real-time |
| Product name masking | Yes | Yes |
| Best for | New or clean domains | Flagged domains or maximum protection |
Many merchants use both solutions together: CODARAB Payments on Site 2 as the payment processor, and CODARAB Redirect on Site 1 to route customers there. This combination provides the deepest level of account protection available. The CODARAB Pay vs CODARAB Redirect comparison covers this in detail.
Prerequisites and Setup Requirements
Before installing CODARAB Redirect, you need to have two functional WordPress and WooCommerce installations ready. Site 1 is your main high risk store where customers browse and shop. Site 2 is a clean, low risk store with a neutral domain name and an active payment processor account.
The requirements for each site are straightforward:
- Site 1 (High Risk): A WordPress site with WooCommerce installed and the CODARAB Redirect plugin activated. This is where your products are listed and where customers arrive.
- Site 2 (Low Risk): A WordPress site with WooCommerce installed and a payment processor configured. You can use CODARAB Payments, Stripe, or any other gateway. The domain should have no history of high risk activity.
For the iFrame option, Site 2’s checkout page must be configured to allow embedding in an iFrame. The Clean WooCommerce Checkout for iFrame Cloaking guide explains how to strip unnecessary elements from the Site 2 checkout to create a seamless embedded experience.
If you do not yet have a professional WordPress site, CODARAB offers web development services that include full setup, payment gateway integration, and SEO optimization at competitive rates. You can contact them directly through codarab.com.
Common Mistakes High Risk Merchants Make Without a Redirect Solution
High risk merchants who skip a redirect solution like CODARAB Redirect often repeat the same costly mistakes. Understanding these pitfalls helps you appreciate why a structured two-site approach is necessary rather than optional.
Mistake 1: Using the Same Domain for All Payment Attempts
After a payment account ban, many merchants simply open a new account with the same processor and connect it to the same domain. The processor’s Webhook system detects the domain within days and bans the new account as well. CODARAB Redirect avoids this by never exposing the flagged domain to the processor.
Mistake 2: Displaying Real Product Names on Receipts
Merchants who do not mask product names on receipts give the processor’s automated systems a direct signal about what is being sold. Terms like “IPTV,” “replica,” or “peptide” in a receipt are enough to trigger an automated review and suspension. CODARAB Redirect’s order number replacement feature eliminates this risk entirely.
Mistake 3: Sending Customers to an Unfamiliar Domain Without Cloaking
A visible redirect to an unknown domain at checkout creates immediate distrust. Conversion rates drop sharply when customers see a domain they do not recognize just before entering their card details. The iFrame feature in CODARAB Redirect solves this by keeping the familiar domain visible throughout the entire checkout process. For more background on this subject, see PayPal merchant account information.
Mistake 4: Managing Two Order Databases Manually
Without automatic sync, merchants must manually copy order data between Site 1 and Site 2. This leads to errors, delays in fulfillment, and poor customer experiences. CODARAB Redirect’s real-time synchronization eliminates this operational burden entirely.
Frequently Asked Questions
What exactly does CODARAB Redirect do?
CODARAB Redirect is a WooCommerce plugin that routes customers from a high risk store to the checkout page of a separate low risk site for payment processing. It protects your payment processor account by ensuring the risky domain is never exposed to PayPal, Stripe, or any other gateway during the transaction.
Do I need two websites to use CODARAB Redirect?
Yes. CODARAB Redirect requires two WordPress and WooCommerce installations. Site 1 is your main high risk store where customers browse. Site 2 is a clean, low risk store that handles the actual payment. Both sites must be active and accessible for the plugin to function correctly.
Which payment processors work with CODARAB Redirect on Site 2?
CODARAB Redirect is compatible with any payment processor you install on Site 2, including CODARAB Payments, Stripe, and other WooCommerce-compatible gateways. The plugin itself is processor-agnostic. CODARAB Payments is the recommended option for Site 2 because it provides additional protection features like product name masking and dispute reduction.
Can customers tell they are being redirected to another site?
With the iFrame option enabled, customers cannot tell they have been redirected. They see the high risk domain in their browser address bar throughout the entire checkout. Without iFrame, there is a visible domain change when they reach the checkout page of Site 2. Most merchants use the iFrame option to maintain a seamless experience.
How does order synchronization work between the two sites?
When a payment is confirmed on Site 2, CODARAB Redirect automatically creates and updates the corresponding order on Site 1 in real time. All order status changes, including Processing, Completed, Canceled, and On Hold, are reflected on Site 1 immediately without any manual action required from the merchant.
Will customers receive emails from both sites?
No. CODARAB Redirect is designed so that all order notifications are sent exclusively from Site 1, the main store. Customers receive only one set of emails from the brand they recognize. This prevents confusion and avoids revealing the two-site architecture to customers or payment processors.
Why does CODARAB Redirect replace product names with order numbers?
Payment processors use automated systems that scan receipt data for keywords associated with high risk categories. By replacing product names with neutral order numbers like Order#1234, CODARAB Redirect removes any keyword signal from receipts. This prevents the processor’s robot from detecting and flagging the account based on what is being sold.
Is CODARAB Redirect a replacement for CODARAB Payments?
No. They are complementary solutions. CODARAB Payments is a payment gateway for a single site and works best when the domain is not yet blacklisted. CODARAB Redirect is an additional layer of protection that routes transactions through a second clean site. Many merchants use both together for maximum account protection.
What happens if my high risk domain is already on a payment processor blacklist?
If your domain is already blacklisted, CODARAB Payments alone may not be sufficient because the processor detects the blacklisted domain via Webhook. CODARAB Redirect solves this by routing all transactions through Site 2, which has a clean domain that is not on any blacklist. The high risk domain never appears in the payment processor’s system.
Where can I see a live demonstration of CODARAB Redirect?
CODARAB provides a live demonstration of the redirect solution at dev.wpchatbox.com. You can also visit codarab.com/redirect for pricing details. CODARAB also uses its own redirect solution on the codarab.com checkout page, which serves as both a live implementation and a demonstration of the technology in production.
CODARAB Redirect is the most complete checkout protection strategy available for high risk WooCommerce merchants who need to keep selling without losing their payment processor accounts. Whether you are dealing with an already-flagged domain or simply want to build a proactive two-site safety net, CODARAB Redirect provides the iFrame cloaking, real-time order sync, and product name masking your business needs. To get started with a full setup or to explore how CODARAB Redirect and CODARAB Payments work together, visit the official CODARAB Redirect Plugin page for complete documentation and pricing.