Comment to 'Hard coded payment options in Stripe'
Comment to Hard coded payment options in Stripe

  • Hi @thomlin

    I wonder why do you ever need to add Stripe payment method types manually in a file? Aren't they added automatically in the Stripe integration with UNA?

    Sorry for asking, it's because I am having a weird issue while testing Stripe (probably a setting issue). The payment methods I enabled in my Stripe account dashboard are not showing on my UNA site. Only the 'Card' method is available on my UNA Checkout.

    @Anton L, after enabling payment methods from the Stripe account dashboard, do we still need to add them manually in the BxPaymentProviderStripeV3.php file?

    If so, every time there will be a UNA update, we will have to edit that file manually again to put back those payment methods, right?

    Can't we have an option in the UNA payment settings where the admin can select which payment methods should be available for Stripe and that information saved into the database?

    Thanks

    • T

      That's because Stripe offers a vast number of different payment methods. Credit Cards are globally means of payment. Therefore it's rather safe to hardcode it as the only predefined option. For every other payment method you configured in your Stripe account, you have to add it by its name code manually to the payment types array in una stripe connection.

      Since the stripe connection is part of the una core, it's necessary to update your payment methods in the connector after an update, again and again. That's why I asked for a better solution, if that can be done (because for full automation the connector would have to have permission to read payment methods from a stripe account or you do the dirty hack and ask the user in a studio form, which payment methods he has defined and then the system replaces this input in the payment types array in una code dynamically).