#lawebso_code

1 messages ยท Page 1 of 1 (latest)

echo gateBOT
#

๐Ÿ‘‹ 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/1359838625231015996

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

steel sand
past kernel
#

Could you please share the PaymentIntent ID pi_xxx?

echo gateBOT
shrewd lake
#

hi! I'm taking over this thread. can you share the PaymentIntent ID as mentioned above?

steel sand
#

seti_1RCIbnJZUpJ6fJ99O6iigDm2

#

it is a setup_intent in this case

#

we collect the payment method for a charge that will happen in the future

#

request id: req_MXS51ddQPM0FQa

shrewd lake
#

the request ID you just shared was successful.

#

can you share the one with the error message?

steel sand
#

we dont have a failed setup intent - we retrieve the setup intent without a problem... when we try to confirm the setup we receive an error back

#

wait, can I find those as well in the stripe dashboard !?- i check

shrewd lake
steel sand
#

i can't find a single failed setup_intent or confirmation call

shrewd lake
#

do you have a link where I can reproduce the issue in test mode?

shrewd lake
#

thanks, give mes a few minutes to look into this.

dapper perch
#

๐Ÿ‘‹ @steel sand

#

Can you share your Javascript file with the function behind the click handler of your confirm button ?

steel sand
dapper perch
#

What does this function?

        route.params.id,
        route.query.token,
        condition
    );``
#

As mentioned earlier today in your other thread, when confirming the Intent, you need to avoid doing intermediate network calls that adds latency. You need directly call stripe js and confirm the intent

#

Otherwise, you'll get the click or touch gesture error

steel sand
#

it makes an api post call to our backend to confirm the checkout first and retrieves an object/response with a order_status_url

dapper perch
#

You need to refactor your code and remove it from the confirm function

#

It's adding latency (waiting your backend to repsond) which causes Apple Pay to fail.

steel sand
#

okay - thank you very much for inspecting the code deeply

#

I will refactor it now