#CreativeMutation - guest customer

1 messages · Page 1 of 1 (latest)

nova dew
#

Hello, in Stripe's API there is a type of object called a Customer. If you want multiple Checkout purchases to be associated with one customer, you need to manually provide its ID when creating Checkout Sessions (not sure if Squarespace wrote their code to allow you to associate purchases like that)

#

If a Customer ID isn't provided, Stripe creates a guest customer and tries to associate payments with other payments based on email and whatnot

#

Is that helpful?

keen sage
#

no

#

becasue sometimes Stripe creates an account and sometimes it doesn't

#

they all go through the same checkout page

#

so I am not sure why some end up being customers and some end up being guests

nova dew
#

Do you have the ID from one payment with a guest customer and one without?

keen sage
#

yes ofcourse

#

customer : pi_3LaS8jH9md9B7zuY03yY23gF

#

guest : pi_3LajloH9md9B7zuY1wkybdpb

#

in either case, I am not changing anything manually

#

also the weird part is Customers have this random string of text and guests have actual customer name.

nova dew
#

And just to clarify, did you write any code here or is this entirely by SquareSpace?

keen sage
#

i can also give you the checkout page to check it yourself

#

it's entierly squarespace

#

no manual coding

nova dew
#

So I hate to ping pong this again but this looks like their code is deciding whether to create a customer or not at some point and unfortunately I don't know why that might be. When I looked at that first payment, there is a specific API call coming from SquareSpace's code that creates the customer and it just doesn't exist for that second payment https://dashboard.stripe.com/logs/req_EREXs0ax3GVnwS

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

#

They even included a custom idempotency key for the creation so it looks like this is definitely their code, not some automatic thing in Stripe.

#

Can look in to the name aspect of this for a minute. But yeah, I think they pushed you here because "why is a guest customer created" is a Stripe kind of question, but now it is more of a question of when their code decides to create a customer for you vs when it doesn't.

keen sage
#

so what can I do?

nova dew
#

Go back to squarespace and ask why their integration creates a customer or doesn't here

#

They developed the code so they are best equipped to look in to this

keen sage
#

alright

#

thanks for the help

nova dew
#

I can see the end result on our side but not the why unfortunately

#

Of course, good luck figuring this out!

keen sage
#

I am planning to ditch Squarespace totally and just use Payment Links.

nova dew
#

Gotcha, glad to hear that payment links can serve your use case. In that case it will move to all guest customers by the way so that will be consistent

keen sage
#

i have a question though

#

will everyone paying on payment link, will become customers?

#

I want everyone who pays on my platfomr to become customer...

nova dew
#

Unfortunately Payment Links don't support customers. You would need to go to the low-code solution Checkout for that

#

Is there specific customer functionality you are trying to work with here that guest customers don't do?

keen sage
#

but I am talking with stripe support and they say that when anyone pays using payment link, a customer is created

nova dew
#

It looks like I was mistaken. Payment links do create customers, the thing they don't support is re-using customers. So if I make three payments on that link you will have three separate customers on your account even if I use the same card/email/etc

keen sage
#

okay, so the card information is saved?

#

if anyone is paying using payment links, will their card information is saved?

woeful portal
#

Hello 👋
Taking over from Pompey as they had to step away, Give me a few to catch up and I'll respond asap 🙂 thanks

keen sage
#

also found the issue with squaresapce

#

as you can see, when paying the customer decides wheether they want to create an account and save the payment info or not

unknown.png
woeful portal
#

Can you share a bit more about exact usecase here? Like my colleague mentioned, the customers cannot be re-used.
So even if their payment information is saved, there isn't a way to reuse it in future.

#

also found the issue with squaresapce
we're not really familiar with the squarespace integration really, as our team primarily works with Stripe's API integrations.

keen sage
#

sometimes, they don't pay the due amount and defraud us. In that case, we would like to charge their card.

#

in order to avoid this issue, we would like that all payer's payment information is stored. So that we can charge them in case of ghosting/defraud.

woeful portal
#

I see. hmm, I don't know if payment links would be the best option here.

keen sage
#

what would you recommend

#

?

woeful portal
keen sage
#

the issue is you don't know upfront who might defraud you. SO I need to store the info for all payment

woeful portal
#

right, the guide I linked above should store payment method information and set it up for future use

    setup_future_usage: 'off_session',
  },```
#

however, PaymentLinks don't support this

keen sage
#

yeah, but the issue is I have no coding background. And I was wondering if Payment link can do this?

#

exactly

#

so yeah, I probably have to hire a developer

woeful portal
#

yeah I'd recommend working with a developer