Try our conversational search powered by Generative AI!

New payment configurations added in new releases are enabled by default - impact on prod



after an epi update we noticed that our payment flow was changed.

Apparently -I assume during a commerce migrate step- a new payment method was added. 'Pay by phone' in the language es.
The new method was also enabled and set to default.

Isn't this a dangerous approach? Suddenly there was a payment method added which enabled free purchases on the shop.

If you start a project, you take the defaults into account. But once the development is started, you don't expect that new (enabled) payment methods are added automatically.

Suggestion, all configured payment methods are disabled by default.

I'm I correct? Or do you think there something wrong in our codebase.
I also could find these changes in the release notes.

Kind regards,


Jul 11, 2017 11:55


anyone any feedback on this?

Kind regards,

Sep 17, 2017 14:31

I haven't heard anything regarding this issue, and it's of course not something we want to do. Which version were you on, and which version did you upgrade to?

Sep 17, 2017 17:12


I must be the upgrade (commerce) from 10.4.3 -> 10.6.0 or 10.6.0 -> 10.7.2. Not sure anymore.



Sep 18, 2017 15:36
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.