#lafafm-source
1 messages · Page 1 of 1 (latest)
yep, we consider source deprecated, you would use the payment_method_details object on the Charge for a consistent interface to the details of what card/etc was used
Yea, got it
But unfortunately haven't found any info about it
E.g. usually it appears on the api docs, but I don't see any deprecation warning in Charge section
yeah we don't always have that, it depends
basically source is there if you're using legacy objects, so existing code works
if you're using PaymentMethods you're expected to look for payment_method_details in your updated code. We had docs on that at one point but I can't find it right now