#eric_api

1 messages ยท Page 1 of 1 (latest)

sinful oasisBOT
#

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

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

upbeat flumeBOT
upbeat hemlock
#

hello! i'm sorry but i don't understand, can you explain what's the behaviour you're seeing and the behaviour you're expecting in more detail?

spice tide
#

Sure so when we make an API call to get the session object (when our application returns to verify how the process went)
When the session object is returned and the state of it is 'open' url is null

#

So I thought that if the state is 'open' and one would receive the url, one could resume a checkout that was started

#

but we're not seeing any url and therefore I am wondering if it is not possible?

upbeat hemlock
#

do you have an example Checkout Session id? the id will have the prefix cs_

spice tide
#

sure

#

here are parts of the object

"id": "cs_test_a1gPqPEGGMKzSPqXxn5MXJyQ6k9vrGwMdQaMlh5i6QwKcK9LmMOV7iqUDD",
"status": "open",
"url": null

upbeat hemlock
#

the current status of this Checkout Session object is expired

spice tide
#

yeah now it is

#

this was tested last week or something

upbeat hemlock
#

maybe do you have a Checkout Session that currently reflects that issue you're talking about?

spice tide
#

let me see if I can run something

#

"id": "cs_test_a1kzm7GXrjecBcEHisnyt9bGIXD6aMiTsVWxE04mJK1HpHu0WSeeEFHbkC"

#

this one I failed

#

it still shows as open

#

and url is null

upbeat hemlock
#

ah okay, you're using embedded Checkout. Since you're using embedded Checkout, there's no need for a URL - why are you checking for a URL? Typically the URL is used for hosted Checkout whereby the customer is redirected to that URL

spice tide
#

When we create the embedded session we still receive a url so I thought we could go back to that url and that it would be in that object

#

so should we handle open/expired the same in this situation?

upbeat hemlock
#

what are you trying to do with an open/expired Checkout Session?

spice tide
#

So my idea was that if the session in still open that one could resume that payment process

#

or wait, maybe I am thinking wrong about this

#

should we use the clientSecret?

#

if the session is open

#

could one resume a payment with that?

#

Well what I am trying to understand here is if we can resume a payment process if the session is open

upbeat hemlock
#

you should probably be using the clientSecret to load the embedded Checkout Session if the session is still open

spice tide
#

so in the embedded

if expired -> go to expired view
if open -> resume payment
if completed -> go to completed view

#

ok great, we will try that

#

That was all! thanks for the help

upbeat hemlock
#

feel free to reach out again if you're still having issues ๐Ÿ˜ƒ