rosen | Modular proxy tunnel that encapsulates traffic | Proxy library

You need to check if name state is set, and if so, then proceed with the payment. Right now, your handleSubmit() function does not check for name at all, or pass it in the confirmCardPayment() Stripe API call.

Your handleSubmit() function should look like this:

For me your second solution is working

As @sinanspd mentioned, you need to use Stripe Connect for this, and I'd also recommend checking with Support to make sure your use case is supported.

The Client Secret comes from the Payment Intent, which you have to create first on the server side, using both the Customer ID, and their attached Payment Method ID.

https://stripe.com/docs/payments/save-and-reuse#web-create-payment-intent-off-session

As long as you use the same instance of elements to create and mount all of the separate card elements, you can pass any of the mounted card parts to confirmCardPayment(). Stripe.js will group them together automatically. So for example:

Your code is calling the PaymentIntent Confirm API but you're passing a PaymentMethod id (pm_123) as the first argument instead of the PaymentIntent id pi_123 which is why you're getting that error. Instead, you need to make sure you pass the PaymentMethod id inside confirmOptions and the PaymentIntent id as the first argument.

Relatedly, your code is creating a PaymentIntent but also passing Confirm = true which means you are already confirming it. And right after you are trying to re-confirm it which does't really make sense. You should pass the PaymentMethod id when you are confirming it.

If you want to create and confirm a PaymentIntent in one call you would do this instead:

Assuming that "OTP" is a "one time password" as part of a 3D Secure flow, then you can trigger this in test mode by using the SCA regulatory test cards such as the 3155 or 3184 card.

It's not clear where your error is coming from, but if you can share more detail with reproduction in test mode then someone may be able to offer more suggestions.

Note: I originally answered this question thinking you wanted the path taken by the optimizer, not the value during optimization. I've updated the answer so that it shows both, but you're probably only interested in the second plot.

The object returned by differential_evolution does not contain the path towards the result, nor the values along the way. However, you can use the callback argument to provide a callback function that gets called on each iteration. That callback can then record the progress.

For example:

It looks like the problem was mismatching the start and end span/p tags for the para information.

HTML with mismatched opening and closing tags causes the javascript DOM parser to miss elements despite them actually being on the page.