#rpt_checkout-customer

1 messages ยท Page 1 of 1 (latest)

real owlBOT
#

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

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

kind girder
#

@plain steeple this is a bit vague/meta as a question so it's hard to say. I feel like you have a different question maybe?

#

@plain steeple do you have more details?

plain steeple
#

Ill try to clarify.
Currently, each card validation attempt in the checkout funnel results in a new stripe_id, even when associated with the same session. This continues until the user completes checkout. Only then is a single stripe_id assigned to their validated payment method.

#

We're wondering if this is an atypical implementation, as in other areas of our platform (another team) didnt implement it this way.

#

We're also wondering if this affects any Radar rules.

kind girder
#

sorry for the delay

#

I don;t fully grasp what you are describing unfortunately ist's still super high level. What do you call "a new stripe_id" @plain steeple ?

plain steeple
#

It looks like stripe_id corresponds to a customer_id returned from stripe.

#

In our implementation that is.

kind girder
#

Okay then that doesn't really make sense to me. A Customer id wouldn't be created for each attempt unless you create a separate Checkout Session maybe?

#

I think we need to look at 2 concrete examples where you share the exact details: Event id, Checkout Session id and Customer id so I can help debug

plain steeple
#

๐Ÿ‘ will work to grab you the details

kind girder
#

thanks sorry again for missing your follow up earlier

plain steeple
#

No problem, this may take me 24ish hrs to get btw.

kind girder
#

Ah those threads are ephemeral but you can come back tomorrow and start a new thread with all the actionable details

plain steeple
#

:/

kind girder
#

I mean there isn't much in the current thread. So when you have the details you ask the clear question with the exact info and someone should be able to explain quickly after that!

plain steeple
#

Yeah, I get it. Going fishing ๐Ÿ™‚

kind girder
#

I will keep this open for a bit so if you find those fast I can help immediately!

#

rpt_checkout-customer