#cashiersprit - PaymentIntent status
wicked carbon
Just to confirm, is the customer adding any payment details before they go back to the overview page? If they are, is your code attaching their payment details to the PaymentIntent? https://stripe.com/docs/payments/finalize-payments-on-the-server#payment-method-details
pallid helm
no, client does not in put anything to payment element form, at sub card info form straight go back to overview page to update price then go to sub card info form again, submit form, the status is requires_payment_method
amount: 2100
amount_details: {tip: {…}}
automatic_payment_methods: {enabled: true}
canceled_at: null
cancellation_reason: null
capture_method: "automatic"
client_secret: "pi_3LW4BX4M9E4kTTfW1GzjdUSZ_secret_xGdZ7RrJVMWMhq0opsVMfMluB"
confirmation_method: "automatic"
created: 1660335023
currency: "usd"
description: null
id: "pi_3LW4BX4M9E4kTTfW1GzjdUSZ"
last_payment_error: null
livemode: false
next_action: null
object: "payment_intent"
payment_method: null
payment_method_types: ['card']
processing: null
receipt_email: null
secret_key_confirmation: "required"
setup_future_usage: null
shipping: null
source: null
status: "requires_payment_method"
[[Prototype]]: Object
is the above info useful to you? can you check which step is missing?
btw, this is paymentInent from const {paymentIntent, error} = await (this.stripe as any).updatePaymentIntent({ elements: this.stripeElements });. the error is null
wicked carbon
thanks for the context! do you know if your server is attempting to confirm the PaymentIntent? this is described in steps 5 & 6 here: https://stripe.com/docs/payments/finalize-payments-on-the-server#payment-method-details
this would come after you've updated the PaymentIntent with the customer's changes after they went back to the overview page
pallid helm
yes, our normal workflow is good following https://stripe.com/docs/payments/finalize-payments-on-the-server#payment-method-details
this is an edge case happened when user go back to update price and then to submit form
confirm paymentintent is the last step. but the issue I described above is a very early step, happened at updatePaymentIntent step
basically, stripe side seems did not receive customer submitted card info, if I understand requires_payment_method correctly 😉
wicked carbon
could you share the PaymentIntent ID for that example edge case?
I have to head out but my colleague @bold wharf will stick around
pallid helm
id: "pi_3LW4BX4M9E4kTTfW1GzjdUSZ" is this payment intent id? in #1007744617032204338 message
bold wharf
👋 give me a minute to catch up and i'll take a look
bold wharf
Hmmm... this is definitely strange. Are you seeing any errors/anything in the console or network logs when you call updatePaymentIntent?
pallid helm
I did not see any particular special thing. I think at your side, you can check payment intent status, right? can you tell me why payment intent id: "pi_3LW4BX4M9E4kTTfW1GzjdUSZ"status is not changed after client submit card info?
did you receive card info?
bold wharf
Well the issue here is that I see the update request, but no card information in the request
pallid helm
en, strange, so you mean actually we submitted updatePaymentIntent action, but no card info was included, like card number, expire date, and cvc, nothing is included?
bold wharf
Correct - you should be able to see the update request in your dashboard as well: https://dashboard.stripe.com/test/logs/req_LErLI6Th9zn89x
Do you potentially have a test side that replicates this issue that I could try out?
pallid helm
that's very useful info. I don't know the https://dashboard.stripe.com/test/logs before
sorry, it is our internal url. I think https://dashboard.stripe.com/test/logs will help me to debug issue
that's a lot.
so far so good