CODARAB Payments: 7 Best Proven Ways to Hide Product Names

CODARAB Payments solves one of the most dangerous vulnerabilities for high-risk WooCommerce merchants: by replacing product names on PayPal receipts with a neutral WooCommerce order number, CODARAB Payments prevents PayPal’s automated detection systems from flagging your account based on the keywords in your transaction data. This guide explains exactly how CODARAB Payments achieves this, why it matters, and how you can combine it with complementary strategies to protect your PayPal account long-term.

Why PayPal Scans Your Receipt Data

CODARAB Payments addresses a risk that most WooCommerce merchants overlook entirely: PayPal’s automated compliance engine reads the item-name field on every transaction receipt. When that field contains words associated with high-risk niches — IPTV, peptides, replica, high-copy, adult content — the system can flag or suspend your account without any human review.

PayPal uses a combination of keyword matching and pattern recognition across transaction metadata. The item name field is one of the most accessible data points in that metadata because it is transmitted in plain text during the API call that creates the order.

This means a merchant selling IPTV subscriptions who uses a standard WooCommerce PayPal plugin will send a receipt that literally reads Item Name: IPTV Monthly Subscription. That string is enough for the automated system to initiate a review or an immediate restriction.

The solution is not to remove the item-name field — PayPal requires some value — but to replace the product name with a neutral identifier that reveals nothing about what was sold.

How CODARAB Payments Hides Product Names on PayPal Receipts

CODARAB Payments intercepts the PayPal API order-creation call and substitutes the WooCommerce product name with the order reference number, producing a receipt that reads Item Name: Order:ID1234 instead of the actual product title. This is the core protective mechanism built into CODARAB Payments at the plugin level.

The substitution happens server-side before the data reaches PayPal. From PayPal’s perspective, every transaction processed through CODARAB Payments looks identical in terms of item naming: a neutral order number with no industry-specific keywords.

This approach has several practical consequences:

• PayPal’s keyword-detection robot finds nothing actionable in the item-name field.
• Customers still receive a proper WooCommerce order confirmation email with full product details from your store.
• The PayPal receipt visible to the customer and to PayPal contains only the order reference.
• Dispute evidence is harder to construct because the receipt does not describe the product, which is particularly useful for digital goods and services where delivery proof is difficult.

CODARAB Payments applies this substitution automatically to every order processed through the gateway. You do not need to configure it per product or per category — it is a global setting that protects your entire catalog.

Step-by-Step: Setting Up CODARAB Payments on WooCommerce

CODARAB Payments requires a WordPress/WooCommerce site and a PayPal Business account. The PayPal Business account can be created in under two minutes because CODARAB Payments uses the standard PayPal API — there is no separate merchant account application, no underwriting process, and no complex compliance documentation required at the setup stage.

After activation, CODARAB Payments will also give you the option to disable the PayPal yellow button entirely, leaving only the card payment form visible on your checkout page. This is a separate but equally important feature discussed in the next section.

You can verify the plugin is working correctly by checking the PayPal transaction details in your PayPal Business account after a test purchase. The item description column should display the order number, not the product name.

Disabling the PayPal Yellow Button to Reduce Disputes

CODARAB Payments gives merchants the ability to hide the standard PayPal yellow checkout button and accept only card payments through the PayPal API. This feature works alongside the product-name masking to create a second layer of account protection.

The yellow PayPal button is associated with a higher dispute rate for one structural reason: a logged-in PayPal user can open a dispute with a single click from their PayPal account dashboard. The barrier to filing a dispute is extremely low, which makes it the preferred route for buyers seeking a quick refund on digital goods. For more background on this subject, see WooCommerce official documentation.

Card payments processed through the PayPal API follow a different dispute path. The buyer must contact their card issuer, file a chargeback claim, and wait for the bank’s investigation process. This multi-step procedure significantly reduces impulsive disputes.

For merchants selling digital products, IPTV subscriptions, or services where delivery proof is difficult to provide, this distinction is critical. Fewer disputes mean a healthier PayPal account history, which reduces the probability of automated restrictions.

CODARAB Payments lets you toggle the yellow button off directly from the plugin settings panel in WooCommerce, with no additional code required. Once disabled, only the card form is displayed on your checkout page.

Accepting International Card Payments Without the Yellow Button

CODARAB Payments processes international credit and debit card payments through the PayPal API, which means your customers pay by card on your WooCommerce checkout page while the funds land directly in your PayPal Business account. CODARAB Payments makes this workflow available without requiring a separate merchant account or payment processor contract.

This is a meaningful advantage over Stripe and similar processors for high-risk merchants. Stripe requires business registration, industry verification, and ongoing compliance monitoring. PayPal Business accounts, by contrast, can be opened quickly and do not require the same level of documentation at the account-creation stage.

The card form displayed by CODARAB Payments is minimalist and responsive. It collects card number, expiry, and CVV directly on your WooCommerce checkout page, with no redirect to an external PayPal page. This keeps the customer experience clean and reduces cart abandonment caused by unexpected redirects.

CODARAB Payments supports all major international card networks accepted by PayPal, including Visa and Mastercard. The plugin also supports 2D payment processing, which means transactions do not require an OTP (one-time password) confirmation from the cardholder — a useful option for merchants whose customer base uses prepaid or non-3DS cards.

For a practical demonstration of the card payment flow, you can visit the live demo at codarab.com/card-testing/.

CODARAB Redirect: The Complementary Layer of Protection

CODARAB Payments is highly effective at preventing keyword-based detection, but it has one known limitation: if your domain name is already listed on a payment processor blacklist, PayPal can detect the association through the Webhook notification system, which transmits your domain as part of the transaction metadata. In that scenario, CODARAB Payments alone is not sufficient.

