The CODARAB Redirect setup is the most effective way to protect your PayPal or Stripe account from suspension when running a high-risk WooCommerce store. By routing customers from a high-risk Site 1 to a clean, low-risk Site 2 at checkout, the plugin shields your payment processor from detecting sensitive product keywords. This guide walks you through every configuration step in precise detail.
- The CODARAB Redirect setup connects two WooCommerce sites so payments process on the low-risk domain.
- Three redirection triggers are available: Add to Cart, Proceed to Checkout, and custom payment method selection.
- Orders sync automatically and instantly between both sites after each transaction.
- Customers receive all email notifications exclusively from Site 1, preserving brand consistency.
- An iFrame option lets the low-risk checkout appear visually inside the high-risk domain.
- Product names are replaced by WooCommerce order numbers on PayPal receipts to avoid keyword detection.
- You need two separate WordPress/WooCommerce installations before starting the CODARAB Redirect setup.
- The plugin supports PayPal, Stripe, CODARAB Payments, or any other processor on Site 2.
- The iFrame cloaking mode keeps the customer on your high-risk domain URL throughout checkout.
- Order name masking (Order#1234 instead of product name) is a built-in feature of the plugin.
- If your domain is already blacklisted, CODARAB Redirect routes payments around that blacklist via Site 2.
- A live demonstration of the full flow is available at dev.wpchatbox.com.
- What Is CODARAB Redirect and Why High-Risk Merchants Need It?
- Prerequisites for the CODARAB Redirect Setup
- Step-by-Step CODARAB Redirect Setup: Installing the Plugin on Both Sites
- Configuring the Three Redirection Trigger Options
- How the iFrame Cloaking Mode Works in the CODARAB Redirect Setup
- Automatic Order Synchronization Between Site 1 and Site 2
- Replacing Product Names with Order Numbers on PayPal Receipts
- Customer Email Notifications: Keeping Communication on Site 1
- Choosing the Right Payment Processor for Site 2
- Common Mistakes to Avoid During Configuration
- Frequently Asked Questions
What Is CODARAB Redirect and Why High-Risk Merchants Need It?
The CODARAB Redirect setup solves a critical problem: payment processors like PayPal and Stripe use automated systems to detect high-risk keywords in webhook data, domain names, and receipt item descriptions. When your domain appears on a blacklist or your receipts mention terms like “IPTV” or “High Copy,” your account faces suspension.
CODARAB Redirect intercepts the customer journey at checkout and silently transfers the transaction to a second, clean WooCommerce site. The payment processor only ever sees the low-risk domain, never the original storefront. When it comes to CODARAB Redirect setup, preparation matters more than speed.
This architecture is especially valuable for merchants selling digital products, IPTV subscriptions, peptides, high-copy goods, or dropshipping products that standard processors flag automatically.
The plugin is a complementary tool to CODARAB Payments. While CODARAB Payments hides product names and disables the PayPal yellow button, CODARAB Redirect goes further by completely separating the high-risk storefront from the payment processing environment. Anyone dealing with CODARAB Redirect setup should keep this step in mind.
Prerequisites for the CODARAB Redirect Setup
Before you begin the CODARAB Redirect setup, you must have the following infrastructure in place. Skipping any prerequisite will cause the plugin to malfunction or the redirect flow to break mid-checkout.
Site 1: The High-Risk Storefront
This is your main customer-facing store where products are listed and browsed. It can have any domain name. WooCommerce must be installed and active. You do not need a payment gateway connected to Site 1 directly.
Site 2: The Low-Risk Checkout Site
This is a separate WordPress/WooCommerce installation on a clean domain with no history of payment processor flags. It should have minimal product listings, a neutral brand name, and a fully configured payment gateway. This is the site that actually processes the transaction.
Payment Processor on Site 2
You can use CODARAB Payments, Stripe, PayPal Business API, or any other WooCommerce-compatible gateway on Site 2. The choice depends on your country and business model. CODARAB Payments is the recommended option for merchants who also want product name masking on PayPal receipts. This is exactly why CODARAB Redirect setup deserves a documented, methodical approach.
| Requirement | Site 1 (High Risk) | Site 2 (Low Risk) |
|---|---|---|
| WordPress + WooCommerce | Required | Required |
| CODARAB Redirect Plugin | Required | Required |
| Payment Gateway | Not needed | Required |
| Product Listings | Full catalog | Minimal or generic |
| Domain History | Can be flagged | Must be clean |
| Customer-Facing Brand | Primary brand | Hidden from customers |
Step-by-Step CODARAB Redirect Setup: Installing the Plugin on Both Sites
The CODARAB Redirect setup requires the plugin to be installed and activated on both WordPress installations. The two instances then communicate via a secure API connection to transfer cart data and sync orders.
Once the connection is verified, a green status indicator appears in the plugin dashboard on both sites. If the connection fails, check that both sites use HTTPS and that no firewall or CDN rule is blocking outbound POST requests.
For merchants on Hostinger, note that the CDN layer can block plugin API calls. Refer to the guide on fixing Forbidden errors on Hostinger by disabling CDN for a quick resolution.
Configuring the Three Redirection Trigger Options
The CODARAB Redirect setup offers three distinct trigger points, and you must choose which one or which combination fits your store flow. Each trigger intercepts the customer at a different moment in the purchase journey.
Trigger A: Add to Cart / Buy Now / Order Now Button
When a customer clicks any of these buttons on Site 1, the plugin immediately captures the product and quantity, creates a draft order on Site 2, and redirects the customer to the Site 2 checkout page. This is the most aggressive option and converts the fastest because it skips the cart page entirely. Everything described above applies directly to CODARAB Redirect setup.
Trigger B: Proceed to Checkout Button
The customer browses Site 1 normally, adds items to the cart, and reaches the cart page. When they click “Proceed to Checkout,” the plugin transfers the cart contents to Site 2 and redirects them. This trigger allows customers to review their cart before being moved. For more background on this subject, see WooCommerce official documentation.
Trigger C: Custom Payment Method Selection
The customer reaches the checkout page of Site 1 and selects a specific custom payment method you have configured. Selecting that method triggers the redirect to Site 2. This is the most subtle option and is useful when you want to maintain a partially functional checkout on Site 1 for non-redirected payment methods.
You can combine triggers A and B simultaneously for maximum coverage. The plugin settings panel on Site 1 has individual toggle switches for each trigger option. Planning ahead for CODARAB Redirect setup saves both time and money later.
How the iFrame Cloaking Mode Works in the CODARAB Redirect Setup
The iFrame cloaking mode is one of the most powerful features of the CODARAB Redirect setup. Instead of visibly redirecting the customer to a new domain, the checkout page of Site 2 is loaded inside an iFrame embedded on Site 1’s checkout URL.
From the customer’s perspective, they never leave highrisk.com. The browser address bar continues to show the Site 1 domain. The payment form, however, is served from the clean Site 2 domain. This creates zero friction and zero suspicion for the customer.
Technical Considerations for iFrame Mode
Site 2 must allow iFrame embedding. You need to configure the X-Frame-Options header on Site 2 to permit embedding from the Site 1 domain. Some hosting providers block this by default. Additionally, the checkout page on Site 2 should be stripped of its navigation, header, and footer so only the payment form appears inside the iFrame.
CODARAB provides a dedicated guide for creating a clean, minimal checkout page on Site 2 specifically for iFrame use. This ensures the embedded page looks native to Site 1’s design. Most questions about CODARAB Redirect setup come back to these same basics.
For a detailed walkthrough of building that clean checkout environment, see the guide on creating a clean WooCommerce checkout for iFrame cloaking.
Automatic Order Synchronization Between Site 1 and Site 2
The CODARAB Redirect setup includes real-time, automatic order synchronization. The moment a transaction is completed on Site 2, the order data is pushed back to Site 1 instantly via the plugin API.
This means your Site 1 WooCommerce dashboard always reflects the true order status without any manual intervention. You manage fulfillment, tracking, and customer service entirely from Site 1.
What Data Is Synchronized?
The synchronization covers the following order fields between both stores:
- Order status (Processing, Completed, On Hold, Cancelled, Failed)
- Customer billing and shipping address
- Product line items and quantities
- Transaction ID from the payment processor
- Order total and applied discounts
The sync is bidirectional for status updates. If you manually change an order status on Site 1, the change propagates to Site 2 as well. This keeps both databases consistent at all times. A structured response to CODARAB Redirect setup always beats a rushed one.
For a deeper technical explanation of how this sync works, read the article on how CODARAB Redirect syncs orders between two WooCommerce stores instantly.
Replacing Product Names with Order Numbers on PayPal Receipts
The CODARAB Redirect setup includes an optional but highly recommended feature: replacing product names with the WooCommerce order number on all PayPal receipts generated by Site 2.
Without this feature, a PayPal receipt for an IPTV subscription would display “IPTV Monthly Plan” as the item name. PayPal’s automated systems scan these receipt descriptions for high-risk keywords and use them as signals to flag or suspend accounts.
How the Name Masking Works
When enabled, the plugin intercepts the order data sent to PayPal via the API before the receipt is generated. Instead of sending the actual product name, it sends the string “Order:#1234” where 1234 is the WooCommerce order ID from Site 1. Anyone researching CODARAB Redirect setup will recognise this pattern quickly.
The customer still receives a proper order confirmation email from Site 1 with full product details. The PayPal receipt, however, contains only the neutral order reference. This protects the PayPal account on Site 2 from keyword-based automated suspensions.
This feature is enabled with a single toggle in the CODARAB Redirect plugin settings panel under the “Receipt Masking” section.
Customer Email Notifications: Keeping Communication on Site 1
One of the most important UX decisions in the CODARAB Redirect setup is controlling which site sends email notifications to customers. By default, WooCommerce on both sites would attempt to send order emails, which would confuse customers with duplicate or contradictory messages.
The plugin solves this by suppressing all customer-facing transactional emails on Site 2. Only Site 1 sends order confirmation, processing, and completion emails to the customer. Keeping written notes on CODARAB Redirect setup makes the next decision easier.
Why This Matters for Customer Trust
If a customer receives an email from an unfamiliar domain (Site 2), they may question the legitimacy of the purchase or open a dispute with their bank. By routing all communications through Site 1, you maintain a consistent, professional brand experience.
Admin notification emails for new orders are still sent to you from Site 2 so you can monitor transaction activity on the payment processing side. Customer-facing emails come exclusively from Site 1.
To learn more about managing this notification flow, see the article on WooCommerce order notifications: how to send emails only from your main store. That single detail changes the outcome of CODARAB Redirect setup completely.
Choosing the Right Payment Processor for Site 2
The CODARAB Redirect setup is processor-agnostic, meaning Site 2 can use any WooCommerce-compatible payment gateway. However, the choice of processor significantly affects how long your setup remains protected from suspensions.
CODARAB Payments on Site 2
Using CODARAB Payments on Site 2 provides the deepest level of protection. It combines the redirect cloaking of CODARAB Redirect with the PayPal API card processing, yellow button suppression, and receipt name masking of CODARAB Payments. The two plugins work together as a layered defense system.
Stripe on Site 2
Stripe is a viable option for Site 2 if the low-risk domain and product descriptions are genuinely neutral. Stripe’s automated review systems still scan merchant accounts periodically, so the domain and product catalog of Site 2 must remain clean and free of any high-risk associations.
Other Processors
Any gateway that integrates natively with WooCommerce via a plugin can be used. The CODARAB Redirect plugin transfers cart data using standard WooCommerce order structures, so compatibility is broad. Refer to the comparison of solutions at CODARAB Pay vs. CODARAB Redirect: WooCommerce solutions for high-risk merchants. Testing everything before going live keeps CODARAB Redirect setup predictable.
Common Mistakes to Avoid During Configuration
The CODARAB Redirect setup fails most often due to a small number of avoidable configuration errors. Reviewing this list before going live will save significant troubleshooting time.
Mistake 1: Using the Same Hosting Account for Both Sites
If Site 1 and Site 2 share the same hosting account or IP address, payment processors may link the two domains together during their automated reviews. Use separate hosting providers or at minimum separate server IP addresses for each site.
Mistake 2: Leaving High-Risk Keywords in Site 2 Product Names
Even if Site 2 is only used for payment processing and customers never browse it directly, its WooCommerce product catalog is still visible to PayPal and Stripe via API calls. Keep all product names on Site 2 generic and neutral, such as “Digital Service Plan” instead of “IPTV 12-Month Subscription.”
Mistake 3: Not Testing the Full Checkout Flow Before Launch
Always place a real test order using a live card in a small amount before sending real customer traffic through the redirect. Verify that the order appears correctly on both Site 1 and Site 2 dashboards, that the customer receives only one email from Site 1, and that the PayPal receipt shows the order number instead of the product name. For more background on this subject, see WordPress plugin repository. Small adjustments often improve CODARAB Redirect setup more than a full rebuild.
Mistake 4: Forgetting to Configure iFrame Headers
If you use iFrame cloaking mode and forget to set the correct X-Frame-Options or Content-Security-Policy headers on Site 2, the iFrame will be blocked by the browser and customers will see a blank checkout area. Test across Chrome, Firefox, and Safari before launch.
Mistake 5: Using the Same PayPal Account on Both Sites
The entire purpose of the two-site architecture is to separate the high-risk domain from the payment processor. If both sites use the same PayPal account, the protection is nullified. Site 2 must use a dedicated, separate PayPal Business account.
Frequently Asked Questions
Does the CODARAB Redirect setup work with any WooCommerce theme?
Yes, the CODARAB Redirect setup is theme-independent. It hooks into WooCommerce core actions and filters rather than template files. The redirect triggers fire regardless of which theme is active on Site 1 or Site 2. However, for iFrame mode, a minimal checkout template on Site 2 improves the visual result significantly.
Can I use CODARAB Redirect if my domain is already on a PayPal blacklist?
Yes, this is precisely the scenario CODARAB Redirect was designed for. Because all payment processing happens through Site 2’s clean domain, PayPal’s webhook and receipt data never reference your blacklisted Site 1 domain. The plugin routes around the blacklist entirely. The same logic applies to CODARAB Redirect setup in almost every setup.
How many products can I redirect through the CODARAB Redirect setup?
There is no documented product limit in the plugin. The redirect mechanism transfers cart data via API call, so it scales with your WooCommerce catalog size. Merchants with hundreds of products use the same configuration as those with a single product. Performance depends on your hosting server speed, not the plugin itself.
Will customers know their payment is processed on a different site?
In iFrame mode, customers see only the Site 1 domain in their browser at all times. In direct redirect mode, the URL briefly changes to Site 2 during checkout. Using a neutral, professional domain name for Site 2 minimizes any customer concern. All post-purchase emails come from Site 1, reinforcing your primary brand.
What happens to an order if the API connection between Site 1 and Site 2 drops during checkout?
The CODARAB Redirect plugin includes error handling that prevents partial orders. If the API call to Site 2 fails, the customer is shown a standard WooCommerce error message and the transaction is not initiated. No payment is captured and no order is created on either site. The customer can retry immediately. Reviewing CODARAB Redirect setup early prevents costly mistakes later on.
Is the CODARAB Redirect setup compatible with WooCommerce Subscriptions?
The plugin transfers standard cart and order data. Subscription renewal handling depends on whether the payment gateway on Site 2 supports WooCommerce Subscriptions natively. CODARAB Payments supports recurring billing via PayPal API. Verify compatibility with your chosen gateway before configuring subscription products.
Do I need a developer to complete the CODARAB Redirect setup?
The plugin is designed for store owners with basic WordPress experience. Installing on both sites, entering the API key, and selecting trigger options requires no coding. The iFrame header configuration may require brief server-level access, which a hosting provider’s support team can assist with. CODARAB also offers professional setup services via codarab.com.
Can I use CODARAB Redirect alongside CODARAB Payments on the same store?
Yes, and this is the recommended combination for maximum protection. CODARAB Payments is installed on Site 2 to handle the actual card processing with name masking and yellow button suppression. CODARAB Redirect is installed on both sites to manage the customer flow from Site 1 to Site 2. The two plugins are fully compatible and complementary. Clear expectations make CODARAB Redirect setup far simpler to manage day to day.
How does the plugin handle currency and tax differences between Site 1 and Site 2?
The cart total transferred from Site 1 to Site 2 includes the final amount calculated by Site 1’s WooCommerce tax and currency settings. Site 2 displays this amount at checkout. You should configure Site 2 to use the same base currency as Site 1 to avoid display discrepancies. Tax rules on Site 2 should be set to match Site 1 or disabled if Site 1 already calculates the final inclusive price.
Where can I see a live demonstration of the CODARAB Redirect setup in action?
CODARAB maintains a live demonstration environment at dev.wpchatbox.com where you can experience the full customer journey, including the redirect trigger, the checkout flow on Site 2, and the order confirmation experience. The CODARAB website at codarab.com/redirect also contains pricing details and documentation links.
The CODARAB Redirect setup is the most complete two-site WooCommerce protection strategy available for high-risk merchants in 2026. By following the seven configuration steps above, you can process payments safely without exposing your primary domain or payment accounts to automated suspension systems. To get started with the full plugin and explore complementary tools, visit the complete overview at CODARAB Redirect Plugin: the all-in-one WooCommerce cloaking and sync solution.