#ketaaa-sepa
unique coyote
thanks
pure nexus
it was confirmed during creation of the PaymentIntent (https://dashboard.stripe.com/test/logs/req_vJ0LHrQeYRDlo0) by passing confirm:true
I don't know why Magento would try to confirm it again, that would be a possible bug in the plugin
unique coyote
okay thanks for the hint
i have sometiems this error aswell
let me send you
req_p2T3YXTaxOZcaN
confirm: true is used for offline payment right?
pure nexus
confirm: true is used for offline payment right?
it can be yes
pure nexus
req_p2T3YXTaxOZcaN
that's kind of the same thing really, it's just the plugin trying to confirm the PaymentIntent a second time when it doesn't need to
if this causes some actual problem for you you might want to reach out to the support for that Magento plugin
unique coyote
Can I remove the confirm flag and let the plugin confirm the payment again?
because i'm setting this confirm
pure nexus
Can I remove the confirm flag and let the plugin confirm the payment again?
no idea, I don't know what control you have over individual API parameters when using that plugin.
(this Discord is for developers directly integrating with our API, we know very little about plugins)
unique coyote
no worry
i will take other the plugin prt
just need to understand 😄
It's me who added the confirm flag to do "off_session" payment
I think I could not do off_session payment without the confirm flag
pure nexus
that is usually how you do an off-session payment yes
usually you create the PI and pass confirm:true and off_session:true at that point
unique coyote
main.DEBUG: The parameter off_session cannot be passed when creating a PaymentIntent unless confirm is set to true. [] []
pure nexus
you can instead create the PI without those, and then later call the /confirm API passing off_session:true ; it's the same thing. But usually there's no point to make two API calls when it could just be one.
unique coyote
ok so the goal is to avoid the confirm call when i'm making offline payment, is that right?
pure nexus
I don't know, are you writing code that triggers that confirm call?
if so, don't do that
unique coyote
i'm not but I can do some adjustment to the plugin itself
pure nexus
if not and it's the plugin doing that itself, then you have to ask the maintainers of the plugin
pure nexus
I mean you might break something else by changing the plugin code
unique coyote
but my code worked fine for credit cards but not for sepa 😄
it's okay though, thanks for your help
I understood what's going wrong
I checked the plugin code and it tries to confirm again because the payment_intent status is "processing" when using SEPA and "succeed" when using credit cards.
Any idea why?
pure nexus
nope
I mean I know why the status is processing if that's the question
that's how SEPA works, it takes multiple days for the transction to clear, in the mean time the PaymentIntent is processing. I don't know why you'd try to confirm the PI again, you're supposed to just wait for the webhook notification where we tell you the payment succeeds
I have no idea what you're doing overall really since the plugin should do all this for you if you're using a version that says is officially supports those payment methods