Open MarcusWolschon opened 7 years ago
Hi Marcus,
Thanks for the suggestion. At the moment the language is determined based on the region of the merchant. Reader support for the language of the customer's card is on our backlog, but it has not been scheduled so it may still be a little while off. So that we can keep track of which integrators are interested in certain features, could you please tell me you are working with?
Thanks, Angus
We write our own software because nobody else did a Magento 2.0 integration. POS functionality and payments are but a small part.
We do however also often use your Android App standalone and have the same need there. Without any API involved.
"Reader support for the language of the customer's card is on our backlog, but it has not been scheduled " Has it been scheduled within the last 7 month?
Hi Marcus,
Unfortunately there are no changes to date, when we start to tackle this issue we'll inform you here.
Angus
It's been 2 years and this is still a huge issue for our customers.
Any update on this issue?
If all else fails, It's not THAT hard to force a different locale on a Context. (For NumberFormat and DateFormat you have a locale parameter, so that's not a big issue.)
public void forceLocale(@NonNull final Application application, @NonNull final Locale newLocale) { final Resources resources = application.getBaseContext().getResources(); final Configuration config = resources.getConfiguration(); config.locale = newLocale; resources.updateConfiguration(config, resources.getDisplayMetrics()); }
@MarcusWolschon Thanks again for following up here. Unfortunately this improvement is still in our backlog and we have not yet been able to deliver. We will keep you posted. Thanks
So we have 2019 now. Any change?
We would also be interested in this.
I would need this feature for my customer, too. He can not understand, why it is not possible. The payment builder would only need an additional parameter.
I would need this feature for my customer, too. He can not understand, why it is not possible. The payment builder would only need an additional parameter.
A language parameter? SumUp knows the language of the customer's card. The app initiating the process doesn't.
Yes but the screen is in the device's language. I need to support different languages at once. So the customer can choose this language.
Example:
So if there would be a parameter like a language "en", "fr", .... during the SumUpPayment.builder().... .build(), this would be a great improvement for the end user UX.
Ok, so as a workaround have the customer manually choose a language instead of reading the language from whatever card the user presents and selecting it automatically because for your app more then just the SumUp payment-process should be in the customer's language.
The app I'm working for is for the merchant and with the SumUp terminals the phone needs to be presented to the customer for a signature after a card payment in some cases. So the user has already inserted the card and the SumUp app has opened.
The suggested feature would be much needed over here in Finland, too.
Is there at least a way for the API to tell the app what the priority-sorted list of languages (possibly just 1 entry) for the customer is? Probably via a listener-callback or Livedata or intent.
Still not possible? @jahenry
I really don't believe that this feature is requested 4 years ago and still not implemented. I guess this will never be implemented!
I think SumUp doesn't know that other languages then English exist on this planet or that dealer regularly sell to people from other countries then their own in-person.
I agree, this is unfathomable.
On Fri, Dec 3, 2021 at 5:52 PM Marcus Wolschon @.***> wrote:
I think SumUp doesn't know that other languages then English exist on this planet or that dealer regularly sell to people from other countries then their own in-person.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/sumup/sumup-android-sdk/issues/30#issuecomment-985629388, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABOO3YKSO3DBW6VJYON5VBTUPDRSBANCNFSM4DXO3D4Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
International clients are really confused when they get Dutch instructions on the screen. Please implement this after all.
At the moment the card readers cannot identify the language of the card used to make a payment. By default, they will come with the language of the country where the SumUp account was registered. However, it is possible to change the language of the terminals. Please contact our support team so that they can make the change.
Will the request for a signature on the phone app be shown in the language the bluetooth terminal is set to, if we go through that procedure?
Hi, this is not true, tatianalizarazo, I'm in France, in my computer, my dashboard is in french BUT the app in my phone is in spanish!! and the tickets is in spanish... my costumers don't understand spanish and it is not possible to change the language. I contact the support team one year ago and it is not possible.
what about adding a language option to SumUpPayment.builder()?
what about adding a language option to SumUpPayment.builder()?
Yes. That's all we're asking for here.
According to support there is no way yet to have the SumUp card reader ask the customer to enter pin, wait, sign, ... in another language. There should be a way towards select a UI-language with every payment request, so that international customers have a clue what the device wants them to do. This is a huge problem at international events especially with French customers.