CODARAB Redirect was developed specifically to address this gap. It is a separate WooCommerce plugin that redirects the checkout process from your high-risk site (Site 1) to the checkout page of a secondary low-risk site (Site 2), where the actual payment is processed.

The key features of CODARAB Redirect include:

• Three redirect trigger options: Add to Cart button, Proceed to Checkout button, or custom payment method selection.
• Real-time order synchronization between Site 1 and Site 2.
• Customer notifications sent only from Site 1, so buyers never see the secondary site.
• An iFrame option that loads the Site 2 checkout page inside Site 1’s domain, so the customer URL never changes.
• Product-name masking identical to CODARAB Payments — item names are replaced with order numbers on the Site 2 receipts as well.

Together, CODARAB Payments and CODARAB Redirect form a two-layer protection system. CODARAB Payments handles keyword masking at the API level; CODARAB Redirect handles domain-level exposure by routing transactions through a clean secondary site.

Learn more about this dual-site approach in the article on WooCommerce dual store strategy for protecting your business from shutdowns.

Converting PayPal Funds to USDT via RedoPay

CODARAB Payments also enables an indirect conversion pathway from PayPal balances to USDT cryptocurrency, using the RedoPay Visa card as an intermediary. This is particularly relevant for merchants in regions where direct PayPal withdrawals to a local bank account are restricted or unavailable.

The conversion flow works as follows:

• Your customer pays by card on your WooCommerce checkout page.
• The payment is processed through the PayPal API and the funds arrive in your PayPal Business account.
• You transfer the PayPal balance to a RedoPay Visa card linked to your account.
• RedoPay credits the equivalent amount in USDT to your RedoPay account, typically within one to five business days.

This pathway does not require a cryptocurrency exchange account or any direct PayPal-to-crypto transfer, which PayPal does not natively support in most markets. The RedoPay card acts as the bridge between the traditional PayPal ecosystem and the crypto ecosystem.

For merchants who want to preserve earnings in a stable digital asset rather than a fiat currency subject to local exchange controls, this is a practical and documented option offered through the CODARAB Payments ecosystem.

Explore the detailed walkthrough in the guide on how to withdraw PayPal funds to USDT in 2026 with CODARAB Payments.

Comparison: CODARAB Payments vs. Standard PayPal WooCommerce Plugin

CODARAB Payments differs from the standard WooCommerce PayPal plugin in several important ways that matter specifically to high-risk merchants. The table below summarizes the key differences.

The standard plugin is adequate for low-risk merchants with conventional product catalogs. For merchants in high-risk niches, the absence of product-name masking and the inability to disable the yellow button make the standard plugin a liability rather than a convenience.

Common Mistakes High-Risk Merchants Make with PayPal

CODARAB Payments addresses several mistakes that high-risk WooCommerce merchants make repeatedly when trying to use PayPal as their primary payment processor. Understanding these mistakes helps you configure the plugin correctly from the start.

Using Descriptive Product Names in WooCommerce Without Masking

The most common mistake is simply installing a standard PayPal plugin and assuming that PayPal only reviews transactions manually after a dispute. In reality, automated keyword scanning happens at the transaction level, often before any human reviewer is involved. CODARAB Payments eliminates this risk by masking the product name at the API call stage.

Leaving the Yellow Button Active for Digital Products

Merchants who sell digital goods — ebooks, software licenses, IPTV subscriptions, online courses — often leave the yellow PayPal button active because it seems like a convenient payment option for buyers. The problem is that the ease of opening a dispute through a logged-in PayPal account makes digital goods particularly vulnerable to abuse. Disabling the button with CODARAB Payments and forcing card payments shifts the dispute process to the card network, which is more structured and less prone to abuse.

Using a Personal PayPal Account Instead of a Business Account

CODARAB Payments is designed for use with a PayPal Business account. Personal accounts have lower transaction limits, different API access levels, and are more likely to trigger automatic reviews when processing high volumes. Opening a PayPal Business account is free and takes a few minutes — there is no reason to operate on a personal account for a WooCommerce store.

Ignoring Domain Blacklist Risk

Merchants who have been flagged before, or who operate in well-known high-risk niches, sometimes assume that simply switching to CODARAB Payments will resolve all their account issues. If your domain is already on a blacklist, the Webhook system will still expose it. In that case, CODARAB Redirect is the necessary additional step.

When CODARAB Payments Is Not Enough

CODARAB Payments is a powerful tool, but it is not a universal solution for every account protection scenario. Understanding its limits helps you decide when to deploy CODARAB Redirect alongside it.

Domain Already on a Payment Processor Blacklist

If your store’s domain has been associated with a suspended or restricted PayPal account in the past, PayPal’s Webhook system will flag new accounts that receive notifications from the same domain. CODARAB Payments cannot mask the domain in the Webhook payload. CODARAB Redirect solves this by processing payments through a secondary domain that has no negative history.

High Dispute Rate from Previous Transactions

If your PayPal account already has an elevated dispute rate, masking product names on future transactions will not retroactively improve your account standing. You may need to open a new PayPal Business account and use CODARAB Payments from the start to build a clean transaction history. For more background on this subject, see PayPal Acceptable Use Policy.

Products in Explicitly Prohibited Categories

Some product categories are explicitly prohibited by PayPal’s Acceptable Use Policy regardless of how the transaction is labeled. Product-name masking reduces automated detection risk but does not change the underlying policy compliance status of your business. For categories that are outright prohibited, CODARAB Redirect with a clean secondary site is the appropriate architecture.

For a comprehensive overview of how the two-plugin system works together, see the guide on CODARAB Redirect Plugin: the all-in-one WooCommerce cloaking and sync solution.

You can also review the full feature set of the latest plugin version in the article on CODARAB Payments V10.8.5: 5 new features for WooCommerce.