beware of PCI compliance requirements [0] but you can either create a payment method explicitly [1] or include the card details when handling a card payment [2] `{payment_method_data: {card: {…}}}`
I am aware of [0], but unless I'm missing something neither of the methods allows creating a payment method on the client and then passing its ID to our backend to be executed and set up for 'future use'.
That's the flow we had with the v2 and that's what we can't replicate with the v3.
That's the flow we had with the v2 and that's what we can't replicate with the v3.