The CODARAB Redirect setup is the most reliable method for high-risk WooCommerce merchants who need to route customers from a flagged domain to a clean checkout page without losing sales or exposing their payment processor to risk. This guide walks you through the complete two-site configuration, covering every option the plugin offers so you can go live with confidence.
- CODARAB Redirect setup connects a high-risk Site 1 to a low-risk Site 2 for seamless payment processing.
- Three redirection trigger options: Add to Cart button, Proceed to Checkout button, or custom payment method selection.
- Orders are synchronized automatically and instantly between both WooCommerce stores.
- Customers receive all email notifications exclusively from Site 1, preserving brand consistency.
- An iFrame option keeps the low-risk checkout visible inside the high-risk domain URL.
- Product names are replaced by order numbers on PayPal receipts to prevent keyword-based account flags.
- You need two separate WordPress/WooCommerce installations before starting the CODARAB Redirect setup.
- Site 2 (low-risk) must have a working payment processor: CODARAB Payments, Stripe, or another gateway.
- The plugin protects accounts even when the high-risk domain is already on a payment processor blacklist.
- iFrame cloaking lets buyers complete payment on Site 2 while the browser URL still shows Site 1.
- Order name masking replaces sensitive product keywords with a neutral order ID on every receipt.
- Pricing and licensing details for CODARAB Redirect are published at codarab.com/redirect.
- What Is CODARAB Redirect and Why High-Risk Merchants Need It
- Prerequisites Before Starting the CODARAB Redirect Setup
- How the Three Redirection Trigger Options Work
- Step-by-Step CODARAB Redirect Setup: Two-Site Configuration
- iFrame Checkout Cloaking: Keeping Customers on Your Domain
- Automatic Order Synchronization Between Site 1 and Site 2
- Order Name Masking: Replacing Product Names with Order Numbers
- Email Notifications and Customer Experience Management
- Comparing CODARAB Redirect Setup Options at a Glance
- Common Configuration Mistakes and How to Avoid Them
- Frequently Asked Questions
What Is CODARAB Redirect and Why High-Risk Merchants Need It
The CODARAB Redirect setup solves a specific problem: your high-risk domain is already known to payment processors, and any transaction routed through it triggers an automatic review or account suspension. The plugin redirects buyers from Site 1 (high-risk) to the checkout page of Site 2 (low-risk) where a clean payment processor handles the transaction.
This approach is fundamentally different from simply switching gateways. Even if you install a new payment method on a flagged domain, the processor’s webhook system can still detect the domain name and flag the account. By processing payments on a separate, neutral domain, you break that detection chain entirely.
CODARAB developed this solution as a direct complement to CODARAB Payments. While CODARAB Payments hides product names and disables the PayPal yellow button, the Redirect plugin goes further by physically separating the storefront domain from the payment domain.
Prerequisites Before Starting the CODARAB Redirect Setup
A successful CODARAB Redirect setup requires specific infrastructure in place before you install a single plugin file. Skipping any prerequisite will cause the synchronization or redirection to fail silently.
What You Need on Site 1 (High-Risk Store)
- A live WordPress and WooCommerce installation on your high-risk domain.
- Products already published with standard WooCommerce product pages.
- The CODARAB Redirect plugin installed and activated.
- An API key generated inside the plugin settings to connect to Site 2.
What You Need on Site 2 (Low-Risk Store)
- A separate WordPress and WooCommerce installation on a clean domain with no payment processor history.
- A working payment gateway: CODARAB Payments, Stripe, or any other processor you prefer.
- The companion CODARAB Redirect receiver plugin installed and activated.
- SSL certificate active on the domain (required for iFrame embedding).
If you do not yet have a professional WordPress store, CODARAB offers development services at competitive rates. You can contact the team directly through this guide on setting up a low-risk WooCommerce backup store to understand the architecture before commissioning the build.
How the Three Redirection Trigger Options Work
The CODARAB Redirect setup gives you three distinct moments at which the redirect can fire, each suited to a different user experience goal. Choosing the right trigger is critical to minimizing cart abandonment.
Trigger A: Add to Cart, Buy Now, or Order Now Button
When a visitor clicks any purchase-intent button on Site 1, they are immediately sent to the checkout page of Site 2. This is the most aggressive option and works well when you want to minimize the number of steps between product discovery and payment.
The risk with this trigger is that buyers who want to add multiple products before checking out may feel rushed. Use it for single-product stores or for stores where each product is purchased individually.
Trigger B: Proceed to Checkout Button
The redirect fires only when the buyer clicks the cart page button to move to checkout. This preserves the standard WooCommerce shopping experience on Site 1 and only switches domains at the final step.
This is the most balanced option for stores with multiple products in a single order. Customers browse and add items normally on Site 1, then complete payment on Site 2.
Trigger C: Custom Payment Method Selection
The redirect fires when a buyer selects a specific payment method on the Site 1 checkout page. This allows you to offer multiple payment options, routing only certain methods through Site 2 while keeping others local.
This trigger is particularly useful when you have some low-risk products that can be processed directly on Site 1 and other high-risk items that must go through Site 2. For more background on this subject, see WooCommerce official documentation.
Step-by-Step CODARAB Redirect Setup: Two-Site Configuration
Follow this CODARAB Redirect setup sequence precisely to avoid synchronization errors between your two WooCommerce stores.
For a deeper look at how the synchronization layer works technically, see the CODARAB order sync between two WooCommerce stores guide.
iFrame Checkout Cloaking: Keeping Customers on Your Domain
The iFrame feature in the CODARAB Redirect setup is what separates this plugin from a simple URL redirect. Instead of sending the buyer to a visibly different domain, the Site 2 checkout page loads inside an iFrame embedded on the Site 1 checkout URL.
From the buyer’s perspective, they never leave your high-risk domain. The browser address bar continues to show your Site 1 URL throughout the entire payment process. This eliminates the trust gap that occurs when a customer notices they have been sent to an unfamiliar domain.
Technical Requirements for iFrame Mode
- Site 2 must serve pages over HTTPS. Mixed content will break the iFrame.
- Site 2 must not send an
X-Frame-Options: DENYorSAMEORIGINheader. Configure your server or hosting panel to allow framing from Site 1’s domain. - Site 1 must have a clean WooCommerce checkout template without conflicting header or footer scripts that could interfere with the embedded form.
The WooCommerce checkout inside iFrame guide on the CODARAB blog covers the server-side header configuration in detail.
When iFrame mode is active, customers see your Site 1 branding, your Site 1 URL, and a checkout form that is actually served from Site 2. This is the most seamless user experience the plugin can deliver and the hardest configuration for payment processors to detect.
Automatic Order Synchronization Between Site 1 and Site 2
The CODARAB Redirect setup includes a real-time order synchronization engine that pushes order data between both stores the moment a payment is confirmed on Site 2. No manual intervention or cron job is required.
What Gets Synchronized
- Order ID and total amount.
- Customer billing and shipping details.
- Product line items (with masked names if that option is active).
- Order status changes: Processing, Completed, On Hold, Cancelled, Failed.
What Stays Separate
- Payment processor credentials and API keys remain on Site 2 only.
- Customer payment card data never touches Site 1.
- Site 2 order notifications are suppressed so buyers only receive emails from Site 1.
This separation is intentional. The goal is to make Site 1 the single source of truth for the customer relationship while Site 2 handles only the financial transaction. Learn more about the notification management approach in the WooCommerce order status sync guide.
Order Name Masking: Replacing Product Names with Order Numbers
One of the most valuable features included in the CODARAB Redirect setup is the ability to replace product names with neutral order numbers on every PayPal receipt and transaction record.
Payment processors, including PayPal, scan the item name fields in transaction data. If your product names contain keywords associated with high-risk categories such as IPTV, peptides, high-copy goods, or adult content, the processor’s automated system can flag your account without any human review.
How the Masking Works
Instead of transmitting the literal product name, the plugin sends a neutral string such as Order #1234 as the item description. The actual product details remain inside your WooCommerce order on Site 1, visible to you and your team, but invisible to the payment processor.
This feature mirrors what CODARAB Payments already does for merchants using that gateway directly. When combined with the two-site redirect architecture, you get double protection: the domain is clean and the transaction data contains no incriminating keywords.
For merchants who need this feature without the full two-site setup, see the dedicated article on replacing WooCommerce product names with order numbers.
Email Notifications and Customer Experience Management
A well-executed CODARAB Redirect setup is invisible to the customer. They should never receive a confusing email from an unfamiliar domain or see any indication that two separate stores are involved in their purchase.
Email Configuration Rules
- Disable all WooCommerce transactional emails on Site 2. Only Site 1 should send order confirmation, processing, and completion emails.
- Configure Site 1 to send emails using your brand name and domain email address via SMTP for reliable delivery.
- Test every order status transition to confirm that only one email arrives per status change and that it comes from Site 1.
Order Status Flow from the Customer’s View
The customer places an order on Site 1 (or via the iFrame on Site 1). Payment is processed on Site 2. Site 2 triggers an order status update that syncs back to Site 1. Site 1 sends the customer a branded email with the correct status. The customer never learns that Site 2 exists.
This design protects both the merchant’s operational security and the buyer’s trust. A confused customer who receives emails from two different domains is far more likely to open a dispute, which is exactly what this architecture is designed to prevent.
Comparing CODARAB Redirect Setup Options at a Glance
The CODARAB Redirect setup offers multiple configuration combinations. The table below summarizes the key options so you can choose the right combination for your business model.
| Feature | Trigger A: Add to Cart | Trigger B: Proceed to Checkout | Trigger C: Payment Method |
|---|---|---|---|
| Redirect moment | Immediately on product page | On cart page exit | On checkout page method selection |
| Multi-product cart support | Limited | Full | Full |
| iFrame compatible | Yes | Yes | Yes |
| Order sync active | Yes | Yes | Yes |
| Name masking available | Yes | Yes | Yes |
| Best for | Single-product stores | Multi-product stores | Mixed-risk product catalogs |
| Customer disruption risk | Low with iFrame | Very low | Very low |
All three triggers can be combined with iFrame mode and order name masking regardless of which option you choose. The trigger selection only affects the moment the redirect fires, not the features available after that point.
Common Configuration Mistakes and How to Avoid Them
Even a careful CODARAB Redirect setup can fail if specific details are overlooked. The following mistakes account for the majority of support requests related to this plugin.
Mistake 1: Using the Same PayPal Account on Both Sites
If Site 2 uses the same PayPal Business account that is already linked to your high-risk Site 1 domain, the webhook will still transmit your Site 1 domain name in the transaction metadata. Always use a fresh PayPal Business account on Site 2 that has never been connected to your high-risk domain.
Mistake 2: Leaving Site 2 Email Notifications Active
WooCommerce sends emails by default for every order status change. If you forget to disable these on Site 2, customers receive duplicate emails from an unfamiliar domain, which triggers confusion and disputes. Disable all Site 2 transactional emails immediately after installation.
Mistake 3: Incorrect iFrame Header Configuration
Many hosting providers, including some managed WordPress hosts, set restrictive X-Frame-Options headers by default. If Site 2 sends this header, the iFrame will fail silently and buyers will see a blank checkout area. Verify the headers using a browser developer tool before going live.
Mistake 4: Skipping the End-to-End Test Order
Configuration errors in the API key connection between Site 1 and Site 2 are only visible when an actual order is placed. Always complete at least two test transactions before accepting real customer payments. Check both dashboards and both email inboxes after each test.
Mistake 5: Not Activating Name Masking on Both Sites
The order name masking setting must be enabled on the Site 1 plugin configuration panel. If you only configure it on Site 2, the product names may still appear in the initial webhook payload sent to the payment processor. Enable the setting on Site 1 first, then verify on Site 2. For more background on this subject, see WordPress plugin repository.
For a broader look at protecting your store from payment processor detection, the checkout cloaking and account ban prevention guide covers additional defensive measures beyond what the redirect plugin handles alone.
Frequently Asked Questions
What is CODARAB Redirect and how does it differ from a standard checkout redirect?
CODARAB Redirect is a WooCommerce plugin that moves payment processing from a high-risk domain to a clean low-risk domain while keeping the customer experience seamless. Unlike a basic URL redirect, it includes real-time order synchronization, iFrame cloaking, email suppression on Site 2, and product name masking. These features together make the two-site architecture invisible to both customers and payment processors.
Do I need two separate hosting accounts for the CODARAB Redirect setup?
You need two separate WordPress and WooCommerce installations, but they do not have to be on different hosting providers. What matters is that Site 2 operates on a domain that has no history with your high-risk products or your existing payment processor accounts. Using separate hosting accounts adds an extra layer of separation but is not strictly required by the plugin.
Which payment gateways can I use on Site 2?
Site 2 supports any WooCommerce-compatible payment gateway. CODARAB recommends using CODARAB Payments on Site 2 for maximum protection, since it also hides product names and disables the PayPal yellow button. However, Stripe, standard PayPal, or any other processor you have access to will work technically with the redirect architecture.
Will customers know they are being redirected to a different website?
Not if you use iFrame mode. With iFrame enabled, the Site 2 checkout page loads inside the Site 1 domain URL. The browser address bar never changes. Without iFrame mode, customers will see the Site 2 domain in the address bar during checkout, which may raise questions. iFrame mode is strongly recommended for a professional customer experience.
How does the CODARAB Redirect setup handle order numbers and IDs?
When an order is placed, it receives a unique ID on Site 2 where payment is processed. The plugin then creates a corresponding order on Site 1 and links the two records via the API connection. Customers receive communications referencing the Site 1 order ID only. The Site 2 order ID is an internal reference used only for reconciliation purposes.
Can I use CODARAB Redirect if my domain is already on a payment processor blacklist?
Yes, this is precisely the scenario the plugin was designed to address. Because payment is processed on Site 2’s clean domain, your Site 1 domain never appears in the payment processor’s webhook data. The processor has no visibility into Site 1 at all. However, you must ensure that Site 2’s domain and payment account have no prior connection to your high-risk domain or products.
Does the plugin work with subscription products and recurring payments?
The CODARAB Redirect setup is designed primarily for one-time payment flows. Recurring payment support depends on whether the gateway installed on Site 2 supports WooCommerce Subscriptions and whether the synchronization layer can correctly relay subscription renewal events. Contact CODARAB support directly to confirm compatibility with your specific subscription setup before purchasing.
What happens if the connection between Site 1 and Site 2 goes down during a transaction?
The payment is still processed on Site 2 because the gateway connection is direct. If the API link between the two sites is temporarily unavailable, the order may not sync to Site 1 immediately. The plugin includes a retry mechanism that attempts to push the order data again once the connection is restored. Monitor both dashboards after any known downtime to catch any unsynchronized orders.
Is the CODARAB Redirect setup legal?
Operating two separate WooCommerce stores where one processes payments on behalf of the other is a legitimate architectural choice used by many multi-brand and multi-market businesses. The key legal requirement is that you accurately represent your business to your payment processor on Site 2 and that the products sold are legal in the jurisdictions where you operate. The plugin does not facilitate fraud; it provides domain separation and data privacy for merchants who sell legal but processor-restricted products.
Where can I find the pricing for CODARAB Redirect?
Pricing for the CODARAB Redirect plugin is published on the official pricing page at codarab.com/redirect. The CODARAB team also offers professional WordPress development services if you need help building Site 2 from scratch. You can reach the team through the contact options listed on the main CODARAB website.
The CODARAB Redirect setup is the most complete two-site WooCommerce architecture available for high-risk merchants who need to separate their storefront domain from their payment processing domain. By combining the right redirection trigger, iFrame cloaking, real-time order sync, and product name masking, you can accept payments reliably without exposing your payment accounts to automated detection. To get started with the full plugin and explore all available features, visit the CODARAB Redirect Plugin: The All-in-One WooCommerce Cloaking and Sync Solution page for complete documentation and licensing options.