How to translate Buy Now button?

Hi @kybernetikservices,

The buttons, labels, taglines, and PayPal interface are all translated automatically by PayPal. It is not possible to do it manually as there are no strings to translate. It’s all JavaScript coming from PayPal directly. You can change the desired label per button, but the “Buy Now” label is the one that is recommended for German merchants.

When requesting the smart buttons, PayPal checks eventual PayPal cookie locale settings and if there are no PayPal cookies, it will attempt to use the browser or system language as a fallback.
We are working on a few features that could be interesting for German merchants, in particular, like for example a language override to force the PayPal buttons and interface in the locale of your site.
It’s difficult to judge, but this will probably happen sometime later in Q1 or in early Q2 together with other improvements for the German market like a “Pay per invoice” payment method.

So for now, most of the relevant front-end translation happens automatically.

Kind regards,
Niklas

Thank you @niklasinpsyde for your reply.
The truth is, on my test enviorment the button has the Englisch text “Buy Now” on a German shop, with a German located browser and a German operating system. It seems your callback does not work properly.
So, in my opinion your plugin is not useable in Europe because it does not follow the European law. It says the button has to be titled with “Buy Now” in the local language. At least in the shop language. And this does not work.
Can you confirm this?

Hi @kybernetikservices,

For now, the translation of the iframe content is handled by PayPal directly and usually reflects the language stored in eventual PayPal cookies on the device.
For us, it works as expected in the majority of cases. There used to be some issues with the translation on iOS devices but that was resolved by PayPal recently.

If you could maybe share with us a copy of your system report from the staging environment, then we’d be happy to take a closer look:
https://paypal.inpsyde.com/docs/request-support/
Please also include a link to this thread.
Thanks!

As mentioned previously, we are adding more (relevant) features to achieve feature parity with the previous Checkout plugin. Beyond that, we are working with PayPal and PayPal Germany to make sure German merchants can transition smoothly to PayPal Payments once our PayPal Plus plugin will be retired as well later this year.

Kind regards,
Niklas

I can confirm german translations are not working in firefox at all, making the plugin completely useless in germany.

Tested in multiple testing environments, multiple machines, browser versions, etc. Although it seems to work in all other major browsers, Firefox always shows “Buy Now” instead of “Jetzt kaufen”.

Also is there any way to style the buttons (except for the three color options)? Styling does not fit our Shop at all, making it look very unprofessional.

I also have the same problem. The text ‘Buy Now’ doesn’t get translated in german. In my case, the behaviour is a bit random. The text get translated sometimes in Firefox, but it doesn’t get translated in Chrome. I have tried in different and in different browsers but no result.
We are now using old Paypal Standard, but wanted to move to the newer version. There is another problem we encountered in this version. When user click on the Buy Now button, it doesn’t check the required fields. It redirects to Paypal even if the required fields are empty.
Hoping to get these problems solved soon, so that we can move to the new version.

Hey together,
just to give the topic more attention, since it certainly affects more people: Unfortunately, I can confirm that in a store with language “German” the button is displayed in English. As the previous speakers already mentioned, this unfortunately leads to the fact that the plugin or the button does not meet the EU requirements and can therefore not be used.

However, since the plugin is virtually the only valid way to implement an appropriate PayPal integration, I wish a classification with high priority for all users in the EU. ??

Thanks in advance! ??

Kind regards,
fr1000

We also have exactly the same problem.

I can confirm german translations are not working in firefox at all.

Tested in multiple browsers. It seems to work in Chrome and Edge. In Firefox always shows “Buy Now” instead of “Jetzt kaufen”.

We are now using old Paypal Standard method.

Thanks in advance.

Hi folks,

The plugin does not actively translate the PayPal interface, like the buttons. PayPal automatically determines the language based on a few factors like cookies in your browser or the browser locale.

In most cases, the browser configuration is relevant. German labels will be displayed when Deutsch (Deutschland) de-DE is selected:

Deutsch de (or any locale without country code) may not be recognized by PayPal, but the example smart buttons here are working the same way. You can configure different locales in your browser to try it out.

We understand you may want to force the display of a German label if this is your primary audience. This functionality is not available yet, but it’s still on the roadmap, albeit with no estimate.

Kind regards,
Niklas

Hi @niklasinpsyde .

Please allow me to write that what you are trying to say is a bit nonsense.
We have to follow the German law for online shops. And they say, the “Buy now” button has to be in German. Thats it and this is what we have to do.
In court we cannot argue that the settings of a browser were maybe this or that. Because we can’t prove it!

The language settings in a browser are not a parameter for the law. So, what ever you want to tell us, it is a technical issue. And this is such an issue that we can not use this plugin for a German online shop.

Your plugin is useless in Germany and if we do it right, it’s forbidden to use because it’s not compliant with the law.

You’ve been ignoring this important fact for almost a year.

Hello everyone,
I also want to point out another thing. The button does not check the required fields are filled in or not.It redirect to Paypal without checking if required fields are filled. Has anyone face the problem?
If yes, can you tell me why this thing is happening and what ist the solution?

Thanks,
Faisal

Hello @niklasinpsyde .

I come back to this topic and hope you do not ignore the following information:

The language of the PayPal button is related to the browser language. Thats correct but against German law. Beside this, it is not working as it should.
In your sample (screenshot) you show the language Deutschland (Deutschland) with the code de-de. Unfortunatlelly at least Edge and Firefoxe have the pe-setup of the German language Deutschland with the code de. With this (standard) setting the text on the PayPal button is English. Only if I actively change the language to Deutschland (Deutschland) with the code de-de the button has German text. Otherwise it stays in English even if I use the standard pre-setup of Deutschland with the code de.

This is annoying because this situation prohibits the use of the plugin in Germany – if I want to follow German law.

It’s also annoying that PayPal doesn’t take this fact seriously and fix it.

What has to happen for someone to take care of a solution?

Hi @kybernetikservices

We understand that you are not satisfied with how the language detection works on PayPal’s end and have repeatedly raised your concerns with PayPal. But the final word about what is included in the integration and what not is with PayPal, and we have only recently received the green light to develop a solution for this.

So the next update later in January will include a setting (& filter) to override the locale for the buttons. Then you have full control over which locale is used.
I hope this helps!

Kind regards,
Niklas

Thats a good news @niklasinpsyde. Many users will be happy about this belated Christmas present.

@niklasinpsyde I’m wondering when we can get this long awaited feature.

The task seems to be still open. When will it be released?

Hi @kybernetikservices

That’s a good and valid question. Shortly before the anticipated release, we identified some minor UX issues and inconsistencies with the new feature that required another round of development to make it more consistent and the purpose more clear.

However, since the work on this was started, resources had to be allocated to other tasks with a higher priority.
We regret the unexpected delay, and the only thing I could provide for you at this time is this preview package with the language override feature, in case you would like to give it a try and report back how it works for you.
This is built on the update 2.0.1 and while it did pass all critical tests, there are minor improvements still to be made. Functionally, it should be alright, though.
That being said, I hope this can be included as an official feature in the next feature update 2.1.0 (the one after the upcoming 2.0.3). Ultimately, it’s not up to me, though.

Kind regards,
Niklas