#k3davis-guest-customers

1 messages · Page 1 of 1 (latest)

daring tangle
#

Hello, there's not I'm afraid

#

What's the use case? How are you integrating?

bitter mauve
#

users make one time payments, which we prefer not to create customers for because of a lack of de-duplication capabilities in this object (and our forms not being authenticated, so we don't really know who they are yet), but then later wish to convert their charge into recurring.

daring tangle
#

What payments UI are you using to integrate?

bitter mauve
#

we're using card element

daring tangle
#

So you're creating Payment Intents and then confirming on the front-end?

bitter mauve
#

yes

daring tangle
#

Ah, just re-read your question and lack of auth

bitter mauve
#

we're collecting donations rather than selling things, so auth is a hindrance in most cases to this

#

i really wish the customer object was more flexible/featured. but that's not something we can fix here. for us it causes more problems than it solves 😦

daring tangle
#

i really wish the customer object was more flexible/featured
How so?

bitter mauve
#

being able to merge duplicates, mostly 🙂

daring tangle
#

Would your preference here be to disable Guest customers?

#

I guess one solution would be to create a Customer object and persist the cus_xxx in a session cookie or something

#

Not a perfect solution

bitter mauve
#

i'd like it best if we could convert guests to real customers, by adding supporting data to them when they are identified later. being able to disable guest customers would at least hide the problem from view, so that's kind of something, haha

daring tangle
#

Got it. I'll relay the 'convert to real customers' feedback

bitter mauve
#

thanks 🙂 i assume there is some reason why merging isn't a thing, because that seems even more obvious?

#

even if guest customers aren't included that would be very useful

daring tangle
#

I guess it's just an edge case that isn't covered (i.e. unauthenticated customers/users)

#

In most integrations the cus_xxx ID is persisted against some kind of user/session so it's not an issue

bitter mauve
#

yes, fair

#

if we asked every passer by to create an account and sign in before donating it would be a serious hit