You're being discerning. And a little over-generous.
I'll counter - as a fellow 'older' one :)
There's a tendency to be over-conciliatory and exercise excessive tolerance towards folly, for fear of being labelled a throwback. Don't minimise the wisdom your age brings.
Some things just get worse, objectively, until a correction occurs. Reality is, there are perverse design incentives and it's also the younger people who are tearing their hair at the madness of gratuitous tech and UX as a cult/ideology.
It is almost always easier and cleaner to use their HTTPS name=value post interface directly if they officially allow it and support it.
Often you are going to get your payment information from the user in that format anyway, such as via a post from your checkout page, or as a row of named columns when you retrieve on file payment information from your database.
In that case submitting name=value pairs mostly just requires translating the field names from your checkout page or column names from database to the names that the payment processor uses, plus adding a few more name=value pairs.
Going through their language specific SDKs often requires building up some ridiculous object oriented mess.
Don’t get me wrong, touchscreen gloveboxes are stupid as hell, but as I get older and things change, i find myself wondering if I’m being discerning or closed-minded.