#irishman-react

1 messages · Page 1 of 1 (latest)

restive socket
#

there's no security problem with it really, it's totally fine

#

the only caveat is that if you use the PaymentElement (https://stripe.com/docs/payments/payment-element) that can't be initialised without a PaymentIntent, so you need to create that(and know the amount) before the point that you render that page

Accept payment methods from around the globe with a single secure, embeddable UI component.

hoary mural
#

Is it possible to update resources in the payment intent after its been created?

restive socket
#

you can update the PaymentIntent with an API call yes (https://stripe.com/docs/api/payment_intents/update) but one of the issues is it doesn't update the PaymentElement when doing that(so the amount shown in parts of it, like the Google/Apple Pay popup, would be wrong

#

it's something we are trying to fix(the PaymentElement is new) but for right now it's more like you have to reload the page when the PaymentIntent changes so you re-render the PaymentElement with the new details

hoary mural
#

I don't think this will be an issue with my UI. I'll be updating the payment intent after the user feeds me the amount. Thank you so much for the response and for being here answering questions. Both you guys and your product are truly delightful.

While I have you here, I'm natively bilingual in english and spanish and I can see your documentation is basically non existant in Spanish.

If you guys have any way for me to contribute such as github pull requests, or if you can forward me to somebody that might be interested in this task, I would be happy to get started translating. (Would be a great excuse for me to become learn stripe in-depth👍 )

restive socket
#

thank you!