Just to be clear, does Softr handle association between its accounts and those in Stripe purely by the email address or by the combination of the email address and the Full Name?
We have actually made both the Full Name and the Email of the Softr user read-only on the Stripe checkout screen to prevent the app user from sending different info than that in Softr of the user’s username (email) and the user’s full name, but I wonder - if I had a scenario where my app user wanted to pay with someone else’s credit card, they should be able to do so, and in that case I would allow the user to enter a Full Name other than their own (i.e. the one held in the Softr app itself). That would mean that the only link between Softr and Stripe would be the username email.
Great question. Hate to sound like this, but not surprised Softr isn’t chiming in here. I think email is the only key they use to link a Softr user with a Stripe user. Would love them to correct me if I’m wrong.
They’ve been talking about redoing user accounts for the past year (ie. onboarding, email changing,… ). I just hope they take Softr’s Stripe integration into consideration if and when they do this.
We have actually asked for (and Softr did provide) the code for making the Full Name field read-only on the checkout page (simple checkout form block) to ensure our user’s name always matches that recorded as the customer’s name in Stripe.
I suppose it is possible that our app’s user might want to pay with someone else’s credit card and the full name of that card holder person would be different. That’s when I thought - maybe we should revert back to the Full Name field being read-write.
But then I thought, if the only link between Softr and Stripe users is by email address, then it doesn’t matter whether I keep the Full Name field on the checkout form read-only or read-write. Even if my app’s user has a name different than the payee’s (i.e. card holder’s) name, then if Stripe doesn’t care about the customer’s name matching that of the name on the credit card being charged, then I might as well keep the field read-only for easy tracking of names between the two platforms, while still allowing Stripe to process the card payment, even if that name doesn’t match that of the name on the credit card.
Asking this last nuance of chat gpt, I get the following response:
No, the Stripe customer’s name does not have to be the same as the name on the credit card being used to pay for the subscription in Stripe. Most banks don’t provide a way to verify the cardholder’s name, and names are not typically used for card authorizations.
So, there you go, everyone. I hope this clarifies any mysteries about the checkout form, the user/customer names, the linking between Softr and Stripe and how card authorizations work.
Thanks for the explanation Boris. It sounds like you’re taking the logical approach for user correspondence between Softr and Stripe then. I also noticed that Stripe’s checkout page conveniently auto-populates the Softr user’s info when they are directed from Softr to it as well.
