ducnguyenthe_code

[worn lance]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1443455269269934172

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[lapis laurel]

Hello team

[fresh lion]

Hi there

[lapis laurel]

Yes, hi you

Do you understand my issue ?

Tell me if you need more information to check it

[fresh lion]

Yes looking

Which interface are you using? Is it Payment Elements or Checkout?

[lapis laurel]

Stripe Checkout

Here is payment method element i integrated

[fresh lion]

Could you share the Checkout Id? cs_test_xxx or cs_live_xxx

Hmm where is this UI? Doesn't look like Stripe Dashboard

[lapis laurel]

After click checkout, buyer will be redirected to stripe page and process on there

yes, on live mode

[fresh lion]

Ah I see. Okie can you share the CheckoutSession ID cs_live_xxx?

Or the Checkout URL if it is still accessible

[lapis laurel]

Yes, wait me a minute

I have payment_intend, is it helpful ?

here is public key live: pk_live_51Q4zEADeGLYn1xV9IoE3R7QBs8KxUgIY2G5JlBjbVOoarBe0UikazQEiUXY7ndDw129ruT9CLIDxTKUmLD7sjXcK008aGtwda0

error payment_intend: pi_3SXfgWDeGLYn1xV93MdO8FTi

[fresh lion]

The Payment Intent doesn't seem to be created from a Checkout Session

Ah I see you created a direct PI with ideal

On your checkout page, how do you confirm the transaction?

Everything looks normal to me

[lapis laurel]

Buyer will confirm it after redirect to

Here is page that buyer will authorize payment (example is test mode)

[fresh lion]

Then your customer say what happen after they click on authorize?

[lapis laurel]

We could not know what happend after customer click authorized, we just known that payment_intend was success on Stripe

Via log system

[fresh lion]

It could be the customer lost internet access when returning to your site

So you got no nginx log of your return_url, and they may saw a disconnected UI

[lapis laurel]

Oh you mean customer may lost connect internet so Stripe can not call to return_url ?

We do not think so because after checking request time on server, other request of customer quiet quickly

[fresh lion]

WDYM by quiet quickly?

[lapis laurel]

Here is request time of customer to our server

you can see, it's so quick

So i think the problem dose not come from network

Could you help me to check the issue closely ?

The issue just occur sometimes, maybe 7-10 times each month

sorry, 7-10 checkout each month

it does not occur with all

So we can not replicate it on dev env

not only Bancontact, we meet a lots with Idel and Klarna

[fresh lion]

Yes but is this the same customer? You have many customers, right?

[lapis laurel]

no, it comes from different customers

not the same customer

[fresh lion]

Yes, so maybe only one of them has connectivity issue, and they never reach your server

Do you have any kind of session tracking?

Also, is this causing lost of service because you are giving your customer services based on return_url?

In that case, you would want to utilize Stripe webhook instead

It isn't depended on the redirection

[lapis laurel]

Could you help me to check if Stripe call return_url or not ?

This issue affect to us so much, customer reported that thay paid order on checkout page

but we not see order from our dashboard admin because return_url was not call, so we did not create order on our database

And from that, we can not received that order placed, we would not make fulfillment for them

They will open dispute on Stripe, it affect to our gateway trust

return url like that:
/api/checkout/pre/3bc928d11138456b94e1513a65f95adb/next/confirmed.json?payment_intent=pi_3SXv3EDeGLYn1xV90Lm96k7F&payment_intent_client_secret=pi_3SXv3EDeGLYn1xV90Lm96k7F_secret_zoDCO2jfuojSYQyC83fATsCNI&redirect_status=succeeded&x_system_id=

here is an example of other checkout

[fresh lion]

but we not see order from our dashboard admin because return_url was not call, so we did not create order on our database
This is exactly why you should use Stripe webhook instead of relying on the return url

We will send you payment_intent.succeeded event every time a Paymetn succeeded

[lapis laurel]

Yes, this so helpful

Let me discuss with team about this issue

our system currently is so big and complex

So changing from return_url to webhook flow need to consider carefully

Do you have any way to workaround for shorterm instead of changing to webhook flow ?

[fresh lion]

Yeah I know this is a heavy lift

For short-term we don't have great suggestions here unfortunately. Literally we don't know what happened on the customer browser at that time, just that it never reach your server

All we see is that this PI is succeeded

[lapis laurel]

Yes, bro

Before we end the chat, could you help me to confirm that Stripe did not call to return_url in that checkout ?

[fresh lion]

I can't confirm, as we have no log on either it redirected or not unforunately