PayPal API Setup: 5 Best Proven Steps for WooCommerce

The PayPal API setup process with CODARAB Payments lets any WooCommerce merchant accept international card payments through PayPal’s infrastructure in under five minutes. Whether you sell digital products, IPTV subscriptions, peptides, or dropshipping items, this guide walks you through every step from creating your PayPal Business account to going live with a fully configured, dispute-resistant checkout.

What Is CODARAB Payments and Why Use It for PayPal API Setup?

The PayPal API setup through CODARAB Payments gives WooCommerce merchants a Stripe-like card form powered entirely by PayPal’s infrastructure. Instead of the standard yellow PayPal button, customers see a clean credit and debit card input field at checkout.

CODARAB Payments is built specifically for high-risk merchants — sellers of digital products, IPTV subscriptions, dropshipping goods, peptides, and high-copy items. It solves three problems at once: accepting international cards, reducing disputes, and masking sensitive product keywords from PayPal’s automated review systems.

Because the plugin is built on the PayPal API, account creation is fast. A PayPal Business account can be opened in under two minutes, with no complex underwriting or document submission required at the start. This contrasts sharply with Stripe, which often rejects high-risk merchants outright during onboarding.

Prerequisites Before You Start the PayPal API Setup

Before beginning the PayPal API setup, confirm that you have all required components in place. Missing even one item will block you at a later step and waste time.

Here is what you need:

• A live WordPress website running WooCommerce (version 5.0 or later is recommended).
• A PayPal Business account — a personal account does not expose the API credentials panel.
• Administrator access to your WordPress dashboard.
• The CODARAB Payments plugin file, obtained from codarab.com.
• A stable internet connection during the credential copy-paste step to avoid input errors.

If your WordPress site is not yet ready, CODARAB also offers professional WooCommerce development services. You can request a ready-made store with the payment gateway pre-integrated directly from their team.

Do not attempt the PayPal API setup on a localhost environment. PayPal’s Webhook system requires a publicly accessible URL to confirm transactions and send order status updates.

Step 1 — Create or Prepare Your PayPal Business Account

The PayPal API setup begins with a verified PayPal Business account. If you already have one, skip ahead to generating credentials. If not, open a new account at the official PayPal Business account page.

During registration, use a business email address that you control long-term. Avoid free webmail addresses that look unprofessional to PayPal’s review system.

Key tips for a clean account opening:

• Use your real legal name or registered business name — inconsistencies trigger automatic holds.
• Add and verify a bank account early to avoid fund-release delays.
• Do not link the new account to a previously suspended PayPal account’s phone number or bank card.
• Complete your profile fully before processing your first live transaction.

Once your account is active, navigate to Account Settings > Business Information and confirm that the account type shows as Business. This status is required for the API credentials panel to appear in the Developer Dashboard.

Step 2 — Generate Your PayPal API Credentials

The PayPal API setup requires two credentials: a Client ID and a Secret Key. These are generated inside the PayPal Developer Dashboard, not inside your regular PayPal account interface.

Follow these steps exactly:

1. Go to developer.paypal.com and log in with your PayPal Business account.
2. Click My Apps & Credentials in the left sidebar.
3. Select the Live tab (not Sandbox — that is only for testing).
4. Click Create App, give it a name (for example, your store name), and click Create App again.
5. Your Client ID appears immediately. Click Show next to the Secret field to reveal the Secret Key.
6. Copy both values into a secure text file before closing the page.

Never share your Secret Key publicly. Anyone with both credentials can initiate transactions on your behalf. Store them in a password manager rather than a plain text document.

If you accidentally expose your Secret Key, return to the Developer Dashboard immediately and click Regenerate Secret. Update the plugin settings as soon as the new key is generated. For more background on this subject, see WooCommerce official documentation.

PayPal API Setup: Installing the CODARAB Payments Plugin

The PayPal API setup continues with installing the CODARAB Payments plugin on your WooCommerce store. The installation follows the standard WordPress plugin workflow.

After activation, the plugin creates its own settings panel inside the WooCommerce Payments tab. You will not find it under the standard PayPal settings — it operates as a fully independent gateway.

If the plugin does not appear after activation, check that your WooCommerce version meets the minimum requirement. You can also review the CODARAB documentation at CODARAB Payments documentation for version compatibility notes.

Step 4 — Configure CODARAB Payments Settings in WooCommerce

The PayPal API setup configuration step is where you paste your credentials and choose your key protection options. Open WooCommerce > Settings > Payments > CODARAB Payments > Manage.

After filling in the Client ID and Secret Key, click Save Changes. The plugin immediately validates the credentials against the PayPal API. If validation fails, double-check that you copied the Live credentials, not the Sandbox credentials.

