#chris_paymentelement-savedpms

1 messages ¡ Page 1 of 1 (latest)

spice elkBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1280924583859458089

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

restive fable
#

Are you trying to get the Payment Element to autofill all the fields and just allow the customer to update them if they want? (e.g. expiration date, cvv, etc.)

ornate moat
#

Auto-filling would be nice, but not required. The most important aspect is allowing user to EDIT the existing payment method (even if they have to fill-out all of the inputs). We want to avoid the current outcome of a NEW payment method being created.

restive fable
#

As far as I know, a new Payment Method will always be created from customer input on the Payment Element. That goes for whether or not they use the existing Payment Method.

ornate moat
restive fable
#

I think that's intended for workflows that don't use Payment Element (e.g. if you wanted to confirm a Setup Intent from the back-end with an existing Payment Method)

ornate moat
#

Ah, that makes sense. OK, thank you!!

restive fable
#

Sure thing!

spice elkBOT
umbral iron