outrageous

Hi there,

Thanks for providing feedback.

The old Paypal plugin worked perfectly. The new one is completely useless.
It replaces the checkout-buttons with an iframe,[…]

Both, the PayPal Checkout plugin and PayPal Payments do the same thing on the Checkout page by replacing the regular button with the PayPal smart buttons.

[…] neither the layout fits […]

Would you mind elaborating? The buttons are rendered in a flexible layout, meaning they will adapt to the #ppc-button div where they are rendered in.
If you want smaller buttons, you can reduce the width of the div, which automatically impacts the button width. There are also render hooks that allow you to reposition the buttons & messaging.

[…] nor the translation works in Firefox […]

For a reason I cannot determine based on the provided information, the button translation may not work for you with the Firefox browser, but this is not a general issue with the plugin.
The button language is determined by PayPal for every individual visitor in any case and the detection works as expected in all major browsers in our tests.

[…] This way it does not meet german or EU regulations so it can not be used at all. […]

The integration is developed in partnership with PayPal Germany. If you have any doubts please reach out to the PayPal support and if you require any legal advice, I suggest consulting a lawyer.

But if you encounter any problems with the plugin setup or need assistance with the configuration, please open a thread in the support forums here: https://www.ads-software.com/support/plugin/woocommerce-paypal-payments/
Thanks!

Kind regards,
Niklas

Hi Niklas,

first of all, thank you very much for your fast and detailed reply.
We have never used the Paypal Checkout plugin, but the integrated “PayPal-Standard” Gateway, which does not implement the Smart-Buttons but does use the Woocmmerce standard buttons (which ist a much better solution in my opinion).

Regarding the layout:
We would like to change font, font-weight, color, background-color, borders and hover states. Plus we would like to remove the max-width. Afaik it is not possible to does this with CSS for elements in an iframe.
But if I get your linked example correctly, it should be possible to filter the generated html within the iframe and inject some CSS or classes for that matter. I Will give it a try for sure. Thank you very much.

From my point of view, the solution would comply with german rights, if the button text translation would work reliably. I am a little surprised that you have not been able to reproduce the issue. If i set the Button-Text to “PayPal – Jetzt kaufen”, it works in all major Browsers but Firefox. Firefox always shows “PayPal – Buy Now”. I have not been able to find a single computer in our office or in my private apartment that showed “Jetzt kaufen” on Firefox. Tested both the regular release and the developer version. This might happen due to a setting in the browser, but if that is the case it seems to be a pretty common one. As long as a singificant number of computers shows “Buy now”, this is an issue and makes the plugin unusable for us (and baically any german based show in my opinion). Maybe the easiest way to get around this would be an option to override the detection with a setting in the plugin, if that possible. That way users of the plugin could decide if they would like to use language detection or set a fixed language themselves.

Thanks,
Daniel

• This reply was modified 2 years, 4 months ago by dgoehr.
• This reply was modified 2 years, 4 months ago by dgoehr.

Hi Daniel,

Thanks for elaborating.
I see; PayPal Standard and PayPal Payments are working indeed quite different.
We hear your concerns regarding the button look and translations.

There are feature requests in our backlog for a language override feature as you proposed and a feature to potentially disable the smart button in favor of a regular button on the Checkout page.
These features are popular especially with German merchants, due to the nature of the local legal regulations, and we have raised the concerns with PayPal, especially PayPal Germany. But for the time being, there are no resources available to develop these features as PayPal is looking for an automated and standardized way the PayPal experience is presented to the buyer.
This means the smart buttons the PayPal buyer is used to are presented in a language they are familiar with. A hardcoded language override would more often result in the buttons having the wrong translation on the buttons, especially for international buyers. And a custom button cannot provide any of the functionality PayPal is looking to provide with PayPal Payments (e.g. checkout via popup window or features such as Vaulting or Pay Later).
These features may come at some point, but they are not a priority for now.

We understand that there are some isolated cases under which the delivered language may not be the expected one, but there should still be an explanation for the behavior. Which language is displayed relies on multiple factors and is decided per user. This would be a better thing to look into together with the PayPal MTS but please also consider reaching out to the plugin support if any questions arise, as the team is happy to help.

For now, the only way to present the buyer with a regular payment button, is only to utilize the express buttons. This means disabling “PayPal on Checkout” and only displaying the buttons on the non-Checkout pages. When the buyer initiates a PayPal payment from e.g. the cart page, they are redirected to the pre-filled Checkout page and confirm the payment with a regular “Place order” button.

PayPal Payments is undergoing some optimizations for German merchants following the recent release of the Pay upon Invoice integration, and we hope to be able to share more soon.
I must dampen your hopes regarding the render hooks, though, as these likely won’t help with the requested modifications. For any remaining questions though, please open a thread in the support forums as we try to keep the discussion in reviews at a minimum. Thanks!

Kind regards,
Niklas