How to Customize and Troubleshoot the New Stripe OCS Field in Forminator

Many users of the Forminator Forms plugin have reported confusion and styling issues after upgrading to the new Stripe OCS (Off-site Customer Session) payment field. This field, which is served directly by Stripe's API, introduces elements that may not be desirable for all sites, such as terms text and additional payment buttons.

Common Issues with the New Stripe Field

Based on community reports, the most frequent points of confusion are:

• Misleading Terms Text: The field displays text that says, "By providing your card information, you allow [company_name] to charge your card for future payments in accordance with their terms," even for one-time payments.
• Unexpected Payment Methods: Buttons for payment methods like Amazon Pay, Klarna, or bank transfers appear even when the field is configured for "Cards Only."
• Stripe Link Popup: A prompt for "Save your info for secure 1-click checkout with Link" appears, which may not be relevant for all merchants or regions.
• Limited Styling Control: The field is a combined, single-element iframe served by Stripe, making it difficult to split into separate number, expiry, and CVC fields or to customize its appearance with CSS.

Why This Happens

The core of these issues lies in how the integration works. The new Stripe OCS field is rendered directly by Stripe's servers onto your page. This means its appearance and certain behaviors are primarily controlled by Stripe's API and your Stripe account settings, not solely by the Forminator plugin.

Most Common Solutions and Workarounds

1. Controlling Payment Methods and Link Popups

The display of various payment methods (Klarna, bank transfers, etc.) and the "Link" popup is governed by your Stripe account configuration, not Forminator.

• To disable the "Link" popup: You must log into your Stripe dashboard and disable the "Link" feature from your account's payment methods settings. This cannot be done from within WordPress.
• To control available payment methods: Similarly, you must configure which payment methods are active and available in your Stripe dashboard. Forminator's "Cards Only" setting should then reflect those changes, but the ultimate control is on Stripe's side.

2. Addressing the "Future Payments" Terms Text

This text is a standard part of the Stripe Elements layout for this type of field and is not directly configurable within Forminator. It is designed to cover Stripe's terms of service. For many users, this text is accurate even for one-time payments, as it refers to the specific transaction's authorization. If the text is causing significant user confusion, it may be necessary to add explanatory text near the payment field on your form.

3. Styling and Layout Limitations

Because the field is an iframe served from Stripe, it is highly secure but also highly restrictive.

• CSS Limitations: You cannot use typical CSS rules to hide elements inside the iframe, such as the terms text or the Link prompt. Attempts to use display: none !important; will not work.
• Cannot Split the Field: The field is designed by Stripe to be a single, combined element for card number, expiry, and CVC. It is not possible to split it into separate fields through Forminator.
• Appearance API: Advanced styling via the Stripe Appearance API is not currently supported within the Forminator plugin's interface.

Conclusion

When troubleshooting the new Stripe OCS field in Forminator, the first place to look is often your Stripe.com account dashboard. Many display and behavioral issues are resolved by configuring payment methods and features there. Understanding that the field is an external Stripe element, not a native Forminator field, is key to diagnosing these problems. For styling and layout changes that fall outside of Stripe's account settings, options are currently limited due to the secure nature of the Stripe Elements integration.