#hellotika
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- pinkmel-pending-webhooks, 1 day ago, 7 messages
- pinkmel-card-funding, 1 day ago, 4 messages
Payment methods don't have a status
They simply represent a payment method
Only payments have statuses
And setup intents, etc
But a payment method object has no concept of status
When pm gets attached to cust, it’s like a setup intent confirmed though, correct?
Yeah a setup intent has a status
A payment method does not
But payment method being attached doesn't necessarily mean it was from a setup intent
What are you really trying to do here?
We save a cc locally and this has a pmID and status.
If we manually say call stripe to create a pm the attach to a cust, we want you to create that cc object with a status (which is succeeded if we go thru setup intent)
There is no status
A setup intent has a status
So check the setupintent
ie this webhook event https://stripe.com/docs/api/events/types#event_types-setup_intent.succeeded
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
or this for a failure: https://stripe.com/docs/api/events/types#event_types-setup_intent.setup_failed
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
The payment method itself has no state
well other than attached/detached