How to use Stripe client side events

@MohamedTammam I'm using Stripe PHP package to make a one time payment. The backend handles the payment amount and everything while the front end is being used only to pass card details. so now I just want a way to fetch the success response to do backend actions. I'm trying to figure out what to do in this case.

@martinbean Okay so can you just help me wrap my head around webhooks? I mean,

I have a stripe controller that creates payment intent with amount and currency on checkout page mount.

$paymentIntent = PaymentIntent::create([
                'amount' => $amount,
                'currency' => $currency,
                'automatic_payment_methods' => [
                    'enabled' => true,
                ],
            ]);

then a user makes a payment and I'm confirming the payment like so

async function handleSubmit(e) {
  e.preventDefault();
  setLoading(true);

  const { error } = await stripe.confirmPayment({
    elements,
    confirmParams: {
      return_url: "url to where???????",
    },
  });

}

Now what? where should the return_url take the user to? I was considering that it takes the user to a page where it sends another request to the controller and check if the submission was successful because that's the only way I could see that can be adhering to Stripe docs

Stripe recommends handling the payment_intent.succeeded, payment_intent.processing, and payment_intent.payment_failed events.

Listen for these events rather than waiting on a callback from the client. On the client, the customer could close the browser window or quit the app before the callback executes, and malicious clients could manipulate the response. Setting up your integration to listen for asynchronous events is what enables you to accept different types of payment methods with a single integration.

Now if i'm to use webhooks, what should I change? you don't need to code anything just give me the idea and I will dig up the internet

@MooseSaid return url is what you want the user to see after they complete the payment. ie, a thanks for your order type page, or whatever.

But really you need to confirm that stripe is happy by creating a webhook endpoint and then setting this in the stripe website.

You tell Stipe what events you want to listen to, and the URL that should handle it.

For instance, I have an API route /stripe-webhook which receives ALL webhooks from stripe, validates its stripe calling the endpoint and then processes the event. Processing might just involve setting the status of an order to 'paid'. This bit is really down to your app to decide. Since the webhook is asynchronous, you need to add data into the payment intent that lets your app know which transaction or customer the webhook is concerning. One way is to store the payment intent id, but you could also put meta data in the payment intent, such as order id

@Snapey Thank you so much! I decided to go for Spatie package and handle the webhooks with jobs.