#quro_api

1 messages · Page 1 of 1 (latest)

weary thistleBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1466712417928216607

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

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.

rocky egret
#

👋 Hi there!

dense basin
#

hi

rocky egret
#

What is it that you are trying to achieve? The last_payment_method object is just there for information; there is no ID associated with it.
You can prefer to use the payment_method object, whose ID you would see on the Payment Intent

dense basin
#

well i am just confused about the structure of the api itself.

#

there is paymentmethod card once on payment method

#

and once on paymentintent

#

there sure are more instances i can look it up, but cant this be merged into one type so it is at one place

#

my question is if those two are the same object or not

rocky egret
#

They're not the same object

dense basin
#

thanks

#

rant off

rocky egret
#

The last_payment_error is just a snapshot of the card that was used. It's possible for a PaymentIntent to return to requires_payment_method state, and then you could attach a different payment_method ID, for example