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).