#Maxv - requires confirmation status
1 messages · Page 1 of 1 (latest)
Yeah,
pi_3Mict7FdCE6n8elI0jkVQ6yc
is there any way to change its status from 'requires_confirmation' ?
to 'requires_payment_method'
I am not sure. Can you try attaching a new Payment Method to it?
hmmm, if I do this it would still be with the same status but different method.
Or Is there any way to know if the modal was closed by pressing X ?
modal that is shown via collectBankAccountForPayment function
We don't track these events, unfortunately.
hmm, ok is there a way to detach the payment method from payment intent?
Have you tried setting the ID to a blank one?
tried setting it as null
Also is there a particular reason that you want it out of that particular status? You should be able to perform the same operations on it like trying to confirm with a different payment method
You passed an empty string for 'payment_method'. We assume empty values are an attempt to unset a parameter; however 'payment_method' cannot be unset. You should remove 'payment_method' from your request or supply a non-empty value.
Well yeah, we are checking client balance (via financial accounts API), asynchronously in back-end and if the balace is ok we confirm the payment, or send a failure mail.
In case of a failed email the client can pay again if he wants.
But because payment intent status is 'pending_confirmation' if the client closes the modal he will have the same flow as if he finished the modal with linking his bank because I dont know if he exited modal because he finished or becuase he pressed 'X'
Apologies for the delay. Still trying to think of what you can do here
Maxv - requires confirmation status
Thank you!
Still not finding a good way to do this. At that point it may be worth it to delete the old payment intent and create a new one if you need a fresh requires_payment_method status
so only cancelling?
I am surprised the failed payment doesn't move the status back to requires_payment_method here, I thought that is how that failure was handled
At the moment yes, I think that might be how this is handled. I can put in a feature request to see if we can put in a clearer signal that the user closed the modal without selecting a PM as this scenario does break what our docs recommend for checking that