You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In internal HelpScout ticket https://secure.helpscout.net/conversation/1641517421/22778/ we had a customer who added the payment method iDEAL with the label iDEAL and also the value iDEAL, this while the value ideal is required for the iDEAL payment method. I think this problem also sometimes occurs with Gravity Forms, so I think this setup is too error-prone. How can we improve or simplify this?
The text was updated successfully, but these errors were encountered:
The correct values to use are filled out when adding the payment method field. Why would the user change the value? When unsure about which values to use (when not getting redirected to the correct payment method on form submission), a new payment method field can easily be added — as replacement or reference.
Unfortunately, Ninja Forms does not seem to use some kind of pre-defined lists when 'importing' field options, as we hook into with for example Formidable Forms to add payment method options with the correct values in an existing payment method field.
As for Gravity Forms: the values of currently active payment methods can not be changed in a payment method field. I don't see any issues there (also not in support).
In internal HelpScout ticket https://secure.helpscout.net/conversation/1641517421/22778/ we had a customer who added the payment method iDEAL with the label
iDEAL
and also the valueiDEAL
, this while the valueideal
is required for the iDEAL payment method. I think this problem also sometimes occurs with Gravity Forms, so I think this setup is too error-prone. How can we improve or simplify this?The text was updated successfully, but these errors were encountered: