#IanGungee
1 messages · Page 1 of 1 (latest)
Update: the dashboard may be displaying incorrect information? The error I get as a response from the server says the status is requires_confirmation
In the first couple screenshots, it looks like you're viewing an Event object. The contents of those objects are preserved because they are point-in-time records, their contents are not updated based on future changes that happen to the related objects (like the Payment Intent).
I see. That would explain the discrepancy. So even if I pass a payment_method param at the creation of the payment intent, it will be created without it? i.e. the event will display no payment method?
I've verified all fields have valid values
It depends on which type of event you're looking at (can't tell from the screenshots). If you're looking at a payment_intent.created event then I would expect it to have the ID of the Payment Method if one was provided in the creation request. If you're looking at a payment_intent.updated event that occurred later in the intent's lifecycle, then it is hard to say what should be present without knowing what led to that event being triggered.
It was a payment_intent.created event, but what's shown in the dashboard seems to have no impact on the actual payment flow, so I think you can go ahead and mark this as solved. Thanks, Toby!
Sounds good!