The Hide Product Names option is critical for high-risk sellers. When enabled, PayPal receipts display only the WooCommerce order number (for example, Order #1234) instead of the actual product name. This prevents PayPal’s automated keyword-detection system from flagging your account based on receipt content.

Step 5 — Test the PayPal API Setup Before Going Live

The final phase of the PayPal API setup is a live test transaction. Use a real card with a small transaction amount — most merchants use a one-dollar or one-euro test product created specifically for this purpose.

What to verify during testing:

• The card form appears at checkout without the yellow PayPal button visible.
• The transaction completes and the WooCommerce order status changes to Processing.
• The PayPal receipt shows the order number, not the product name.
• You receive the payment notification email from PayPal.
• The WooCommerce order confirmation email sends to the customer address.

If the card form does not appear, clear your browser cache and check that no other PayPal plugin is active simultaneously. Conflicts between the standard WooCommerce PayPal Payments plugin and CODARAB Payments are the most common cause of display issues.

After a successful test, delete the test order from WooCommerce and refund the test transaction from your PayPal dashboard. Your PayPal API setup is now complete and ready for production traffic. You can see a live demonstration of the checkout at codarab.com/card-testing.

How to Disable the Yellow PayPal Button and Reduce Disputes

Disabling the yellow PayPal button is one of the most impactful steps after completing the PayPal API setup. The yellow button allows customers to pay directly from their PayPal wallet, which creates a one-click dispute pathway that is notoriously easy to abuse.

When a customer pays through their PayPal wallet, opening a dispute requires only a few clicks inside the PayPal app. When a customer pays by card through the CODARAB Payments card form, disputing the charge requires contacting their bank, providing documentation, and waiting for a formal chargeback process — a significantly higher barrier.

This distinction is especially important for sellers of digital products and services, where proof of delivery is inherently difficult to provide. Disabling the yellow button does not prevent customers from paying — it simply routes all payments through the card form, which is processed via the same PayPal API infrastructure.

To disable the button, toggle the Disable PayPal Button option inside the CODARAB Payments settings panel as described in Step 4. No additional code changes are required. For a deeper look at this feature, see the guide on how to disable the PayPal yellow button to reduce disputes.

Hiding Product Names on PayPal Receipts for High-Risk Sellers

After completing the PayPal API setup, high-risk merchants should immediately enable the product name masking feature. PayPal’s automated compliance system scans transaction data — including receipt line items — for keywords associated with restricted or high-risk categories.

Without masking, a receipt for an IPTV subscription might read: Item Name: Premium IPTV Monthly Plan. PayPal’s system can flag this keyword and trigger an account review or limitation.

With the CODARAB Payments masking feature enabled, the same receipt reads: Item Name: Order #1247. The order number carries no risk signals for PayPal’s detection algorithms.

This protection applies to all transaction types processed through the plugin — one-time purchases, subscription renewals, and manual orders created from the WooCommerce admin panel. The masking happens at the API request level, before the data reaches PayPal’s servers, so there is no way for PayPal to see the original product name.

For merchants selling multiple product categories with different risk levels, this single feature can extend the usable lifespan of a PayPal Business account considerably. Learn more about this technique in the article about hiding product names on PayPal receipts.

Withdrawing PayPal Funds as USDT via RedoPay

One of the most valuable features unlocked by the PayPal API setup with CODARAB Payments is the ability to convert PayPal earnings into USDT cryptocurrency indirectly through a RedoPay Visa card.

The withdrawal flow works as follows:

1. Your customer pays by card at checkout — the payment is processed via the PayPal API.
2. The funds arrive in your PayPal Business account, typically within minutes.
3. You transfer the funds from PayPal to your RedoPay account using the linked Visa card.
4. RedoPay credits your account in USDT within one to five business days.

This flow is particularly valuable for merchants in countries where direct PayPal withdrawals to local bank accounts are unavailable, restricted, or subject to unfavorable exchange rates. USDT is a stablecoin pegged to the US dollar, so it retains its value without the volatility associated with Bitcoin or Ethereum.

There are no additional fees from the CODARAB Payments plugin for this withdrawal path. Standard PayPal transaction fees and RedoPay’s own conversion fees apply. For a complete walkthrough, see the guide on how to withdraw PayPal funds to USDT in 2026.

When to Add CODARAB Redirect to Your PayPal API Setup

The PayPal API setup with CODARAB Payments is sufficient for most high-risk merchants. However, there is one scenario where an additional layer of protection is necessary: when your domain name is already listed on a payment processor blacklist.

PayPal’s Webhook system checks the originating domain of every transaction. If your domain has been flagged in the past — due to previous disputes, chargebacks, or a prior account suspension — PayPal may detect this via Webhook data even with a brand new PayPal Business account.

CODARAB Redirect solves this by routing the actual payment through a second, clean WooCommerce site (Site 2) while the customer remains on your original domain (Site 1). The checkout page of Site 2 appears inside an iFrame on Site 1, so customers never see a domain change. Orders sync automatically between both sites in real time.

Key CODARAB Redirect features that complement the PayPal API setup:

• Three redirect trigger options: Add to Cart, Proceed to Checkout, or payment method selection.
• Automatic real-time order synchronization between both WooCommerce stores.
• Customer notifications sent only from Site 1, preserving a consistent brand experience.
• Product name masking on the Site 2 checkout, identical to the CODARAB Payments feature.

For merchants whose domain is clean, CODARAB Payments alone is the right tool. For merchants with a flagged domain, combining both solutions provides comprehensive protection. Read the full comparison in the article about CODARAB Pay vs CODARAB Redirect for high-risk merchants.