#CodyL - PI migration
1 messages · Page 1 of 1 (latest)
those would be my reference that I look up if there is a dispute or if I need to call a refund on it.
so that I can void the record on my side and update the customer balance
I don't use stripe for billing or anything. just payments
Gotcha. So I would store the PaymentIntent. You would get more info that way (and you could always get to the charge object)
I also still need to use some sources as ACH Credit Transfer has not been migrated yet
so then I would have a mix of charge id's and a payment intent id's
There would be nothing wrong with continuing to store the charge IDs if that's what you're asking
But storing the PI would give you a bit more
ok though I can always walk from the charge to the PI right?
and safe to say the charge object is never going away
well no sooner than the PI would
You are safe for the near future at least
That kind of change would be a massive undertaking and would affect everyone using Stripe so such a change, if it ever were rolled out, would be adequately communicated
I guess I still haven't really wrapped my mind around what a PI really is
PaymentMethod is similar to a Source
PI is more like the lifecycle of a "payment"
Yes that's true. I recommend reading our docs on each of those objects before trying to use them though as you'll get a better understanding