#nickderobertis
1 messages · Page 1 of 1 (latest)
Hello, do you have the ID of an event like this where the payment method was null? (evt_123)
Thank you, will check in to that and get back to you
Thank you!
Sorry for the delay there. It looks like a Source was used to confirm that payment intent. You can see "source": "card_0Mty79WVt9vwrtEDLwzmX2fv", in that event that you sent the ID to. Sources are a legacy object for representing a payment method that came before PaymentMethods https://stripe.com/docs/api/sources
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Do you know how that payment intent and source got created? Not immediately seeing how
Ahh, I see. Probably because we are in the middle of migrating to payment intents, so most of the system is still on an old integration using charges
We are also migrating to setup intents for adding new payment methods, but we haven't implemented that part yet
Before we close this, I have a quick follow-up question, just checking code quickly
Would we be able to send a Source ID like card_xxx to GET /payment_methods/${id}?
Yes, the payment methods API is backwards compatible with the Sources API, so you can just use the card ID anywhere that you would use a pm ID
https://stripe.com/docs/payments/payment-methods/transitioning#compatibility