Back to Community
Home / Community / General

Troubleshooting Common Forminator PayPal Integration Issues

32 threads Sep 16, 2025

Content

Integrating PayPal with Forminator Forms is a powerful way to accept payments, but users often encounter specific, recurring problems. Based on community reports, here are the most common PayPal integration issues and their potential solutions.

1. reCAPTCHA Conflicts Preventing PayPal Checkout

Problem: Forms with reCAPTCHA (especially v3) fail to process PayPal payments, showing errors like “Error! something went wrong during checkout and payment couldn’t be approved” or “invalid captcha” even when it's correctly filled.

Why it happens: There appears to be a compatibility issue where the reCAPTCHA validation process interferes with the JavaScript that initializes the PayPal payment button.

Potential Solutions:

  • Test without reCAPTCHA: Temporarily remove the reCAPTCHA field to confirm it is the source of the conflict.
  • Use an Alternative: Consider using a simpler spam prevention method, like Honeypot, if reCAPTCHA is not absolutely necessary for your form.
  • Check for Updates: Ensure Forminator is updated to the latest version, as the 'Forminator Forms – Contact Form, Payment Form & Custom Form Builder' team may address this known conflict in future releases.

2. PayPal Amount Validation and Calculation Errors

Problem: Users receive errors such as “PayPal amount must be greater than 0,” “Invalid payment amount!,” or payments in currencies like JPY are processed incorrectly (e.g., 5000 JPY is read as 5 JPY).

Why it happens: These errors often stem from how the form calculates and passes the final amount to PayPal. Issues can include JavaScript not updating the amount before the button is first clicked, currency formatting problems (like commas in numbers), or conditional logic that hides fields containing necessary calculation data.

Potential Solutions:

  • Review Calculation Formulas: Double-check the logic in your calculated field. Ensure it handles various user inputs correctly and rounds numbers appropriately.
  • Check Currency Formatting: For JPY and other currencies, ensure the amount passed to PayPal is a plain number without any formatting (e.g., 5000, not 5,000). This can often be configured in the calculation field's settings.
  • Conditional Logic Conflicts: If you hide required calculation fields with conditional logic, it can break the amount validation. Ensure all fields involved in the final calculation are visible or have a default value when the PayPal button is clicked.
  • Community Fix: One user identified a potential bug in the plugin's JavaScript where the amount wasn't being read correctly on the first button click. They suggested a code modification. While modifying core plugin files is not recommended, you can report this specific finding to the 'Forminator Forms – Contact Form, Payment Form & Custom Form Builder' team for an official fix.

3. PayPal Button Not Appearing or Working with Pagination

Problem: The PayPal button does not render on the final page of a multi-page (paginated) form. Instead, clicking “Next” redirects the user directly to PayPal's website, breaking the embedded checkout experience.

Why it happens: The PayPal smart button script likely needs to be loaded and initialized on the same page where it's displayed. Using page breaks may disrupt this initialization process.

Potential Solutions:

  • Single-Page Form: The most reliable workaround is to avoid pagination and keep the entire form, including the PayPal field, on a single page.
  • Check Placement: Ensure the PayPal field is on the very last page of the form, immediately before the submit button.

4. PayPal Not Working with Variable Amounts or Field Groups

Problem: The PayPal field's “Variable” amount option does not provide a dropdown to select a calculation or number field. Furthermore, forms using “Field Group” repeaters fail to submit to PayPal if more than one entry is added.

Why it happens: These are likely limitations or bugs within the current integration. The variable amount feature may require a specific type of field to be present before it can be linked.

Potential Solutions:

  • Use a Calculated Field: Instead of trying to link the PayPal field directly to a radio button or dropdown, first create a separate “Calculation” field that determines the price based on the user's selection. Then, set the PayPal payment amount to use the value from that calculated field.
  • Field Group Limitation: The issue with Field Groups and multiple entries appears to be a known compatibility problem. A temporary solution is to avoid using the Field Group field for forms that require PayPal payments until a fix is provided.

5. Data and Customization Limitations in PayPal

Problem: PayPal transactions show a generic description, making it hard to identify what was purchased without cross-referencing the Forminator entries.

Why it happens: The standard Forminator PayPal integration focuses on passing the payment amount but does not include a feature to dynamically send item names or descriptors from form fields.

Potential Solution:

  • This is a feature limitation. To achieve this, custom development would be required to modify the data sent to PayPal, which is outside the scope of standard troubleshooting.

General Troubleshooting Steps

For any PayPal issue, always start with these steps:

  1. Plugin Conflict Test: Deactivate all other plugins except Forminator and switch to a default WordPress theme (like Twenty Twenty-Four). If the problem disappears, reactivate your plugins one by one to find the conflict. Thread 2 shows a fatal error caused by another plugin (la-sentinelle-antispam).
  2. Clear Caches: Clear any caching on your site (plugin, server, or CDN) and also clear your browser cache.
  3. Check PayPal Connection: Reconnect your PayPal account in the Forminator integrations settings to ensure the API keys are correct.

Many of these issues are known to the 'Forminator Forms – Contact Form, Payment Form & Custom Form Builder' team. If you continue to experience problems after trying these steps, searching for your specific error on the official WordPress support forums or reporting the bug can help bring further attention to it for a future plugin update.

Related Support Threads Support