Comment to 'Hard coded payment options in Stripe'
  • P.S. If you'll take the challenge and create working empty custom module I'll continue with instructions. ο»ΏπŸ˜‰ο»Ώ

    That was ironic though! @Anton L It will be difficult and many of us won't make it.

    Please, would you mind just providing for the solution to this issue and improve the way the Stripe payment method system works in UNA? Please can you create that custom module with all the code needed to fix this problem and make it available for download on the marketplace?

    I think It is not a good pratice having the Stripe Payment Method Types hard-coded (added in a file manually) and overridden whenever there is a UNA update.

    What about if someone forget to manually re-apply the changes after a UNA update, then the payment method types won't be available to members anymore.

    IMHO, this is a crucial aspect of the UNA payment system. The solution should be added to the UNA core features. Thanks in advance for your understanding.

    • Now, that I set BxPaymentProviderStripeV3.php back to its original version, everything works like a charm! It's really magic. πŸ™Œ
      When does the lesson "Extending the module with putting data into the array by using Studio settings" start? ο»ΏπŸ˜‰ο»Ώ

      Hello. If you just want to control items of 'payment_method_types' parameter view Settings then it wouldn't be a problem. I mean to have a Dropdown with Card, Sofort and Sepa Debit choices.

      • How about a comma-separated list of arguments to fill the array with, individually? Of corse, the user will be responsible to configure his payment methods in Stripe accordingly.

        • Yes, it can be done this way. In this case you may use standard Text field. It's even more easier.