#gmgarrison

1 messages · Page 1 of 1 (latest)

stable dustBOT
opaque helm
#

When you create PaymentIntent for your Elements, you can specify a Customer Id, if you already acknowledge they are coming back

#

In another word, tightly coupled your own system login credential to 1 Customer Id, and reuse the Customer Id next time

orchid trail
#

We use customer_id every time already

#

Unless for some reason it's failing and I'm not getting any notice

opaque helm
#

When you pass the Customer Id, you can also pass the previously saved PaymentMethod in the PaymentIntent and charge immediately from backend

orchid trail
#

I think that's what we need to do. We don't currently save PaymentMethods but we can.