#italiano4035
1 messages · Page 1 of 1 (latest)
Hi there 👋 are you just using the Laravel framework, or are you also using Laravel Cashier?
Gotcha, we're not too familiar with how Cashier works since that is Laravel's abstraction of our API, so I'm not sure what could be causing that behavior. I would suggest starting with the Laravel Support team, who I believe will be better suited to assist here.
if I wasn´t using cashier is it necessary to do the manual intent instead of auto??
Can you elaborate on what you're referring to? Are you talking about manual capture versus automatic capture?
yes exactly
Using manual confirmation is not a requirement, no. It's an option that is available for flows where leveraging it would satisfy a business requirement.
ok cool, thanks I think I am missing something with Laravel probably need to create a pay intent manually the only weird bit is that in local creates both calls to stripe with just the charge method
In general I wouldn't expect you to need to redesign any of your flow just to get things to work in livemode. My (possibly naive) guess would be that there is either a difference between the test mode and production code, or there is an error being encountered somewhere in live mode that didn't come up during testing.
With Stripe, you do need to explicitly make a request to create a Payment Intent (in case that's what you were referring to by manual vs auto), and I wouldn't be surprised if the Cashier implementation was the same.
yeah I will ti debug a bit in production first because Laravel docs says that with method charge is enough to make a single payment and it actually works in local tests I have done so maybe something in production is triggering not to call the payment_intents method