#fladson_error
1 messages ยท Page 1 of 1 (latest)
๐ 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/1400079130279546904
๐ 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.
- fladson_docs, 22 hours ago, 23 messages
Is this expected the expected outcome?
Yeah, you need to attache a Customer to the PaymentIntent in order to use it later
Thanks for taking a look at this @final quartz .
Yes, the PaymentIntent has a customer, that's fine, but I was expecting the PaymentMethod to also return it, which it does when the payment intent is successfully confirmed. Why is it not returned when it fails?
How are you creating the PaymentIntent ?
Using the Ruby SDK Stripe::PaymentIntent.create(params)
params is something like this:
{amount: 869000, capture_method: "manual", confirm: true, confirmation_token: "ctoken_1RqYSPGK3Gnpfa3ObHKGyFW0", currency: "USD", customer: "cus_SlOHC0hGIFTEks", description: "Description", metadata: {HIDDEN}, off_session: false, automatic_payment_methods: {enabled: true, allow_redirects: "never"}, statement_descriptor: "HIDDEN", on_behalf_of: "acct_1GLoS9GkS2zqeS82", transfer_data: {destination: "acct_1GLoS9GkS2zqeS82", amount: 760000}, transfer_group: "7bdfa13f-dcd1-43b3-b2b4-fa53a089ac67", setup_future_usage: "off_session"}
๐ taking over for my colleague. Let me catch up.
the PM gets only attached to a customer upon success of auth which in the case of a PI confirmation it's the success of the PI
Thanks for taking a look @oak saffron
Okay, I see, so I guess we need to change our approach a little bit.
Thanks for confirming it.
even if you use SetupIntents or Attach PaymentMethod APIs you're going to face the same issue
we only attach the PM upon success of auth
I see. We are facing this issue when attempting to create a credit card from the PM, so I think we need to revisit this to skip the credit card creation when the PI confirmation fails.