#Nines

1 messages · Page 1 of 1 (latest)

undone egretBOT
glacial whale
wind pelican
#

Yes. I prefill the form - however if the user changes this - then I cannot match the payment to their record

#

I cannot reject the payment inside checkout.session.completed I assume

#

I also cannot 'freeze' the Stripe form to make it so it's impossible to change the email once preloaded

glacial whale
#

That is not mutable, if you pass an email address on the Checkout Creation. I just tested it

#

Are you seeing otherwise?

#

It's grayed out

wind pelican
#

It's mutable for me

#

Not that it's much use, but I can see the issue, and it's as described.

STRIPE - NEW! - checkout.session.completed - e@dsa.com | eg145 | 2190 | 788400
0STRIPE - User has correct email
:white_check_mark: STRIPE - NEW! - checkout.session.completed - zzzzzz@dsa.com | eg145 | 730 | 26
28000
:warning::warning::warning: email doesn't match, returning error 
glacial whale
#

Can you share the request id with me please?

wind pelican
#

req_kIOo3qfSbpEjny

"customer": {
"id": "cus_NXSfZDaX2TmTKi",
"object": "customer",
"email": "zzzz@dsa.com",
}
"prefilled": {
"email": "e@dsa.com",
"promo_code": null
},

#

I set the prefilled email via querystring - i wonder if there's one that can make the field immutable

glacial whale
#

Ah, you're using payment links

wind pelican
#

Yus, sorry, I called them product links. Yes, and some of them have subscriptions too

#

So they can't actually buy it until they're logged in.
Once they're logged in I can prefill the form/url with email
If they change the prefilled email on the form, then I have issues

glacial whale
#

In this case, there is not I'm afraid.

wind pelican
#

What would be any alternatives

#

and would this be a feature request going forward too

glacial whale