[ECP-9564][ECP-9693] Provide adminhtml configuration option for Payment Methods

[DanieliMi]

Is your feature request related to a problem? Please describe.
Currently there is no easy way to configure the payment method titles for non developers. They are all configured in config.xml but no adminhtml configuration is provided via system.xml.

Describe the solution you'd like
It would be nice to have the configuration available in the adminhtml so the customers can change method titles themselves without a developer having to set the config via CLI.

Describe alternatives you've considered
An alternative would be to not use the Magento configuration at all but rather use the title provided by the adyen backend response.

Additional context
Might be realted to #2854.

[aschrammel]

#2854 is pretty sure related this one.

For Credit Card it'll just work fine, but for all other payment methods configuration won't have any effect unless configured in Default scope. That's what is outlined in the linked issue 😄

[candemiralp]

Hello @DanieliMi,

Thank you for raising your concern and creating a issue for this. As @aschrammel mentioned, we already have an internal investigation ticket to tackle this issue. Therefore, I'm adding this as the sub-task of #2854 as it's a duplicate.

Best Regards,
Can

[candemiralp]

Hello all,

Adding sub-task wasn't a good idea as closing the main issue might not auto complete the sub-tasks.

I am closing this duplicate issue and please follow #2854 as we already have an internal ticket assigned to that issue.

Best Regards,
Can

[DanieliMi]

Hi @candemiralp, I am not 100% certain it is a duplicate. #2854 aims to provide store scoped translations, while this issue aims to provide configurable options within the adminhtml. If adding adminhtml configuration (via system.xml) as well as store scoped translations is within the scope of the the other ticket the close is perfectly fine. But as I said options within the adminhtml would be a nice feature.

[candemiralp]

Hi @DanieliMi,

Thank you for your timely response. I partially agree with you. We've also just now realised #2854 is complaining about only the configuration paths are not used while determining the title in different scopes. You can see my comment there.

As we support ~100 payment methods, it's not feasible to add a title input field for each one in the admin area. We are leaning towards using Adyen's translations for titles provided by Checkout API in /paymentMethods API response. This response contains the titles translated based on the shopperLocale field provided in the API request.

However, this will be a breaking change so we've decided to implement it as a part of V10 of the plugin. ETA of V10 is around the end of Q1 2025.

Please let me know if you have any further questions about this implementation and thank you for reporting back the validity of the issue.

Best Regards,
Can

[DanieliMi]

Hi @candemiralp, thanks for reconsidering! Yeah I can perfectly understand that adding 100 fields is quite a lot. I am perfectly fine with using the titles provided from the Checkout API. For us there is currently no rush since in our case the store scope title actually works (using 9.12 with the hyvä compat).