#cactus-charge-legacy
1 messages ยท Page 1 of 1 (latest)
@final nacelle so really you care about the Charge not the Invoice here. I'd recommend dumping the Charge itself and looking at the raw response. On Charge you really shouldn't use the card property which was deprecated back in 2015 ๐
Look at payment_method_details instead
cactus-charge-legacy
Yea I recently just adopted this app and I dont want to make breaking changes just yet. For context, this is only a problem for a certain time period. Since its working 90% of the time
eg:
Invoices from early 2022 โ
Invoices from Mid 2022 โ
Invoices from early 2023 โ
Yep it's likely that some parts of your app are using a different integration/path. So don't look at the card property on Charge and read payment_method_details instead
Okay thanks guess i'll just have to refactor some stuff
Step 1: dump the Charge and look at waht's on it. I assume it'll have payment_method: 'pm_123' as a property instea and card: null or similar
Yup, Accessing payment method on the Invoice object does return the data I was looking for but I have the Stripe Objects modeled as Proxy Classes but PaymentMethod is not a valid Stripe object in v1.36 (I could be wrong here)
yea that version is from 2016 and we shipped the PaymentMethod API back in 2018
Ahh okay I'll try to upgrade to a more recent version